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 had a PR in Korifi that sets the default seccomp profile in the spec template of the korifi workloads (both statefulsets and jobs). This can be helpful when running software that requires additional privleges (such as istio). However this results in a change to the pod spec and restarts the respective pod which is disruptive to the users. That's why we added the flags mentioned in the title.
Action to take
Revert this commit and release it in a disruptive release (one that users will have to upgrade to in a maintainence window).
The text was updated successfully, but these errors were encountered:
* `statefulsetRunnerTemporarySetPodSeccompProfile`
* `jobTaskRunnerTemporarySetPodSeccompProfile`
Those helm values were introduced to avoid workloads restart on Korifi
upgrade. With the upcoming release workloads would be restarted by an
unrelated change anyway, so it is a convenient moment to get rid of
those.
fixes#3164
Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
* `statefulsetRunnerTemporarySetPodSeccompProfile`
* `jobTaskRunnerTemporarySetPodSeccompProfile`
Those helm values were introduced to avoid workloads restart on Korifi
upgrade. With the upcoming release workloads would be restarted by an
unrelated change anyway, so it is a convenient moment to get rid of
those.
issue #3164
Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
* `statefulsetRunnerTemporarySetPodSeccompProfile`
* `jobTaskRunnerTemporarySetPodSeccompProfile`
Those helm values were introduced to avoid workloads restart on Korifi
upgrade. With the upcoming release workloads would be restarted by an
unrelated change anyway, so it is a convenient moment to get rid of
those.
issue #3164
Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
Background
We had a PR in Korifi that sets the default seccomp profile in the spec template of the korifi workloads (both statefulsets and jobs). This can be helpful when running software that requires additional privleges (such as istio). However this results in a change to the pod spec and restarts the respective pod which is disruptive to the users. That's why we added the flags mentioned in the title.
Action to take
Revert this commit and release it in a disruptive release (one that users will have to upgrade to in a maintainence window).
The text was updated successfully, but these errors were encountered: