Remove OwnerReferences from CA configmaps #1467
Merged
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.
Signed-off-by: Ruben Vargas [email protected]
This change is to avoid
ConfigMaps
which are not in the same namespace as the operator from being garbage collected.As the documentation says:
https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/
Which problem is this PR solving?
ConfigMaps
from sidecars that are not in the same namespace as the operator.Short description of the changes
OwnerReferences
fromConfigMaps
ConfigMaps
when aJaeger
instance is deleted.NOTE: The clean up process consider that there is no more than one Jaeger instance with the same name on the cluster. I think we did this assumption for other parts of the code, so I don't think this will be a problem for now.