titansoft-pte-ltd/imagepullsecret-patcher

Issues

• 1.24 breaking change - No Secret by default for Service Account token

  #31 opened 2 years ago by connordwoods
  2

• managedonly setting does not work correctly

  #35 opened 2 years ago by tstraley
  1

• Container Image Add ARM and ARM64 Support

  #23 opened 2 years ago by zxp86021
  1

• ImagePullBackOff on first Deployement of Pods

  #10 opened 4 years ago by keviiin38
  5

• Multiple deployments for multiple secrets / private registries?

  #29 opened 3 years ago by dwarburt
  2

• When the cluster is restarted the registry can't be accessed/stop working

  #28 opened 3 years ago by kewynakshlley
  0

• secret not accepted

  #26 opened 3 years ago by Morriz
  4

• option to specify included namespaces

  #27 opened 3 years ago by sameersbn
  0

• Does registry cred operator can take care of adding imagepullsecret to such non default service accounts during their creation so that pods can use it?

  #25 opened 4 years ago by sushantsj
  1

• Add Helm chart support

  #21 opened 4 years ago by paul-pop
  1

• replace scratch default base image to alpine for easy debugging?

  #20 opened 4 years ago by cccfs
  0

• Add support for multiple private registries

  #19 opened 4 years ago by forp007
  1

• Updating the Secret not working

  #17 opened 4 years ago by manderson-it
  4

• Use a secret ref or mount instead of env var for auth data

  #7 opened 4 years ago by valorl
  4

• Example should be explicit about the usage of automountServiceAccountToken

  #8 opened 4 years ago by paul-pop
  1

• Add CI pipeline notification for Travis

  #4 opened 5 years ago by billjh
  3

• Test open issue

  #5 opened 5 years ago by billjh
  1

• Feature Request: Exclude namespaces

  #2 opened 5 years ago by asoni90
  6

• v0.9 is not available on quay.io

  #3 opened 5 years ago by discordier
  1

• Enable non-default service accounts

  #1 opened 5 years ago by goffinf
  6