Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Access Entry type #7522

Merged
merged 2 commits into from
Feb 2, 2024

Conversation

yuxiang-zhang
Copy link
Member

Description

Resolves #7446

Checklist

  • Added tests that cover your change (if possible)
  • Added/modified documentation as required (such as the README.md, or the userdocs directory)
  • Manually tested
  • Made sure the title of the PR is a good description that can go into the release notes
  • (Core team) Added labels for change area (e.g. area/nodegroup) and kind (e.g. kind/improvement)

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 馃く

  • Backfilled missing tests for code in same general area 馃帀
  • Refactored something and made the world a better place 馃専

@yuxiang-zhang yuxiang-zhang added the kind/feature New feature or request label Feb 1, 2024
@yuxiang-zhang yuxiang-zhang force-pushed the add-access-entry-type branch 2 times, most recently from e7fd636 to 09d4165 Compare February 2, 2024 16:51
@@ -6,7 +6,7 @@ kind: ClusterConfig
metadata:
name: access-entries-cluster
region: us-west-2
version: '1.25'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did this example work before? or it's not being tested at all?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it worked with non STANDARD types. I just updated to show the new fields in use

PrincipalARN ARN `json:"principalARN"`
// +optional
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not very sure here but i think // +optional are supposed to be a one line comment. They are parsed by controller-gen if i'm not mistaken..

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we use controller-gen to generate CRDs for eksctl?

a-hilaly
a-hilaly previously approved these changes Feb 2, 2024
Copy link
Member

@a-hilaly a-hilaly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @yuxiang-zhang ! 馃憤

@yuxiang-zhang yuxiang-zhang merged commit 4af2dce into eksctl-io:main Feb 2, 2024
10 checks passed
@yuxiang-zhang yuxiang-zhang deleted the add-access-entry-type branch February 2, 2024 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Access Entries for Self-Managed Nodes not created by eksctl not working
2 participants