In {product-title} version {product-version}, you can install a cluster on Amazon Web Services (AWS) with customized network configuration options. By customizing your network configuration, your cluster can coexist with existing IP address allocations in your environment and integrate with existing MTU and VXLAN configurations.
You must set most of the network configuration parameters during installation,
and you can modify only kubeProxy
configuration parameters in a running
cluster.
-
You reviewed details about the {product-title} installation and update processes.
-
You read the documentation on selecting a cluster installation method and preparing it for users.
-
You configured an AWS account to host the cluster.
ImportantIf you have an AWS profile stored on your computer, it must not use a temporary session token that you generated while using a multi-factor authentication device. The cluster continues to use your current AWS credentials to create AWS resources for the entire life of the cluster, so you must use key-based, long-lived credentials. To generate appropriate keys, see Managing Access Keys for IAM Users in the AWS documentation. You can supply the keys when you run the installation program.
-
If you use a firewall, you configured it to allow the sites that your cluster requires access to.
-
If the cloud identity and access management (IAM) APIs are not accessible in your environment, or if you do not want to store an administrator-level credential secret in the
kube-system
namespace, you can manually create and maintain IAM credentials.
modules/installation-aws-tested-machine-types.adoc modules/installation-aws-arm-tested-machine-types.adoc
Note
|
For more information on using a Network Load Balancer (NLB) on AWS, see Configuring Ingress cluster traffic on AWS using a Network Load Balancer. |
Note
|
For more information on using Linux and Windows nodes in the same cluster, see Understanding Windows container workloads. |
-
See Accessing the web console for more details about accessing and understanding the {product-title} web console.
-
See About remote health monitoring for more information about the Telemetry service.
-
If necessary, you can opt out of remote health reporting.
-
If necessary, you can remove cloud provider credentials.