You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#### Special case: Resource with .metadata.ownerReferences
198
+
199
+
Sometimes, secrets are generated by external components. Such secrets are configured with an ownerReference. By default, the kubernetes-replicator will copy the
200
+
ownerReference to the target namespace, too.
201
+
202
+
ownerReference won't work [across different namespaces](https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/#owners-and-dependents) and the secret at the destination will be removed by the kubernetes garbage collection.
203
+
204
+
By set `-strip-owner-reference=true` as CLI argument, kubernetes-replicator will strip the ownerReference fields to avoid deletion of the secrets in the destination.
205
+
206
+
See also: https://github.com/mittwald/kubernetes-replicator/issues/120
0 commit comments