-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Adding Chart Museum Module for Custom Chart Repos #395
Adding Chart Museum Module for Custom Chart Repos #395
Conversation
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.
There should also be instructions on how to publish a Helm chart to Helm repository.
|
||
To install `chartmuseum` you first need to add the incubator helm repo. | ||
|
||
$ helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com |
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.
Is there no vendor-agnostic URI for this repo?
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.
Not that I saw.
After you have saved the file you can update the cluster thus adding the new | ||
policies to the nodes. | ||
|
||
kops update cluster example.cluster.k8s.local --yes |
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.
IIRC it might take some time for this command to return. Add a note for that?
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.
This one doesn't it's the rolling-update that takes time. This just applies the policy to the instance role.
|
||
kops update cluster example.cluster.k8s.local --yes | ||
|
||
To test this we need to first remove the deployed `chartmuseum`. |
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.
Purpose of removing the chart is not clear. Can you add a comment?
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.
Rather then adding in helm upgrade
which I realized we don't discuss in the 306 module i figured use what they have already learned. Should I switch this to using helm upgrade
?
|
||
$ curl http://localhost:8080/api/charts | ||
{"sample":[{"name":"sample","home":"https://github.com/arun-gupta/kubernetes-aws-workshop","sources":["https://github.com/arun-gupta/kubernetes-aws-workshop"],"version":"1.0.0","description":"My first Haml chart","keywords":["java","javaee","mysql","wildfly","wildfly swarm"],"maintainers":[{"name":"Arun Gupta","email":"[email protected]"}],"urls":["charts/sample-1.0.0.tgz"],"created":"2018-03-09T17:55:43Z","digest":"f01fb09ecb0e0f8f9789aff8343feebab835986d440127471762cfcc5ec2cc24"}]} | ||
|
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.
Explain what is this output? It seems to be referring to an older version of the workshop too.
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.
Yeah, I will do that in the docs FWIW, I'm using the 306 sample chart and just having them package it. Would it make sense for me to update those urls?
**Why:** * This walks a user through deploying `chartmuseum` which allows you to run your own custom `helm` repo backed by s3 with auth. **This change addresses the need by:** * closes aws-samples#70 Signed-off-by: Christopher Hein <[email protected]>
6fd2d65
to
85fa87c
Compare
Fixed most things, and the update cluster doesn't take long
Why:
chartmuseum
which allows you torun your own custom
helm
repo backed by s3 with auth.This change addresses the need by:
Signed-off-by: Christopher Hein [email protected]
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.