Skip to content

[ENHANCE]Support triggering a rollout strategy or current behaviour of pod restart on change. #773

Open
@wololowarrior

Description

Is your feature request related to a problem? Please describe.
There are some cases when we need to trigger a rollout strategy instead of just restarting the pods.
#724 This pr removed the functionality of triggering a rollout strategy on change of configmap/secrets.

Describe the solution you'd like
Adding a new annotation to the rollout will trigger a rollout strategy for that rollout. The default can be unset or false, so current behaviour should continue on.

Describe alternatives you've considered
Current behaviour only triggers restarting of pods.

Alt can be along the same lines:

  1. Add a helm value that can allow us to switch bw behaviours, but that is cluster wide setting and not desirable.

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions