This release also includes retroactive updates to the existing CSVs. This is a non-standard step to account for the demise of Bintray.
Release steps in CONTRIBUTING still reference the old image location. This section needs additional revision, since the changes to our Docker Hub permissions (removal of personal accounts from the org) preclude manual updates in general. We'll need to move to pushing images from CI. However, as the end of Bintray is imminent, I'm deferring that and will push 0.8.0's image manually still using a temporary local login to one of the bot accounts.
The original attempt to release this with SDK 0.16.0 failed, as 0.16.0 used an older version of Helm 3 that didn't implement lookup. 0.17.2 is a conservative upgrade to do as little as possible to get to a post-Bintray world quickly; we are actually quite behind upstream. Later versions look like they'd require some level of work on the operator metadata (SDK 1.x.y very much so, but even the later 0.x.y suggest they'd need some level of manual work).
I don't think the loss of Helm 2 to 3 migration tools in 0.18 affects the operator, since it was already using a Helm 3-based version and the skip versions for 0.7 even didn't go far back in the past enough to use a Helm 2-based SDK version. Less sure if the K8S v1beta1 CRD removal would cause issues, but we do still use the old version upstream, even though newer K8S versions upgrade the CRD declarations automatically.
0.8.0 updates the chart to 2.1.0.
This release also includes retroactive updates to the existing CSVs. This is a non-standard step to account for the demise of Bintray.
Release steps in CONTRIBUTING still reference the old image location. This section needs additional revision, since the changes to our Docker Hub permissions (removal of personal accounts from the org) preclude manual updates in general. We'll need to move to pushing images from CI. However, as the end of Bintray is imminent, I'm deferring that and will push 0.8.0's image manually still using a temporary local login to one of the bot accounts.
The original attempt to release this with SDK 0.16.0 failed, as 0.16.0 used an older version of Helm 3 that didn't implement lookup. 0.17.2 is a conservative upgrade to do as little as possible to get to a post-Bintray world quickly; we are actually quite behind upstream. Later versions look like they'd require some level of work on the operator metadata (SDK 1.x.y very much so, but even the later 0.x.y suggest they'd need some level of manual work).
I don't think the loss of Helm 2 to 3 migration tools in 0.18 affects the operator, since it was already using a Helm 3-based version and the skip versions for 0.7 even didn't go far back in the past enough to use a Helm 2-based SDK version. Less sure if the K8S v1beta1 CRD removal would cause issues, but we do still use the old version upstream, even though newer K8S versions upgrade the CRD declarations automatically.