-
Notifications
You must be signed in to change notification settings - Fork 26
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
Make CRD configuration the default for MetalLB #391
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". 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. |
/reopen |
@cprivitere: Reopened this issue. 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-sigs/prow repository. |
/remove-lifecycle rotten |
/triage accepted |
/remove-lifecycle rotten |
/reopen |
/triage accepted |
MetalLB 0.13.2 switched from using a ConfigMap for configuration to using CRDs. To enable the CCM to work with newer versions of MetalLB without breaking backwards compatibility, we introduced a
crdConfiguration
flag for the MetalLB integration, and usedcrdConfiguration=false
as a default so that the CCM writes MetalLB configuration to a ConfigMap by default.Since we expect future versions of MetalLB to continue to use CRDs for configuration, we should swap the default to
crdConfiguration=true
. This should happen in a major release, and should be accompanied by deprecation warnings for using the CCM with MetalLB <= 0.12.1.The text was updated successfully, but these errors were encountered: