Skip to content

Move helm from root and fix stuff in README #2303

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

Merged
merged 4 commits into from
Nov 13, 2020
Merged

Move helm from root and fix stuff in README #2303

merged 4 commits into from
Nov 13, 2020

Conversation

nhooyr
Copy link
Contributor

@nhooyr nhooyr commented Nov 13, 2020

See @sreya's review in #2048

Only thing I did not add is templating the mount directory but we can wait for someone else to contribute that at some point.

Also, I fixed the examples for helm v3 which does not have --name.

cc @alexgorbatchev @Matthew-Beckett

@nhooyr nhooyr requested a review from sreya November 13, 2020 22:26
@nhooyr nhooyr requested a review from code-asher as a code owner November 13, 2020 22:26
@nhooyr nhooyr force-pushed the helm-db7f branch 2 times, most recently from ad3a370 to ab9cd4d Compare November 13, 2020 22:35
$ git clone https://github.com/cdr/code-server.git
$ helm install code-server/charts/code-server
$ git clone https://github.com/cdr/code-server
$ helm install code-server code-server/ci/helm-chart
Copy link
Collaborator

@sreya sreya Nov 13, 2020

Choose a reason for hiding this comment

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

what about just ci/helm the chart suffix seems implicit

Copy link
Contributor Author

Choose a reason for hiding this comment

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

For me at least it helps to be clear that the directory itself is the chart. It's not like a bunch of scripts to generate the chart or anything.

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree, in most other repositories that maintain charts they are usual in a charts directory at the root, it's unusual for it to be called CI, it might be confusing since it's not build scripts or CI related wizardry.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree, in most other repositories that maintain charts they are usual in a charts directory at the root, it's unusual for it to be called CI, it might be confusing since it's not build scripts or CI related wizardry.

At some point we will want to automate publishing the helm chart so it'll at least be somewhat used in CI.

We tend to keep all our release related stuff in the ci directory to prevent root pollution. In terms of discovery, I think the link I added in install.md should be enough.

$ helm install --name my-release \
--set persistence.enabled=false \
deployment/chart
$ helm install code-server \
Copy link
Collaborator

@sreya sreya Nov 13, 2020

Choose a reason for hiding this comment

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

we could potentially do helm upgrade --install to cover both install and upgrades

@nhooyr nhooyr added this to the v3.6.4 milestone Nov 13, 2020
@nhooyr
Copy link
Contributor Author

nhooyr commented Nov 13, 2020

Moving this to v3.6.4 now, I don't think it's wise to merge as is. I'm not sure if this chart is for helm v2 or v3 now given the use of --name in the examples.

@sreya
Copy link
Collaborator

sreya commented Nov 13, 2020

@nhooyr imo we should really only promote use of v3.

Edit: to add to this the helm chart works fine with v3

@nhooyr nhooyr modified the milestones: v3.6.4, v3.6.3 Nov 13, 2020
@nhooyr
Copy link
Contributor Author

nhooyr commented Nov 13, 2020

Actually moved the release to tomorrow instead.

@Matthew-Beckett
Copy link
Contributor

@nhooyr this is a Helm v3 compatible chart.

@nhooyr
Copy link
Contributor Author

nhooyr commented Nov 13, 2020

@nhooyr imo we should really only promote use of v3.

Absolutely!

But since the examples use --name, I wonder if @Matthew-Beckett used v2 to create it. Want to give him a chance to clarify and perhaps we can use v3 to generate the base which may have improvements.

@Matthew-Beckett
Copy link
Contributor

@nhooyr imo we should really only promote use of v3.

Absolutely!

But since the examples use --name, I wonder if @Matthew-Beckett used v2 to create it. Want to give him a chance to clarify and perhaps we can use v3 to generate the base which may have improvements.

I used v3 to generate the template and cherry-picked the code-server related elements from the Helm Chart that was deprecated.

@nhooyr
Copy link
Contributor Author

nhooyr commented Nov 13, 2020

Ok awesome! Then yea this should be good to go!

@nhooyr
Copy link
Contributor Author

nhooyr commented Nov 13, 2020

Awesome, thanks again @alexgorbatchev @Matthew-Beckett @sreya <3

@nhooyr nhooyr merged commit 7afa689 into master Nov 13, 2020
@nhooyr nhooyr deleted the helm-db7f branch November 13, 2020 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants