-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kyma Istio Operator labels namespace for sidecar injection #361
Comments
This issue or PR has been automatically marked as stale due to the lack of recent activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /lifecycle stale |
This issue or PR has been automatically closed due to the lack of activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /close |
@kyma-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This issue or PR has been automatically marked as stale due to the lack of recent activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /lifecycle stale |
Description
With high demand for workloads being part of Istio Service Mesh, Kyma Istio Operator should be responsible for labeling namespaces with sidecar injection enabled. Istio default setting for automatic sidecar injection is false. From previous experiences with this configuration proving it's hard in maintenance and error prone. This setting should stay as in default Istio. Instead Kyma Istio Operator should label namespaces with sidecar injection enabled.
Istio CR should have configuration option for auto sidecar injection for namespaces. By default this should be true. All namespaces except
kube-system
or those already labeled should be labeled with sidecar injection true.ACs:
Reasons
All workloads in namespaces are automatically part of service mesh
DoD:
- [ ] verify resource limits- [ ] followup issueAttachments
The text was updated successfully, but these errors were encountered: