Argo CD + Istio Gitops tutorial #737
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* document slack notification task Signed-off-by: Michael Kalantar <[email protected]> * fix wording Signed-off-by: Michael Kalantar <[email protected]>
* rebase Signed-off-by: Srinivasan Parthasarathy <[email protected]> * documentation for adding a new K8s stack Signed-off-by: Srinivasan Parthasarathy <[email protected]> * minor edit Signed-off-by: Srinivasan Parthasarathy <[email protected]> * fixing relative links Signed-off-by: Srinivasan Parthasarathy <[email protected]> * Fixing typos Signed-off-by: Srinivasan Parthasarathy <[email protected]> * Fixing capitalization Signed-off-by: Srinivasan Parthasarathy <[email protected]> * Change wording around CRD Signed-off-by: Srinivasan Parthasarathy <[email protected]>
Signed-off-by: Srinivasan Parthasarathy <[email protected]>
* initial seldon quickstart Signed-off-by: Clive Cox <[email protected]> * Add fortio and promotion yaml and change to Iris models Signed-off-by: Clive Cox <[email protected]> * finish e2e test Signed-off-by: Clive Cox <[email protected]> * change promote url to what would be the case when merged Signed-off-by: Clive Cox <[email protected]>
Signed-off-by: Hai Huang <[email protected]>
|
@huang195 We will want to give the GitOps (and all CI/CD) tutorials greater prominence... and not bury it under the tutorials section. We should consider creating a separate top-level link for GitOps/CI/CD. Also, something that can be handled in a subsequent PR. Also, the slack unfurl messages and landing page messages will also need to prominently showcase Argo CD integrations and GitOps capabilities (can be handled in subsequent PRs). |
|
Let me figure out what's wrong with the git commit history... supposed to be one commit after squashing, but it's not |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@sriumcp @kalantar @fabolive here's a draft of the GitOps tutorial. One caveat is this PR needs to be merged to the
masterbranch 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.