This repository has been archived by the owner on Aug 25, 2021. It is now read-only.
Add script to aid crd migration #685
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This script will add a metadata key to all service-defaults and proxy-defaults config entries. Custom resources can then be created for these CRDs. Without the change to the metadata, the CRD controller will think these resources are managed by another datacenter and it won't sync any changes for the custom resources.
|
Will be closed by hashicorp/consul-k8s#419 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This script will add a metadata key to all service-defaults and
proxy-defaults config entries.
Custom resources can then be created for these CRDs. Without the change
to the metadata, the CRD controller will think these resources are
managed by another datacenter and it won't sync any changes for the
custom resources.