kyma-bot
commented
1 year ago This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
- After 60d of inactivity,
lifecycle/staleis applied - After 7d of inactivity since
lifecycle/stalewas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Close this issue or PR with
/close
If you think that I work incorrectly, kindly raise an issue with the problem.
/lifecycle stale
Description The origin of this is the Operational Awarness workshop item #11.b. The assumption is, that if there is sidecar injection enabled or disabled in a namespace, all pods in the namespace should have a sidecar or no sidecar. There is the scenario where the Injection-label is changed or removed while workloads were already deployed. This might result in a communication issue between workloads. It should also be taken into account that the injection can be controlled by a label at pod level.
The proposed mitigation options were:
Reasons The state of the sidecars in the namespace should be consistent with the configurations of the injection of the namespace. A customer might not be aware that changing this configuration requires a restart of the already deployed pods.
DoD:
Attachments