search

opendatahub-io / data-science-pipelines-operator

Apache License 2.0
11 stars 47 forks source link

Need a process for catching issues with upgrades between versions #144

Closed HumairAK closed 1 year ago

HumairAK commented 1 year ago

Context:

In the past we have encountered blockers after code-freeze where upgrading from a previous rhods version to latest resulted in breaking dspo/dsp deployments, resulting in alerts, etc. We want to be able to catch such issues before code freeze, which requires adopting version uprades as part of our development process in someway.

Acceptance criteria: A proposal on how to perform regular upgrade testing as part of the dev process (does upgrade from old version -> new version result in failures/alerts/etc.?)

DharmitD commented 1 year ago

Proposal doc to perform regular upgrade testing can be found here.

DharmitD commented 1 year ago

Revised proposal for the upstream DSP upgrade testing strategy can be found here.

DharmitD commented 1 year ago

ADR outlining the upgrade testing strategy for Data Science Pipelines: https://github.com/opendatahub-io/architecture-decision-records/pull/14