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

istio: document procedure that generated the manifests #644

Closed
yanniszark opened this issue Dec 5, 2019 · 6 comments
Closed

istio: document procedure that generated the manifests #644

yanniszark opened this issue Dec 5, 2019 · 6 comments

Comments

@yanniszark
Copy link
Contributor

Since Istio comes with many available options, it's important to document which were used during generation of the istio we use in manifests.

@krishnadurai can you provide more info on the procedure you followed for the istio 1.3.1 package?
What is the source?
What arguments were used in helm?

/cc @jlewi @kkasravi @apyrgio

@krishnadurai
Copy link
Contributor

krishnadurai commented Dec 5, 2019

@yanniszark glad that you bring this up. I'll look to soon document how I generated the manifests. Overall, I used the helm charts being maintained at istio/istio.
Using kustomize converter - https://github.com/ContainerSolutions/helm-convert - I was able to get these manifests converted to Kustomize manifests and later had to combine resources together manually.

Here are the commands for helm conversion which I used:

helm convert --destination <destination> --name istio --namespace "\$(namespace)" install/kubernetes/helm/istio --values install/kubernetes/helm/istio/values-istio-sds-auth.yaml
helm convert --destination <destination> --name istio install/kubernetes/helm/istio-init  --values install/kubernetes/helm/istio-init/values.yaml

Refer PR: #413

@yanniszark
Copy link
Contributor Author

@krishnadurai it would be great if we could write that down in a doc.
In addition, I think it's better to refrain from doing manual work, since we want to be able to try different options and easily view the diffs with git to see what has changed.

I'm also a bit sceptical about helm convert.
I'm worried that it could introduce bugs.

I believe it would be better to just store the yaml blob that helm outputs.
This way, diffs are easy and we don't risk bugs getting introduced in the helm<->kustomize conversion.
What do you think?

/cc @jlewi

@xaniasd
Copy link
Contributor

xaniasd commented Jan 9, 2020

please keep in mind that helm charts will be deprecated in the future (see here). recommended way is to dump the manifests with istioctl manifest generate

@sarahmaddox
Copy link

/cc @krishnadurai and @yanniszark

@stale
Copy link

stale bot commented Jun 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in one week if no further activity occurs. Thank you for your contributions.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the labels:

Label Probability
area/kustomize 0.89

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

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

6 participants