-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
v1alpha5 API design #2023
Comments
We should also start labeling when support for a field was introduced in https://kind.sigs.k8s.io/docs/user/configuration/ and ensure all fields are in that doc. EDIT: this is now #2026 |
i like this. |
For dualstack we don't need anything new, just a new field for |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
1 & 4 shipped as additions to v1alpha4 2 pretty much has to be a new one I think, because it's a breaking behavior change in the field. 3 is pretty high effort and I'm not sure we're finding the time. I think it should still happen, but I'm not sure when ... |
We should add a new API revision in order to make some improvements, here is what I have in mind:
extraMounts
should only resolve paths to absolute if they contain a path separator support docker volumes in extra mounts #1966foo
to./foo
, unless they are alreadyfoo/bar
, in which case they will still be resolvedkubeadmConfigPatches
=>componentConfigPatches
+ enhance Kubernetes component config patchingI'm aware of other possible improvements not named above, but I think this is already a lot to work on for the next release, besides changes that aren't API specific, listing them anyhow to start thinking about some more:
The text was updated successfully, but these errors were encountered: