Question: Helm 3, OpenShift specific resources handling (DeploymentConfigs)
lobziik opened this issue · 4 comments
Hello,
I found a couple of Helm 3 related proposals and would ask about plans for OpenShift specific resources, such as DeploymentConfigs.
Unfortunately, at the moment Helm doesn't handle that specific resources properly (you can not force helm to wait for successful DeploymentConfig rollout for example)
Question - Would it be possible to handle DeploymentConfigs with Helm charts somehow?
Many thanks and best regards!
Denis
P.S. Some links which might illustrate the issue
Helm part which handles Deployments: https://github.com/helm/helm/blob/master/pkg/kube/wait.go#L69
I also made some experiments around:
https://github.com/helm/helm/compare/master...lobziik:openshift_cleaned?expand=1
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen
.
Mark the issue as fresh by commenting/remove-lifecycle rotten
.
Exclude this issue from closing again by commenting/lifecycle frozen
./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.