-
Notifications
You must be signed in to change notification settings - Fork 34
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
Argo CD + Istio Gitops tutorial #739
Conversation
Opening this in favor of #737 due to messed up commit history. |
|
Re: failing build, it is due to a breaking change in mkdocs. Part of the reason why my PR is big is because I pushed a fix for this (among other things :) |
I great smaller PR that would have enabled others more quickly :) |
If you could push the fix as a separate PR, that will help. OTOH, If you have suggestions about making this GitOps PR smaller, please let me know. At the moment, this PR includes all the resource files in |
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.
minor comments.
cf4440f
to
74aa891
Compare
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.
lgtm
Signed-off-by: Hai Huang <[email protected]>
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.
lgtm
@sriumcp @kalantar @fabolive here's a draft of the GitOps tutorial. One caveat is this PR needs to be merged to the master branch of this repo for all the references/links to work properly.
The intention of this PR is to provide an initial point of view on how one would use Iter8 in a GitOps scenario, and it's specific for Argo CD + Istio. There are quite a few things that could be improved, e.g., using metrics collector instead of fortio, using a real CI pipeline tool instead of runCI.sh to simulate one, etc. These will be done in a follow up tutorial - to explore Iter8 in a full blown CI/CD pipeline, specifically using Openshift Pipeline and Openshift GitOps. In the process, we will figure out what we need to do to get Iter8 v2 to work in an Openshift cluster.