From e9ade568423bcffa327cf9f272587bc538293862 Mon Sep 17 00:00:00 2001 From: Shane McDonald Date: Wed, 29 Sep 2021 15:31:20 -0400 Subject: [PATCH] Add note about upgrading to 0.14.0 --- CHANGELOG.md | 2 ++ README.md | 7 ++++++- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d9fa3b56..6d143b1b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,8 @@ This is a list of high-level changes for each release of `awx-operator`. A full # 0.14.0 (TBA) +- Starting with awx-operator 0.14.0, the project is now based on operator-sdk 1.x. + - To avoid a headache, you probably want to delete your existing operator Deployment and follow the README. - Starting with awx-operator 0.14.0, AWX can only be deployed in the namespace that the operator exists in. See [upgrade docs](./README.md#upgrading) for necessary cleanup actions. (Christian Adams) - 58c3ebf (breaking change) # 0.10.0 (Jun 1, 2021) diff --git a/README.md b/README.md index 2bc38558..dc0c41b8 100644 --- a/README.md +++ b/README.md @@ -821,12 +821,17 @@ To upgrade AWX, it is recommended to upgrade the awx-operator to the version tha Apply the awx-operator.yml for that release to upgrade the operator, and in turn also upgrade your AWX deployment. +#### v0.14.0 -**Cluster-scope to Namespace-scope considerations** +##### Cluster-scope to Namespace-scope considerations Starting with awx-operator 0.14.0, AWX can only be deployed in the namespace that the operator exists in. This is called a namespace-scoped operator. If you are upgrading from an earlier version, you will want to delete your existing `awx-operator` service account, role and role binding. +##### Project is now based on v1.x of the operator-sdk project + +Starting with awx-operator 0.14.0, the project is now based on operator-sdk 1.x. You may need to manually delete your old operator Deployment to avoid issues. + ## Contributing Please visit [our contributing guidelines](https://github.com/ansible/awx-operator/blob/devel/CONTRIBUTING.md).