Skip to content

Latest commit

 

History

History
20 lines (12 loc) · 930 Bytes

README.md

File metadata and controls

20 lines (12 loc) · 930 Bytes
Raw

Copying and configure pull secrets to a created namespace

This example shows how to organize copying secrets to new namespaces after it's creation.

There's 2 labels that affects secrets managed by this controller:

  • copy-secret: "yes": This will copy the secret into any existing namespace
  • pull-secret: "yes": This will copy the secret into any existing namespace and configure it as pull/push secret in the default SA for that namespace.

The source secrets labeled pull-secret: yes are copied from the namespace defined as MAIN_NAMESPACE in the controller deployment to other namespaces in the Kubernetes cluster in the following cases:

  • after a secret with the label pull-secret: yes is created or changed in the namespace defined as MAIN_NAMESPACE in the controller deployment
  • after a new namespace is created

Image does exist in:

quay.io/jorgemoralespou/image-puller-secret-operator:latest