-
Notifications
You must be signed in to change notification settings - Fork 928
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
Comments
@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. Here are the commands for helm conversion which I used:
Refer PR: #413 |
@krishnadurai it would be great if we could write that down in a doc. I'm also a bit sceptical about I believe it would be better to just store the yaml blob that helm outputs. /cc @jlewi |
please keep in mind that helm charts will be deprecated in the future (see here). recommended way is to dump the manifests with |
/cc @krishnadurai and @yanniszark |
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 is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
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
The text was updated successfully, but these errors were encountered: