rancher/helm-project-operator

Issues

• CI fails due to change in behaviour in rancher-webhook

  #62 opened 8 months ago by alexandreLamarre
  0

• Can't scale up Operator

  #42 opened a year ago by eumel8
  5

• `Values.global.imagePullSecrets` is broken

  #36 opened 2 years ago by aiyengar2
  1

• cattle-helm-system namespace job gets created in a loop

  #5 opened 2 years ago by aiyengar2
  2

• On a Mac, running `./scripts/build` should pass

  #26 opened 2 years ago by aiyengar2
  1

• Add support for Windows builds to repository and Helm chart

  #11 opened 2 years ago by aiyengar2
  1

• Helm Job Image should still be overridden if Helm Controller is disabled

  #15 opened 2 years ago by aiyengar2
  0

• Modifications to kubeVersion or targets of lookup calls should result in automatic Helm redeployment

  #4 opened 2 years ago by aiyengar2
  1

• NetworkPolicies should be created in Project Release Namespaces targeting Project Namespaces

  #8 opened 2 years ago by aiyengar2
  1

• Adding an entry to otherSystemProjectLabelValues in the Helm chart does not modify the status of the ProjectHelmChart left behind in that project's registration namespace

  #7 opened 2 years ago by aiyengar2
  1

• Controller that creates registration namespaces should be capable of being disabled and deployed standalone

  #10 opened 2 years ago by aiyengar2
  1

• Network Policies should be created in Project Release Namespaces to allow access to pods in Project Namespaces

  #9 opened 2 years ago by aiyengar2
  0

• More information on the status of the underlying HelmCharts and HelmReleases should be accessible by Project Owners

  #6 opened 2 years ago by aiyengar2
  1

• Allow multiple Helm Project Operators targeting the same ProjectHelmChart

  #3 opened 2 years ago by aiyengar2
  1

• Creating an issue should automatically add a team/area3 label

  #1 opened 2 years ago by aiyengar2
  0