Skip to content
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

It is recommended to adjust the SidecarSet resource to the namespace level. 建议将 SidecarSet 资源调整为命名空间级别 #1882

Open
sigboom opened this issue Jan 15, 2025 · 3 comments
Assignees

Comments

@sigboom
Copy link

sigboom commented Jan 15, 2025

What would you like to be added:
SidecarSet
scope: Cluster => scope: Namespaced

Why is this needed:
The actual production process is divided by namespace. We have not yet considered which scenarios cannot be covered by namespace-level resources. Instead, cluster-level resource design will lead to constraints.

@furykerry
Copy link
Member

it is a good suggestion, however it is not possible to change sidecarset to clusterscope, instead, an extra namespace scoped sidecarset should be introduced.

@sigboom
Copy link
Author

sigboom commented Jan 15, 2025

I re-read the official documentation and found that the native sidecar can basically replace this enhanced resource.
https://kubernetes.io/zh-cn/docs/concepts/workloads/pods/sidecar-containers/

@furykerry
Copy link
Member

sidecarset is not conflict with native sidecar; native sidecar does not support sidecar injection and independent update, sidearset can inject normal and native sidecar, and sidecarset can inplace update normal sidecars

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants