-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 IPAddress and IPAddressClaim CRs to Experimental API #6313
Conversation
Skipping CI for Draft Pull Request. |
/hold |
22ef513
to
948c005
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.
extend newtype descriptions for linking
thanks! lgtm overall other than this question #6313 (comment) |
933bfcb
to
4b3315e
Compare
lgtm only pending #6313 (comment) from my side |
/lgtm Thank you very much for pushing this forward! |
/lgtm |
/cherry-pick release-1.2 |
@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.2 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
@sbueringer: new pull request created: #6887 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
// IPAddressClaimSpec is the desired state of an IPAddressClaim. | ||
type IPAddressClaimSpec struct { | ||
// PoolRef is a reference to the pool from which an IP address should be created. | ||
PoolRef corev1.TypedLocalObjectReference `json:"poolRef"` |
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.
Was reviewing the enhancement and noticed this is using GroupKind to find obejcts, just wanted to note that this is discouraged now and that the TypedLocalObjectReference exists for legacy sake. Current API conventions recommend to create your own reference types (to avoid someone adding a new API field without you noticing) and to use GroupResource for unambiguity. I the API hasn't evolved past alpha yet, it might be worth looking at making that change before it is promoted to a more stable API
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.
Seems to ~ fit in this discussion: #6539 ?
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 I think it does, we should revive that conversation, I'll see if I can re-review that thread
What this PR does / why we need it:
This implements the API contract described in the IPAM Proposal (#6000).
It adds two new Custom Resources to the experimental API: IPAddress and IPAddressClaim.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):