Added guidance for retrieving CLUSTER_CA, APISERVER_ENDPOINT, and CLUSTER_ID in BootstrapArguments section in outposts/eks-outposts-self-mana…
#834
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fincd-aws
approved these changes
Feb 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Missing information on CLUSTER_ID in EKS Documentation for outposts/eks-outposts-self-managed-nodes.adoc #833
Description of changes:
This PR addresses the issue of missing guidance in the BootstrapArguments section of the EKS user guide for AWS Outposts. It updates the documentation to include commands for retrieving the following values:
CLUSTER_CAAPISERVER_ENDPOINTCLUSTER_IDThese commands clarify how users can fetch these required values using the AWS CLI, making the instructions for self-managed nodes on AWS Outposts using AWS Management Console more complete and user-friendly.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.