Documenting the use of kubernetesUsername while creating an access entry #8223
Conversation
This file contains hidden or 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Hello jolivataws 👋 Thank you for opening a Pull Request in eksctl project. The team will review the Pull Request and aim to respond within 1-10 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website
bryantbiggs
reviewed
Feb 18, 2025
| kubernetesGroups: # optional Kubernetes groups | ||
| - group1 # groups can used to give permissions via RBAC | ||
| - group2 | ||
| kubernetesUsername: username # optional Kubernetes username |
Contributor
There was a problem hiding this comment.
these are just examples, but the config schema does show/document this option https://eksctl.io/usage/schema/#accessConfig-accessEntries-kubernetesUsername
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
The intention of this change is to document that it is possible to specify the kubernetesUsername field while creating an access entry.
Currently there are no reference to the parameter which currently is leading to the users to believe that this capability is not available for the eksctl.
I have modified the example provided that it is given to the users to showcase that the use of the field is possible.
Checklist
README.md, or theuserdocsdirectory)area/nodegroup) and kind (e.g.kind/improvement)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯