rancher
/
rke1-docs
mirror of https://github.com/rancher/rke1-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #80 from btat/aws-cloud-provider-cmd 

useInstanceMetadataHostname -> use_instance_metadata_hostname
This commit is contained in:
Billy Tat 2024-02-26 14:35:50 -08:00 committed by GitHub
parent d5d46654bb 8f6cd22019
commit 1b27038524
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/config-options/cloud-providers/aws/aws.md
View File

@ -165,14 +165,14 @@ If you use IP-based naming, the nodes must be named after the instance followed
2. Select the cloud provider.
Selecting `external-aws` sets `--cloud-provider=external` and allows setting `useInstanceMetadataHostname`. Enabling `useInstanceMetadataHostname` will query the EC2 metadata service and set `http://169.254.169.254/latest/meta-data/hostname` as `hostname-override` for `kubelet` and `kube-proxy`.
Selecting `external-aws` sets `--cloud-provider=external` and allows setting `use_instance_metadata_hostname`. Enabling `use_instance_metadata_hostname` will query the EC2 metadata service and set `http://169.254.169.254/latest/meta-data/hostname` as `hostname-override` for `kubelet` and `kube-proxy`.
Enabling `useInstanceMetadataHostname` is required if `hostname-override` is empty or if `hostname-override` doesn't meet the node naming conventions mentioned above in step 1.
Enabling `use_instance_metadata_hostname` is required if `hostname-override` is empty or if `hostname-override` doesn't meet the node naming conventions mentioned above in step 1.
```yaml
cloud_provider:
name: external-aws
useInstanceMetadataHostname: true/false
use_instance_metadata_hostname: true/false
```
Existing clusters that use `external` cloud provider will set `--cloud-provider=external` for Kubernetes components but won't set the `hostname-override` by querying the EC2 metadata service.
@ -364,14 +364,14 @@ kubectl cordon -l "node-role.kubernetes.io/controlplane=true"
5. Update `cluster.yml` to change the cloud provider and remove the leader migration arguments from the kube-controller.
Selecting `external-aws` sets `--cloud-provider=external` and allows setting `useInstanceMetadataHostname`. Enabling `useInstanceMetadataHostname` will query the EC2 metadata service and set `http://169.254.169.254/latest/meta-data/hostname` as `hostname-override` for `kubelet` and `kube-proxy`.
Selecting `external-aws` sets `--cloud-provider=external` and allows setting `use_instance_metadata_hostname`. Enabling `use_instance_metadata_hostname` will query the EC2 metadata service and set `http://169.254.169.254/latest/meta-data/hostname` as `hostname-override` for `kubelet` and `kube-proxy`.
Enabling `useInstanceMetadataHostname` is required if `hostname-override` is empty or if `hostname-override` doesn't meet the [node naming conventions](https://cloud-provider-aws.sigs.k8s.io/prerequisites/).
Enabling `use_instance_metadata_hostname` is required if `hostname-override` is empty or if `hostname-override` doesn't meet the [node naming conventions](https://cloud-provider-aws.sigs.k8s.io/prerequisites/).
```yaml
cloud_provider:
name: external-aws
useInstanceMetadataHostname: true/false
use_instance_metadata_hostname: true/false
```
**Remove** `enable-leader-migration` from: