Document downstream sync jobs for OSSM#32
Conversation
Add documentation to the profile page for how Prow jobs in OSSM sync upstream Istio repos and propagate dependencies across downstream forks. Signed-off-by: Nick Fox <nfox@redhat.com>
| nightly --> operatorhub | ||
| clean --> operatorhub | ||
|
|
||
| update_deps -->|"merged changes flow<br/>to downstream"| sync_sail |
There was a problem hiding this comment.
I'm not sure if I understand merged changes flow to downstream. Why it starts from Update dependencies box? I guess there is no better box. Or maybe it could start from the grey box which is representing whole stio-ecosystem/sail-operator repo?
There was a problem hiding this comment.
Yeah that's a little confusing. Might be best to just remove the arrow.
| istio_repo -->|"master branch"| sync_istio | ||
| update_istio_ztunnel -->|"updates ztunnel dep<br/>in downstream istio"| sync_istio | ||
| update_istio_proxy -->|"updates proxy dep<br/>in downstream istio"| sync_istio | ||
| update_istio_ztunnel --> gcs |
There was a problem hiding this comment.
I'm not sure if update-istio job pushes artifacts to gcs. Isn't that done elsewhere? The same for proxy
There was a problem hiding this comment.
There was a problem hiding this comment.
But that job only creates a PR to Istio repo to update proxy/ztunnel version. Actual build of proxy/ztunnel and push to gcs is happening somewhere else no? Or the arrow to gcs just means it's using artifacts from there? Not pushing there?
| update_istio_proxy -->|"updates proxy dep<br/>in downstream istio"| sync_istio | ||
| update_istio_ztunnel --> gcs | ||
| update_istio_proxy --> gcs | ||
|
|
There was a problem hiding this comment.
There is also update-istio-module which is updating istio module from upstream to downstream version.
Adds the job to replace the istio/istio dep with ossm/istio. Removes a confusing edge from the graph. Signed-off-by: Nick Fox <nfox@redhat.com>
2 participants
Add documentation to the profile page for how Prow jobs in OSSM sync upstream Istio repos and propagate dependencies across downstream forks.