Closed zdtsw closed 1 year ago
@zdtsw Should we also add component requirements for ODH release manifests?
For an ODH release, we should be pulling manifests from a tag
or release-branch
@zdtsw Should we also add component requirements for ODH release manifests? For an ODH release, we should be pulling manifests from a tag or release-branch
added into "Risk" section
@Jooho could you take a look ?
/lgtm
still missing parts:
Read through the ADR, Thanks for the great efforts. The workbench team is in the process of getting the manifests in place. Will respond with updates and then provide my final review.
Read through the ADR, Thanks for the great efforts. The workbench team is in the process of getting the manifests in place. Will respond with updates and then provide my final review.
Thanks @harshad16 I think the goal for ADR is only to inform and get agreement for this proposal. Component team does not need to finalize the implementation in order to sign off ADR. As the proposed solution from operator, it provides the transition with exception for components that are not ready for the moment. Hence, leave the "How" table with "Transition finished? No"
FYI @RobGeada @ruivieira you might need to consider this too.
@zdtsw This PR needs a rebase.
/lgtm
We will start to test modelmesh manifests soon and I hope it will be done by ODH 1.11
Hi @etirelli, can you merge this PR?
Description
Add ADR-Operator-0001 for odh-manifests trainsition
ref: https://github.com/opendatahub-io/opendatahub-operator/issues/338
How Has This Been Tested?
Merge criteria: