Tekton CD Project Questions
PatrickXYS opened this issue · 6 comments
Per Tekton CD Project, it's developed under GCP Project kf-releasing, build&publish image to GCR registry kubeflow-images-public.
So my question is, is this possible that Google will expire the IAM permission to the GCR registry for Tekton CD in the future as we did for katib
If so, there will be a release issue for training WG + manifests + kubeflow/kubeflow.
/cc @jlewi
Issue-Label Bot is automatically applying the labels:
| Label | Probability |
|---|---|
| platform/gcp | 0.67 |
| kind/question | 0.88 |
Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
Issue-Label Bot is automatically applying the labels:
| Label | Probability |
|---|---|
| area/engprod | 0.69 |
Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
Issue-Label Bot is automatically applying the labels:
| Label | Probability |
|---|---|
| area/engprod | 0.69 |
Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
Issue-Label Bot is automatically applying the labels:
| Label | Probability |
|---|---|
| area/engprod | 0.69 |
Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
Yes. Each wg needs to take ownership of its release process and artifacts. This means each WG should spin up its own release infrastructure as well as any infrastructure to publish release artifact (e.g. docker registry).
kubeflow/community#433 - For notebooks
I also created a Kanban board to start tracking this.
https://github.com/orgs/kubeflow/projects/42?add_cards_query=is%3Aopen