-
Notifications
You must be signed in to change notification settings - Fork 24
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
✨ add support for the claim.spec.clusterName property #275
Conversation
4347dee
to
5e2ca61
Compare
}, | ||
)) | ||
if err != nil { | ||
if err := r.Client.List(context.Background(), claims, client.MatchingFields{"clusterName": a.GetName()}); err != nil { |
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.
does this also index the ClusterNameLabel ?
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.
Yes, it prefers the field but indexes both.
5e2ca61
to
5eb8536
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mcbenjemaa, schrej 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:
Adds support for the new
spec.clusterName
ofIPAddressClaims
that was introduced with CAPI 1.8. It is respected when checking whether the referenced Cluster is paused. The label is also still supported.I've added an index for claims that gets filled with either the property or the label's value to make it easier to react to cluster unpausing.
Also contains a few dependency upgrades, including CAPI 1.8.1
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 #258