|
|
| (3 intermediate revisions by the same user not shown) |
| Line 3: |
Line 3: |
| <big>Este artigo está com o status RASCUNHO, tenho muito ainda pra organizar</big> | | <big>Este artigo está com o status RASCUNHO, tenho muito ainda pra organizar</big> |
|
| |
|
| = Primerios Passos = | | = Redhat Openshift = |
|
| |
|
| == Comando de instalação direto ==
| | * [[RedHat Openshift: Primeiros Passos]] |
|
| |
|
| openshift-install create cluster
| | = Vale a pena dar uma olhada = |
|
| |
|
| O comando do exemplo cria o cluster na Amazon AWS. Usa o Terraform para criar os workers.
| | * [https://www.redhat.com/files/summit/session-assets/2018/S1030-Best-practices-for-OpenShift-high-availability-deployment-field-experience-Distribution.pdf Best practices for OpenShift high-availability deployment field experience] |
|
| |
|
| == Comandos de instalação - Passo a Passo ==
| | * [https://rhpds.redhat.com/ Red Hat Product Demo System] |
|
| |
|
| 1) Cria um arquivo install-config.yaml
| | * [https://github.ibm.com/CASE/redcompute-icp-openshift/blob/master/installation/ose-single-master.md Install RedHat OpenShift Container Platform Single Master] |
|
| |
|
| openshift-install create install-config
| | * [https://developers.redhat.com/cheat-sheets/red-hat-openshift-container-platform/ Cheat-sheets for Redhat Openshift Container Platform] |
|
| |
|
| 2) Cria os arquivos manifests
| | * [https://learn.openshift.com/ Interactive Learning Portal] |
|
| |
|
| openshift-install create manifests
| | * [https://www.youtube.com/user/rhopenshift/ Openshift on Youtube] |
| | |
| 3) Cria os arquivos ignition
| |
| | |
| openshift-install create ignition-config
| |
| | |
| Usa os manifests para criar os Workers. Os arquivos são bootstrap.ign, master.ign, worker.ign
| |
| | |
| == Pegando versões e atualizando==
| |
| | |
| 1) Pega a versão do cluster
| |
| | |
| oc get clusterversion
| |
| | |
| 2) Pega os deployments
| |
| oc get deployments -n openshift-cluster-version
| |
| | |
| Resultado:
| |
| NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
| |
| cluster-version-operator 1 1 1 1 12h
| |
| | |
| 3) Faz um ssh dentro do pod
| |
| | |
| oc rsh -n openshift-cluster-version deployments/cluster-version-operator
| |
| | |
| execute
| |
| sh-4.2# ls /release-manifests/
| |
| | |
| == Diversos Comandos==
| |
| | |
| A) Ver os logs
| |
| | |
| oc logs -n openshift-cluster-version deployments/cluster-version-operator
| |
| | |
| B) Ver os pods em um namespace
| |
| | |
| oc get pods -n openshift-kube-apiserver
| |
|
| |
| oc get pods -n openshift-kube-scheduler
| |
|
| |
| oc get pods -n openshift-kube-controller-manager
| |
| | |
| C) Ver os ???
| |
| | |
| oc get ds -n openshift-apiserver
| |
| | |
| | |
| C) Ver os nodes de um cluster
| |
| | |
| oc get nodes -o wide
| |
| | |
| Resultado:
| |
| <small>NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
| |
| ip-10-0-139-163.us-east2-2.compute.internal Ready worker 11h v1.11.0+c... 10.0.139.163 <none> Redhat CoreOS 4.0 3.10.0-957.el7.x86_64 cri-o://1.11.10
| |
| ip-10-0-15-243.us-east2-2.compute.internal Ready master 12h v1.11.0+c... 10.0.15.243 18.21.78.NNN Redhat CoreOS 4.0 3.10.0-957.el7.x86_64 cri-o://1.11.10
| |
| ip-10-0-159-233.us-east2-2.compute.internal Ready worker 11h v1.11.0+c... 10.0.159.233 <none> Redhat CoreOS 4.0 3.10.0-957.el7.x86_64 cri-o://1.11.10</small>
| |
| | |
| Fazendo SSH dentro de um node
| |
| | |
| ssh -i $PEM_FILE core@$EXTERNAL-IP
| |
| | |
| Verificando o resultado do Ignition
| |
| | |
| journalctl --no-pager | grep "Ignition finished sucess" -B 100
| |
|
| |
|
| = Ver também = | | = Ver também = |
