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
I expected that declaring a ResumeProfile would allow me to specify pods that should always remain active, even when the namespace is suspended. However, this does not seem to be the case.
To Reproduce
Steps to reproduce the behavior:
Define a ResumeProfile targeting specific pods.
Set the annotation k8s-pause/suspend to "true" on the namespace.
Observe that all pods in the namespace are paused, including those specified in the ResumeProfile.
Set the annotation k8s-pause/suspend to "false".
Observe that only the targeted pods in the ResumeProfile are resumed, while the others remain paused.
Expected behavior
I expected that the pods specified in the ResumeProfile would always remain up and running, regardless of the namespace suspension state. Specifically:
When k8s-pause/suspend is set to "true", the pods defined in the ResumeProfile should continue running, while all other pods are paused.
When k8s-pause/suspend is set to "false", all pods should resume, but the pods in the ResumeProfile should not have been paused in the first place.
Is this a bug or is it intentional behaviour? How can I create an exception such that a set of pods never pauses?
Thank you for looking into this issue.
The text was updated successfully, but these errors were encountered:
Describe the bug
I expected that declaring a
ResumeProfile
would allow me to specify pods that should always remain active, even when the namespace is suspended. However, this does not seem to be the case.To Reproduce
Steps to reproduce the behavior:
ResumeProfile
targeting specific pods.k8s-pause/suspend
to "true" on the namespace.ResumeProfile
.k8s-pause/suspend
to "false".ResumeProfile
are resumed, while the others remain paused.Expected behavior
I expected that the pods specified in the
ResumeProfile
would always remain up and running, regardless of the namespace suspension state. Specifically:k8s-pause/suspend
is set to "true", the pods defined in theResumeProfile
should continue running, while all other pods are paused.k8s-pause/suspend
is set to "false", all pods should resume, but the pods in theResumeProfile
should not have been paused in the first place.Is this a bug or is it intentional behaviour? How can I create an exception such that a set of pods never pauses?
Thank you for looking into this issue.
The text was updated successfully, but these errors were encountered: