-
Notifications
You must be signed in to change notification settings - Fork 3.4k
helm: kvstoremesh with external etcd #36216
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
Conversation
63a97ac
to
be68a63
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @balous.
I've left a bunch of comments inline. Overall, my main concern, as I had also commented in the original PR, is that with these new modes it is fairly easy for users to end-up in broken scenarios (e.g., if two replicas are active at the same time), although arguably the additional validation is already preventing a bunch of completely unsupported configuration. I think that one essential aspect here (once the main issues have been addressed) would be to clearly frame this functionality as for advanced users only, who have a lot of expertise in this area.
Another aspect I see completely missing is the testing plan, as otherwise there's no guarantee it will not break over time.
/cc @marseel @hemanthmalla @oblazek, as you commented on the original PR.
install/kubernetes/cilium/templates/clustermesh-apiserver/deployment.yaml
Outdated
Show resolved
Hide resolved
install/kubernetes/cilium/templates/clustermesh-config/_helpers.tpl
Outdated
Show resolved
Hide resolved
install/kubernetes/cilium/templates/clustermesh-config/_helpers.tpl
Outdated
Show resolved
Hide resolved
install/kubernetes/cilium/templates/clustermesh-apiserver/deployment.yaml
Outdated
Show resolved
Hide resolved
install/kubernetes/cilium/templates/clustermesh-apiserver/users-configmap.yaml
Outdated
Show resolved
Hide resolved
Coverted this into draft until the feedback is addressed. Feel free to mark this "Ready for review" when ready. |
This pull request has been automatically marked as stale because it |
e7e8202
to
1887f23
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Helm looks good to me structure-wise, thank you! I left one non-blocking question to make sure I understood things correctly, since I'm not familiar with kvstoremesh at all.
install/kubernetes/cilium/templates/clustermesh-apiserver/metrics-service.yaml
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I took a fresh look (and did a bit of local testing). Overall looks mostly good to me, just a few extra minor comments inline.
install/kubernetes/cilium/templates/clustermesh-config/_helpers.tpl
Outdated
Show resolved
Hide resolved
install/kubernetes/cilium/templates/clustermesh-apiserver/deployment.yaml
Outdated
Show resolved
Hide resolved
Removing myself from review, Marco is already reviewing from sig-clustermesh perspective |
51b272d
to
2e6d142
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks almost ready to me 🚀. A couple more comments inline.
7ae6804
to
b29e3fe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
/test |
have the option to use external etcd with kvstoremesh Signed-off-by: Jiri Vanura <jiri.vanura@firma.seznam.cz>
/test |
When running clustermesh-apiserver, there should be an option to enable and disable containers that are not needed.
For example the etcd and apiserver containers are not necessary when running kvstoremesh with an external kvstore.
This commit adds the options to disable these containers.
This PR is revival of #34174, its comments were adressed and some fixes were made.