preferred cloud provider. This guide was tested in AWS, Azure, and GCP from a Linux host. 2. Read OpenShift documentation [https://docs.okd.io/latest/welcome/index.html] to find out about provider-specific useful. With the AWS provider openshift-install will not work properly when MFA credentials are stored in ~/.aws/credentials, traditional credentials are required. With the Azure provider openshift-install login credentials. It’s recommended to setup a dedicated service principal and use it. With the GCP provider openshift-install will only work with a service account key, which has to be set using GOOGLE_CREDENTIALS

preferred cloud provider. This guide was tested in AWS, Azure, and GCP from a Linux host. 2. Read OpenShift documentation [https://docs.okd.io/latest/welcome/index.html] to find out about provider-specific useful. With the AWS provider openshift-install will not work properly when MFA credentials are stored in ~/.aws/credentials, traditional credentials are required. With the Azure provider openshift-install login credentials. It’s recommended to setup a dedicated service principal and use it. With the GCP provider openshift-install will only work with a service account key, which has to be set using GOOGLE_CREDENTIALS

Choose preferred cloud provider. This guide was tested in AWS, Azure & GCP. 2. Read OpenShift documentation [https://docs.okd.io/latest/welcome/index.html] to find out about provider-specific prerequisites useful. with the AWS provider openshift-install will not work properly when MFA credentials are stored in ~/.aws/credentials, traditional credentials are required with the Azure provider openshift-install login credentials. It’s recommended to setup a dedicated service principal and use it with the GCP provider openshift-install will only work with a service account key, which has to be set using GOOGLE_CREDENTIALS

Choose preferred cloud provider. This guide was tested in AWS, Azure & GCP. 2. Read OpenShift documentation [https://docs.okd.io/latest/welcome/index.html] to find out about provider-specific prerequisites useful. with the AWS provider openshift-install will not work properly when MFA credentials are stored in ~/.aws/credentials, traditional credentials are required with the Azure provider openshift-install login credentials. It’s recommended to setup a dedicated service principal and use it with the GCP provider openshift-install will only work with a service account key, which has to be set using GOOGLE_CREDENTIALS

prefix via the node’s IP to all other nodes. Use of the cloud provider’s rou�ng func�onality. Refer to the documenta�on of your cloud provider for addi�onal details (e.g,. AWS VPC Route Tables [h�p://docs each �me a container node is added to the cluster. If you are running Kubernetes with the --cloud-provider in combina�on with the --allocate-node-cidrs op�on then this is configured automa�cally for IPv4 Prometheus can use a number of more common service discovery schemes, such as consul and DNS, or a cloud provider API, such as AWS, GCE or Azure. Prometheus documenta�on [h�ps://prometheus.io/docs/prometheus/l

prefix via the node’s IP to all other nodes. Use of the cloud provider’s routing functionality. Refer to the documentation of your cloud provider for additional details (e.g,. AWS VPC Route Tables [http://docs each time a container node is added to the cluster. If you are running Kubernetes with the -- cloud-provider in combination with the --allocate-node-cidrs option then this is configured automatically for IPv4 port 8472. When running in Direct / Native Routing Mode mode: 3. Run ip route or check your cloud provider router and verify that you have routes installed to route the endpoint prefix between all nodes

prefix via the node’s IP to all other nodes. Use of the cloud provider’s routing functionality. Refer to the documentation of your cloud provider for additional details (e.g,. AWS VPC Route Tables [http://docs each time a container node is added to the cluster. If you are running Kubernetes with the -- cloud-provider in combination with the --allocate-node-cidrs option then this is configured automatically for IPv4 is configured to contain a default route to point to such a router. This model is used for cloud provider network integration. See Google Kubernetes Engine and AWS ENI for more details. 2. Each individual