Skip to content

Add support for immutable ConfigMaps #1368

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

Closed
matthyx opened this issue Feb 3, 2021 · 7 comments
Closed

Add support for immutable ConfigMaps #1368

matthyx opened this issue Feb 3, 2021 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@matthyx
Copy link

matthyx commented Feb 3, 2021

What is the feature and why do you need it:
Feature is in beta since 1.19 and it would be nice to allow using it:
https://kubernetes.io/docs/concepts/configuration/configmap/#configmap-immutable

Describe the solution you'd like to see:
Allow setting immutable in a ConfigMap (or Secret) declaration, instead of getting this kind of error:
TypeError: init() got an expected keyword argument 'immutable'

@matthyx matthyx added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 3, 2021
@roycaihw
Copy link
Member

roycaihw commented Mar 1, 2021

The python client is lagging behind Kubernetes releases. New releases are tracked in: #1242

@matthyx
Copy link
Author

matthyx commented Mar 2, 2021

I see, do you need help from me?

@roycaihw
Copy link
Member

roycaihw commented Mar 4, 2021

I plan to sync with the current contributors on how we can unblock the releases. Will have more to share once we discuss the next steps.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 2, 2021
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 2, 2021
@k8s-triage-robot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

5 participants