release(v0.8.0) update operator metadata and docs

- Bump deploy operator version
- Update deploy example CR with latest values.yaml
- Add changelog information
- Bump Dockerfile version
- Update Operator SDK version to 0.17.2
- Add 0.8.0 OLM
- Clarify release prep steps

CHANGELOG.md

@@ -1,5 +1,24 @@
 # Changelog
 
+## 0.8.0
+
+### Breaking changes
+
+* Chart 2.1 includes 2.0 changes. 2.0 ends support for Helm 2 and removes
+  support for all deprecated configuration in 1.14. Please review the [2.0
+  upgrade guide for details](https://github.com/Kong/charts/blob/kong-2.1.0/charts/kong/UPGRADE.md#200).
+* Bintray, the Docker registry previously used for several Kong images, is
+  discontinuing service. Affected images have moved to Docker Hub. The latest
+  defaults reflect this, but existing your existing Kong custom resources may
+  still reference the old repositories. Review your CRs to see if they contain
+  `bintray.io`, and if so, replace those repositories with the repositories in
+  the [2.1 values.yaml](https://github.com/Kong/charts/blob/kong-2.1.0/charts/kong/values.yaml).
+
+### Improvements
+
+* Updated Helm chart to 2.1.
+* Updated existing OLM CSVs to use the Docker Hub repo for the operator image.
+
 ## 0.7.0
 
 ### Breaking changes

CONTRIBUTING.md

@@ -26,7 +26,8 @@ _For maintainers only_. These instructions require certain privileges (pushing t
 1. Ensure that `HEAD` of `main` defines the release candidate of the operator:
     - set the right version in `build/Dockerfile`,
     - update the Helm chart vendored in this repo (in a clean working copy, run `./hack/update-kong-chart.sh kong-vA.B.C` where `kong-vA.B.C` is an existing tag in the charts repository)
-    - ensure that `deploy/` manifests point to the new (nonexistent yet) operator image tag.
+    - update the  `deploy/operator/deployment.yaml` manifest to point to the new (nonexistent yet) operator image tag.
+    - update the `deploy/crds/charts_v1alpha1_kong_cr.yaml` to the latest default values.yaml.
 1. Define an OperatorHub release spec:
     - Create `/olm/X.Y.Z/` with the CSV and CRD manifests, similarly to [#37](https://github.com/Kong/kong-operator/pull/37) and [#39](https://github.com/Kong/kong-operator/pull/39). Pay particular attention to the following:
        - Always define [`skipRange`](https://docs.openshift.com/container-platform/4.2/operators/understanding_olm/olm-understanding-olm.html#olm-upgrades-replacing-multiple_olm-understanding-olm) to specify a range of versions which support a direct update to the version you're releasing,

build/Dockerfile

@@ -1,11 +1,11 @@
-FROM quay.io/operator-framework/helm-operator:v0.16.0
+FROM quay.io/operator-framework/helm-operator:v0.17.2
 
 ADD LICENSE /licenses/LICENSE
 
 LABEL name="kong-operator" \
       maintainer="harry@konghq.com" \
       vendor="Kong Inc" \
-      version="v0.7.0" \
+      version="v0.8.0" \
       summary="kong-operator installs and manages Kong in your k8s environemnt" \
       description="kong-operator installs and manages Kong in your k8s environemnt"