0

My team recently started using helm to manage our Openshift projects and we encountered a problem.

Our helm chart states deploymentconfig triggers to be imageChange and configChange and same for a buildConfig

now when we have a feature that needs a change in configuration and we change the configuration in the helm chart the rollout happens before the build is complete and causes errors for unknown configuration.

Is there a way to prevent that? maybe by making the deploymentConfig wait until the build is finished if a build with the same name is running?

If anyone managed to solve it anyhow I would very much appreciate the help.

o bd
  • 21
  • 7

0 Answers0