AWS에 OpenShift4.1 클러스터 구축
해본 일
공식 프로그램 등을 참고하여 AWS에서 OpenShift4를 사용합니다.하나의 클러스터가 설정되었습니다.
Install on AWS: Installer-Provisioned Infrastructure
Configuring an AWS account
Installing a cluster quickly on AWS
전제 조건
컨디션
구축하다
차리다
Route53 도메인 가져오기
취득한 적이 없기 때문에 참고여기.선취득.com을 하겠습니다.
이하xxx.com.
OpenShift용 IAM 사용자 작성
이름은 뭐든지.
사전 정책 부착AdministratorAccess.
액세스 키를 미리 준비합니다.
AWS CLI 설치
AWS 공식에 소개되어 있습니다.
AWS CLI 설정
제작된 OpenShift용 IAM 사용자의 액세스 키 등을 설정합니다.$ aws configure
AWS Access Key ID [****************7VGL]:
AWS Secret Access Key [****************Gxfq]:
Default region name [ap-northeast-1]:
Default output format [json]:
OpenShift CLI 가져오기
wget https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest/openshift-client-linux-4.1.0.tar.gz
tar zxvf openshift-client-linux-4.1.0.tar.gz
sudo cp oc /usr/local/bin/
OpenShift Installer 가져오기
wget https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest/openshift-install-linux-4.1.0.tar.gz
tar zxvf openshift-install-linux-4.1.0.tar.gz
시크릿 다운로드
참고여기..
실질적 구축
다음은 해동된 설치기가 있는 디렉터리에서 실행됩니다.
install-config.만들다
↓ 명령을 수행하면 각종 구성 정보가 요구되며, 제공 후 임의로 제작된다.apt 적절한 디렉터리를 만듭니다../openshift-install create install-config --dir=<installation_directory>
installation_directory,Platform,Region는 상하 선택의 형식이다.AWS를 선택하면 AWS CLI의 현재 설정을 참조하여 후보를 지정할 수 있으므로 너무 고민할 필요가 없습니다.Base Domain 클러스터 이름을 결정합니다.Cluster Name에서 다운로드한 내용을 복제Pull Secret.
특별히'설정이 끝났다'같은 메시지는 없었지만 이미 끝났다.
클러스터 생성
pull-secret.txt 명령을 실행하면 기다리기만 하면 됩니다.$ ./openshift-install create cluster --dir=./config
INFO Consuming "Install Config" from target directory
INFO Creating infrastructure resources...
INFO Waiting up to 30m0s for the Kubernetes API at https://api.machida-oc-cluster.xxx.com:6443...
INFO API v1.13.4+838b4fa up
INFO Waiting up to 30m0s for bootstrapping to complete...
INFO Destroying the bootstrap resources...
INFO Waiting up to 30m0s for the cluster at https://api.machida-oc-cluster.xxx.com:6443 to initialize...
INFO Waiting up to 10m0s for the openshift-console route to be created...
INFO Install complete!
INFO To access the cluster as the system:admin user when using 'oc', run 'export KUBECONFIG=/mnt/c/dev/openshiftaws/installer/config/auth/kubeconfig'
INFO Access the OpenShift web-console here: https://console-openshift-console.apps.machida-oc-cluster.xxx.com
INFO Login to the console with user: kubeadmin, password: xxxxx-xxxxx-xxxxx-xxxxx
$
한 30분 정도 걸려요.
방문해 보다
브라우저에서
create cluster 브라우저에서 명령의 마지막에 표시되는 URL에 액세스합니다.
사용자,password를 입력하여 로그인합니다.
CLI
그룹을 만든 후에 그룹을 만들었기 때문에 exportcreate cluster라면 명령을 사용하여 그룹을 조작할 수 있습니다.$ export KUBECONFIG=<インストールディレクトリ>/auth/kubeconfig
자동제작물 몇 개 확인
ec2
마스터 노드 3대와 워크맨 노드 3대가 있는 것 같습니다.
이러한 일시적인 실례를 구축하는 bootstrap의 실례도 있지만 簇 구조를 거친 지 얼마 되지 않아 자동으로 사라졌다.
node
$ oc get node -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-10-0-129-152.ap-northeast-1.compute.internal Ready master 166m v1.13.4+cb455d664 10.0.129.152 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-142-245.ap-northeast-1.compute.internal Ready worker 158m v1.13.4+cb455d664 10.0.142.245 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-156-139.ap-northeast-1.compute.internal Ready worker 158m v1.13.4+cb455d664 10.0.156.139 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-159-45.ap-northeast-1.compute.internal Ready master 166m v1.13.4+cb455d664 10.0.159.45 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-174-174.ap-northeast-1.compute.internal Ready master 166m v1.13.4+cb455d664 10.0.174.174 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-175-103.ap-northeast-1.compute.internal Ready worker 158m v1.13.4+cb455d664 10.0.175.103 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
조금 길긴 하지만 한쪽으로 보면 OS는 코어OS, 컨테이너 운행 시간은 cri-o다.
프로젝트
$ oc get ns
NAME STATUS AGE
default Active 159m
kube-public Active 159m
kube-system Active 159m
openshift Active 153m
openshift-apiserver Active 154m
openshift-apiserver-operator Active 158m
openshift-authentication Active 158m
openshift-authentication-operator Active 158m
openshift-cloud-credential-operator Active 158m
openshift-cluster-machine-approver Active 158m
openshift-cluster-node-tuning-operator Active 158m
openshift-cluster-samples-operator Active 158m
openshift-cluster-storage-operator Active 158m
openshift-cluster-version Active 159m
openshift-config Active 159m
openshift-config-managed Active 159m
openshift-console Active 150m
openshift-console-operator Active 150m
openshift-controller-manager Active 158m
openshift-controller-manager-operator Active 158m
openshift-dns Active 157m
openshift-dns-operator Active 158m
openshift-etcd Active 159m
openshift-image-registry Active 158m
openshift-infra Active 159m
openshift-ingress Active 152m
openshift-ingress-operator Active 158m
openshift-kube-apiserver Active 159m
openshift-kube-apiserver-operator Active 159m
openshift-kube-controller-manager Active 159m
openshift-kube-controller-manager-operator Active 159m
openshift-kube-scheduler Active 159m
openshift-kube-scheduler-operator Active 158m
openshift-machine-api Active 158m
openshift-machine-config-operator Active 159m
openshift-marketplace Active 158m
openshift-monitoring Active 158m
openshift-multus Active 158m
openshift-network-operator Active 158m
openshift-node Active 153m
openshift-operator-lifecycle-manager Active 158m
openshift-operators Active 158m
openshift-sdn Active 157m
openshift-service-ca Active 156m
openshift-service-ca-operator Active 158m
openshift-service-catalog-apiserver-operator Active 158m
openshift-service-catalog-controller-manager-operator Active 158m
많이 했어.
openshift-monitoring
$ oc get pod -n openshift-monitoring
NAME READY STATUS RESTARTS AGE
alertmanager-main-0 3/3 Running 0 3h24m
alertmanager-main-1 3/3 Running 0 3h24m
alertmanager-main-2 3/3 Running 0 3h23m
cluster-monitoring-operator-6b875c9f45-kwftv 1/1 Running 0 3h30m
grafana-7cbddfd4f6-bpdx7 2/2 Running 0 3h25m
kube-state-metrics-76dbd866ff-xpj9p 3/3 Running 0 3h30m
node-exporter-62z2v 2/2 Running 0 3h30m
node-exporter-b5vmr 2/2 Running 0 3h30m
node-exporter-gfftq 2/2 Running 0 3h27m
node-exporter-k52pr 2/2 Running 0 3h27m
node-exporter-ldgtc 2/2 Running 0 3h30m
node-exporter-nzrz5 2/2 Running 0 3h27m
prometheus-adapter-65d479d44f-b62m9 1/1 Running 0 3h24m
prometheus-adapter-65d479d44f-hl9wt 1/1 Running 0 3h24m
prometheus-k8s-0 6/6 Running 1 3h24m
prometheus-k8s-1 6/6 Running 1 3h24m
prometheus-operator-7bfd67bf6c-xqk6n 1/1 Running 0 3h24m
telemeter-client-6cc78889f8-5dzbv 3/3 Running 0 3h30m
기본값kubeconfig과 oc은 상승합니다.
기타
원래 AWS 측 작업은 VPC, 서브넷, ELB 제작, EIP 취득 등이 거의 모두 자동화됐다.
etcd를 포함한 구성 요소들이kubeadm 등과 마찬가지로pod로 상승하고 있습니다.
감상
너무 멀리 갔어요.
Reference
이 문제에 관하여(AWS에 OpenShift4.1 클러스터 구축), 우리는 이곳에서 더 많은 자료를 발견하고 링크를 클릭하여 보았다
https://qiita.com/tettsu__/items/3851669343782f242799
텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
우수한 개발자 콘텐츠 발견에 전념
(Collection and Share based on the CC Protocol.)
$ aws configure
AWS Access Key ID [****************7VGL]:
AWS Secret Access Key [****************Gxfq]:
Default region name [ap-northeast-1]:
Default output format [json]:
wget https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest/openshift-client-linux-4.1.0.tar.gz
tar zxvf openshift-client-linux-4.1.0.tar.gz
sudo cp oc /usr/local/bin/
wget https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest/openshift-install-linux-4.1.0.tar.gz
tar zxvf openshift-install-linux-4.1.0.tar.gz
./openshift-install create install-config --dir=<installation_directory>
$ ./openshift-install create cluster --dir=./config
INFO Consuming "Install Config" from target directory
INFO Creating infrastructure resources...
INFO Waiting up to 30m0s for the Kubernetes API at https://api.machida-oc-cluster.xxx.com:6443...
INFO API v1.13.4+838b4fa up
INFO Waiting up to 30m0s for bootstrapping to complete...
INFO Destroying the bootstrap resources...
INFO Waiting up to 30m0s for the cluster at https://api.machida-oc-cluster.xxx.com:6443 to initialize...
INFO Waiting up to 10m0s for the openshift-console route to be created...
INFO Install complete!
INFO To access the cluster as the system:admin user when using 'oc', run 'export KUBECONFIG=/mnt/c/dev/openshiftaws/installer/config/auth/kubeconfig'
INFO Access the OpenShift web-console here: https://console-openshift-console.apps.machida-oc-cluster.xxx.com
INFO Login to the console with user: kubeadmin, password: xxxxx-xxxxx-xxxxx-xxxxx
$
브라우저에서
create cluster 브라우저에서 명령의 마지막에 표시되는 URL에 액세스합니다. 사용자,password를 입력하여 로그인합니다.
CLI
그룹을 만든 후에 그룹을 만들었기 때문에 export
create cluster라면 명령을 사용하여 그룹을 조작할 수 있습니다.$ export KUBECONFIG=<インストールディレクトリ>/auth/kubeconfig
자동제작물 몇 개 확인
ec2
마스터 노드 3대와 워크맨 노드 3대가 있는 것 같습니다.
이러한 일시적인 실례를 구축하는 bootstrap의 실례도 있지만 簇 구조를 거친 지 얼마 되지 않아 자동으로 사라졌다.
node
$ oc get node -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-10-0-129-152.ap-northeast-1.compute.internal Ready master 166m v1.13.4+cb455d664 10.0.129.152 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-142-245.ap-northeast-1.compute.internal Ready worker 158m v1.13.4+cb455d664 10.0.142.245 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-156-139.ap-northeast-1.compute.internal Ready worker 158m v1.13.4+cb455d664 10.0.156.139 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-159-45.ap-northeast-1.compute.internal Ready master 166m v1.13.4+cb455d664 10.0.159.45 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-174-174.ap-northeast-1.compute.internal Ready master 166m v1.13.4+cb455d664 10.0.174.174 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-175-103.ap-northeast-1.compute.internal Ready worker 158m v1.13.4+cb455d664 10.0.175.103 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
조금 길긴 하지만 한쪽으로 보면 OS는 코어OS, 컨테이너 운행 시간은 cri-o다.
프로젝트
$ oc get ns
NAME STATUS AGE
default Active 159m
kube-public Active 159m
kube-system Active 159m
openshift Active 153m
openshift-apiserver Active 154m
openshift-apiserver-operator Active 158m
openshift-authentication Active 158m
openshift-authentication-operator Active 158m
openshift-cloud-credential-operator Active 158m
openshift-cluster-machine-approver Active 158m
openshift-cluster-node-tuning-operator Active 158m
openshift-cluster-samples-operator Active 158m
openshift-cluster-storage-operator Active 158m
openshift-cluster-version Active 159m
openshift-config Active 159m
openshift-config-managed Active 159m
openshift-console Active 150m
openshift-console-operator Active 150m
openshift-controller-manager Active 158m
openshift-controller-manager-operator Active 158m
openshift-dns Active 157m
openshift-dns-operator Active 158m
openshift-etcd Active 159m
openshift-image-registry Active 158m
openshift-infra Active 159m
openshift-ingress Active 152m
openshift-ingress-operator Active 158m
openshift-kube-apiserver Active 159m
openshift-kube-apiserver-operator Active 159m
openshift-kube-controller-manager Active 159m
openshift-kube-controller-manager-operator Active 159m
openshift-kube-scheduler Active 159m
openshift-kube-scheduler-operator Active 158m
openshift-machine-api Active 158m
openshift-machine-config-operator Active 159m
openshift-marketplace Active 158m
openshift-monitoring Active 158m
openshift-multus Active 158m
openshift-network-operator Active 158m
openshift-node Active 153m
openshift-operator-lifecycle-manager Active 158m
openshift-operators Active 158m
openshift-sdn Active 157m
openshift-service-ca Active 156m
openshift-service-ca-operator Active 158m
openshift-service-catalog-apiserver-operator Active 158m
openshift-service-catalog-controller-manager-operator Active 158m
많이 했어.
openshift-monitoring
$ oc get pod -n openshift-monitoring
NAME READY STATUS RESTARTS AGE
alertmanager-main-0 3/3 Running 0 3h24m
alertmanager-main-1 3/3 Running 0 3h24m
alertmanager-main-2 3/3 Running 0 3h23m
cluster-monitoring-operator-6b875c9f45-kwftv 1/1 Running 0 3h30m
grafana-7cbddfd4f6-bpdx7 2/2 Running 0 3h25m
kube-state-metrics-76dbd866ff-xpj9p 3/3 Running 0 3h30m
node-exporter-62z2v 2/2 Running 0 3h30m
node-exporter-b5vmr 2/2 Running 0 3h30m
node-exporter-gfftq 2/2 Running 0 3h27m
node-exporter-k52pr 2/2 Running 0 3h27m
node-exporter-ldgtc 2/2 Running 0 3h30m
node-exporter-nzrz5 2/2 Running 0 3h27m
prometheus-adapter-65d479d44f-b62m9 1/1 Running 0 3h24m
prometheus-adapter-65d479d44f-hl9wt 1/1 Running 0 3h24m
prometheus-k8s-0 6/6 Running 1 3h24m
prometheus-k8s-1 6/6 Running 1 3h24m
prometheus-operator-7bfd67bf6c-xqk6n 1/1 Running 0 3h24m
telemeter-client-6cc78889f8-5dzbv 3/3 Running 0 3h30m
기본값kubeconfig과 oc은 상승합니다.
기타
원래 AWS 측 작업은 VPC, 서브넷, ELB 제작, EIP 취득 등이 거의 모두 자동화됐다.
etcd를 포함한 구성 요소들이kubeadm 등과 마찬가지로pod로 상승하고 있습니다.
감상
너무 멀리 갔어요.
Reference
이 문제에 관하여(AWS에 OpenShift4.1 클러스터 구축), 우리는 이곳에서 더 많은 자료를 발견하고 링크를 클릭하여 보았다
https://qiita.com/tettsu__/items/3851669343782f242799
텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
우수한 개발자 콘텐츠 발견에 전념
(Collection and Share based on the CC Protocol.)
$ oc get node -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-10-0-129-152.ap-northeast-1.compute.internal Ready master 166m v1.13.4+cb455d664 10.0.129.152 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-142-245.ap-northeast-1.compute.internal Ready worker 158m v1.13.4+cb455d664 10.0.142.245 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-156-139.ap-northeast-1.compute.internal Ready worker 158m v1.13.4+cb455d664 10.0.156.139 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-159-45.ap-northeast-1.compute.internal Ready master 166m v1.13.4+cb455d664 10.0.159.45 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-174-174.ap-northeast-1.compute.internal Ready master 166m v1.13.4+cb455d664 10.0.174.174 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
ip-10-0-175-103.ap-northeast-1.compute.internal Ready worker 158m v1.13.4+cb455d664 10.0.175.103 <none> Red Hat Enterprise Linux CoreOS 410.8.20190520.0 (Ootpa) 4.18.0-80.1.2.el8_0.x86_64 cri-o://1.13.9-1.rhaos4.1.gitd70609a.el8
$ oc get ns
NAME STATUS AGE
default Active 159m
kube-public Active 159m
kube-system Active 159m
openshift Active 153m
openshift-apiserver Active 154m
openshift-apiserver-operator Active 158m
openshift-authentication Active 158m
openshift-authentication-operator Active 158m
openshift-cloud-credential-operator Active 158m
openshift-cluster-machine-approver Active 158m
openshift-cluster-node-tuning-operator Active 158m
openshift-cluster-samples-operator Active 158m
openshift-cluster-storage-operator Active 158m
openshift-cluster-version Active 159m
openshift-config Active 159m
openshift-config-managed Active 159m
openshift-console Active 150m
openshift-console-operator Active 150m
openshift-controller-manager Active 158m
openshift-controller-manager-operator Active 158m
openshift-dns Active 157m
openshift-dns-operator Active 158m
openshift-etcd Active 159m
openshift-image-registry Active 158m
openshift-infra Active 159m
openshift-ingress Active 152m
openshift-ingress-operator Active 158m
openshift-kube-apiserver Active 159m
openshift-kube-apiserver-operator Active 159m
openshift-kube-controller-manager Active 159m
openshift-kube-controller-manager-operator Active 159m
openshift-kube-scheduler Active 159m
openshift-kube-scheduler-operator Active 158m
openshift-machine-api Active 158m
openshift-machine-config-operator Active 159m
openshift-marketplace Active 158m
openshift-monitoring Active 158m
openshift-multus Active 158m
openshift-network-operator Active 158m
openshift-node Active 153m
openshift-operator-lifecycle-manager Active 158m
openshift-operators Active 158m
openshift-sdn Active 157m
openshift-service-ca Active 156m
openshift-service-ca-operator Active 158m
openshift-service-catalog-apiserver-operator Active 158m
openshift-service-catalog-controller-manager-operator Active 158m
$ oc get pod -n openshift-monitoring
NAME READY STATUS RESTARTS AGE
alertmanager-main-0 3/3 Running 0 3h24m
alertmanager-main-1 3/3 Running 0 3h24m
alertmanager-main-2 3/3 Running 0 3h23m
cluster-monitoring-operator-6b875c9f45-kwftv 1/1 Running 0 3h30m
grafana-7cbddfd4f6-bpdx7 2/2 Running 0 3h25m
kube-state-metrics-76dbd866ff-xpj9p 3/3 Running 0 3h30m
node-exporter-62z2v 2/2 Running 0 3h30m
node-exporter-b5vmr 2/2 Running 0 3h30m
node-exporter-gfftq 2/2 Running 0 3h27m
node-exporter-k52pr 2/2 Running 0 3h27m
node-exporter-ldgtc 2/2 Running 0 3h30m
node-exporter-nzrz5 2/2 Running 0 3h27m
prometheus-adapter-65d479d44f-b62m9 1/1 Running 0 3h24m
prometheus-adapter-65d479d44f-hl9wt 1/1 Running 0 3h24m
prometheus-k8s-0 6/6 Running 1 3h24m
prometheus-k8s-1 6/6 Running 1 3h24m
prometheus-operator-7bfd67bf6c-xqk6n 1/1 Running 0 3h24m
telemeter-client-6cc78889f8-5dzbv 3/3 Running 0 3h30m
너무 멀리 갔어요.
Reference
이 문제에 관하여(AWS에 OpenShift4.1 클러스터 구축), 우리는 이곳에서 더 많은 자료를 발견하고 링크를 클릭하여 보았다 https://qiita.com/tettsu__/items/3851669343782f242799텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
우수한 개발자 콘텐츠 발견에 전념
(Collection and Share based on the CC Protocol.)
좋은 웹페이지 즐겨찾기
