You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using ArgoCD and old replicaset only clutter the interface without any benefit. If we were able to set revisionHistoryLimit to "0" for deployments, replicasets without any pods would be removed.
Describe the enhancement/feature:
Add the following values to the values.yaml and render them into the corresponding Deployment spec.
@helmecke-nlb Thanks for the suggestion.
Currently, we are considering providing users a generic way to define any extra config they need.
Probably this will be part of the 8.6 release in October (maybe also before it).
Describe the use case:
We are using ArgoCD and old replicaset only clutter the interface without any benefit. If we were able to set revisionHistoryLimit to "0" for deployments, replicasets without any pods would be removed.
Describe the enhancement/feature:
Add the following values to the
values.yaml
and render them into the correspondingDeployment
spec.connectors.revisionHistoryLimit: 10
console.revisionHistoryLimit: 10
identity.revisionHistoryLimit: 10
operate.revisionHistoryLimit: 10
optimize.revisionHistoryLimit: 10
tasklist.revisionHistoryLimit: 10
webModeler.restapi.revisionHistoryLimit: 10
webModeler.webapp.revisionHistoryLimit: 10
webModeler.websockets.revisionHistoryLimit: 10
zeebeGateway.revisionHistoryLimit: 10
Desired outcome and acceptance tests:
revisionHistoryLimit
in everyDeployment
can be set viavalues.yaml
.The text was updated successfully, but these errors were encountered: