-
Notifications
You must be signed in to change notification settings - Fork 540
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Support cluster names > 22 characters in length #1290
Conversation
572e894
to
72176e5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kind of wish we could keep part of the cluster name as a prefix to make it a bit user friendlier. That said, we are still applying a tag for the cluster name, so users can filter on that.
I'm also wondering if we should update the default to the hashed naming and just provide a fallback in the call to DescribeLoadBalancers by passing in both the hashed and <clustername>-apiserver
names?
72176e5
to
9bb4469
Compare
Signed-off-by: Naadir Jeewa <jeewan@vmware.com>
9bb4469
to
0068ee5
Compare
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ncdc, randomvariable The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
use a truncated form of Blake2b to compute a consistent hash formatted ELB name.
Think this approach has a sufficiently low risk of collisions. "apiserver" suffix is
replaced with "k8s" to regain some entropy. Names arrive in the format of:
26o3cjil5at5qn27vukn5x09b3ql-k8s
t8gnrbbifaaf5d0k4xmwui3xwvip-k8s
etc...
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #977
Fixes #889