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.
An approach with a status sub-resource would be interesting for scenarios where a separate
IPAMLease
controller operates as an IPAM controller; the client workload controllers (e.g. KubeVirt) would:Differentiating between resource and sub-resource at Roles allows having distinct authorization scopes; meaning users can be granted full write access to spec and read-only access to status, while relevant controllers are granted read-only access to spec but full write access to status.
Thus, assuming KubeVirt would be "the" reference client, we would have the KubeVirt controller as having write access to spec and read-only to status, while the IPAM CNI would have read-only access to the spec stanza, while having full write access to the status sub-resource.