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.

Sign up for GitHub

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

Jump to bottom

Add immutable fields to Kubernetes OpenAPI spec #342

Open
hausdorff opened this issue Jan 7, 2019 · 1 comment
Open

Add immutable fields to Kubernetes OpenAPI spec #342

hausdorff opened this issue Jan 7, 2019 · 1 comment
Labels
area/resource-management Issues related to Kubernetes resource provisioning, management, await logic, and semantics generally kind/engineering Work that is not visible to an external user

Comments

@hausdorff
Copy link
Contributor

Following up from this comment, some fields in Kubernetes resource definitions are immutable (e.g., Deployment's .spec.selector), and changing them necessitates a replacement.

We are currently manually curating a list of these things, which once correct, will be very powerful. But a better idea is to engage SIGCLI and simply solve this in upstream by changing the OpenAPI spec to reflect these things.

This is our local "tracking issue" for this.
@hausdorff hausdorff added priority/P1 area/resource-management Issues related to Kubernetes resource provisioning, management, await logic, and semantics generally labels Jan 7, 2019
@hausdorff hausdorff added this to the 0.21 milestone Jan 7, 2019
@hausdorff
Copy link
Contributor Author

Just a quick note as I un-tag this from P1: I tagged it P1 when I didn't know "what P1 means at Pulumi". To be clear: we can and should track with upstream to see how we can assist as they start to make similar changes to upstream, but we should not block M21 on it.

Since upstream is not quite ready to have the conversation, I will bump to M22.

@hausdorff hausdorff modified the milestones: 0.21, 0.22 Mar 4, 2019
@lukehoban lukehoban removed this from the 0.22 milestone Apr 20, 2019
@protometa protometa mentioned this issue Mar 2, 2020
Closed
@lblackstone lblackstone mentioned this issue Mar 4, 2020
Merged
@infin8x infin8x added kind/engineering Work that is not visible to an external user and removed kind/debt labels Jul 10, 2021
@lblackstone lblackstone removed their assignment Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/resource-management Issues related to Kubernetes resource provisioning, management, await logic, and semantics generally kind/engineering Work that is not visible to an external user
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lukehoban @infin8x @hausdorff @lblackstone