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

clustermesh enable: add enable-kvstoremesh flag #1734

Merged
merged 1 commit into from
Jun 21, 2023

Conversation

giorio94
Copy link
Member

This PR extends the cilium clustermesh enable command with a new flag which can be used to enable kvstoremesh (cilium/cilium#26083). The new flag is supported only when using the new Helm mode, and requires cilium >= 1.14 (it has no effect on earlier versions). Related: cilium/cilium#26348

This commit extends the `cilium clustermesh enable` command with a new
flag which can be used to enable kvstoremesh (cilium/cilium#26083). The
new flag is supported only when using the new Helm mode, and requires
cilium >= 1.14 (it has no effect on earlier versions).

Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
@giorio94 giorio94 requested review from a team as code owners June 19, 2023 12:16
@giorio94 giorio94 temporarily deployed to ci June 19, 2023 12:16 — with GitHub Actions Inactive
@giorio94 giorio94 requested a review from asauber June 19, 2023 12:16
Copy link
Member

@asauber asauber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving this as a clean implementation that matches the current style.

It brings up two questions for me:

  1. Maybe we should reconsider allowing --helm-set for subcommands like clustermesh enable, because we would get features like this for free.

  2. The chained type-assertion on the Helm values instead of using types is starting to look a bit messy, we should revisit that.

@giorio94
Copy link
Member Author

1. Maybe we should reconsider allowing `--helm-set` for subcommands like `clustermesh enable`, because we would get features like this for free.

I personally agree. While for certain features it might still better to have a dedicated flag, we also need --helm-set to be able to configure image versions or other parameters.

2. The chained type-assertion on the Helm values instead of using types is starting to look a bit messy, we should revisit that.

That's true. Maybe we could add an helper to set a given value at a certain "path" in the values map.

Copy link
Contributor

@michi-covalent michi-covalent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😇

@michi-covalent michi-covalent added the priority/release-blocker This issue will prevent the release of the next version of Cilium. label Jun 20, 2023
@michi-covalent michi-covalent merged commit 8882712 into cilium:main Jun 21, 2023
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/clustermesh priority/release-blocker This issue will prevent the release of the next version of Cilium.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants