ADR on components

[goern]

How would we like to cut the components?

1. Operator and it's CRD
2. Pipeline and Task declarations, so the logic is separated from the Operator
3. container image in support of pipeline tasks, holding the scripts etc

Do we want to put it all in one repo/image? is that good enough for a POC?

Acceptance Criteria

• ADRs published/merged for
  • ADR on packaging the pipeline manifests (i.e. documenting the outcome of [spike] Decide on how to package and deploy the pipeline manifests #10)
  • git repo usage (we decided not to use a git repo as the canonical source)
  • ADR on using an operator and a custom resource
  • ADR on base container images
  • ADR on the ownership chains and how we handle cross-namespace relations and/or restrictions. Related info:
    • How project meteor implemented Comas to manage cross-namespace ownership
    • How/if ODH's switch to Kubeflow notebook controller impacts namespaces of our resources ([SPIKE]Investigate the changes needed to adapt to KubeFlow Notebook controller helm-charts#47)
• ADR linked from the README

/kind documentation
/priority important-soon

[codificat]

/wg cnbi

[codificat]

Related:

• [spike] Decide on how to package and deploy the pipeline manifests #10
• create ADR on git repository usage open-services-group/scrum#33

And I think this belongs to the cnbi repo:
/transfer opendatahub-cnbi

[codificat]

/assign

[VannTen]

I would add to the list:

• ADR on the ownership chains/namespacing we choose

[codificat]

Ack! I added it to the list of acceptance criteria