Merge pull request #2101 from MikeSpreitzer/prep-for-0220rc3

✨ Prep for 0220rc3

config/postcreate-hooks/kubestellar.yaml

@@ -184,7 +184,7 @@ spec:
  - kubestellar
  - oci://ghcr.io/kubestellar/kubestellar/controller-manager-chart
  - --version
- - "0.22.0-rc2"
+ - "0.22.0-rc3"
  - --set
  - "ControlPlaneName={{.ControlPlaneName}}"
  env:

docs/content/direct/README.md

@@ -37,7 +37,7 @@ We do not have one that is proven very good yet.
 The first release using the new architecture is 0.20.0; it is feture-incomplete.
 Release 0.21.0 works but is not well documented on the website; [view the missing information directly at GitHub](https://github.com/kubestellar/kubestellar/tree/release-0.21.0/docs/content/direct).
 Release 0.21.2 mostly works but references an outdated version (0.1.0) of the OCM transport plugin.
-The latest release is 0.22.0-rc2.
+The latest release is 0.22.0-rc3.
 See also [the release notes](release-notes.md).
 
 ## Architecture

docs/content/direct/examples.md

@@ -21,7 +21,7 @@ The following steps establish an initial state used in the examples below.
 1. Set environment variables to hold KubeStellar and OCM-status-addon desired versions:
 
  ```shell
- export KUBESTELLAR_VERSION=0.22.0-rc2
+ export KUBESTELLAR_VERSION=0.22.0-rc3
  export OCM_STATUS_ADDON_VERSION=0.2.0-rc8
  export OCM_TRANSPORT_PLUGIN=0.1.6
  ```

docs/content/direct/release-notes.md

@@ -17,6 +17,13 @@ Prominent bug fixes include more discerning cleaning of workload objects on thei
 
 See [the changelogs on GitHub](https://github.com/kubestellar/kubestellar/releases) for full details.
 
+### Remaining limitations in 0.22.0 and its release candidates
+
+* Removing of WorkStatus objects (in the transport namespace) is not supported and may not result in recreation of that object
+* Singleton status return: It is the user responsibility to make sure that if a BindingPolicy requesting singleton status return matches a given workload object then no other BindingPolicy matches the same object. Currently there is no enforcement of that.
+* Objects on two different WDSs shouldn't have the exact same identifier (same group, version, kind, name and namespace). Such a conflict is currently not identified.
+
+
 ## 0.21.2 and its release candidates
 
 The changes since 0.21.1 include efficiency improvements, reducing costs of running the kubestellar-controller-manager for a WDS that is an OpenShift cluster. There are also bug fixes and documentation improvements.

docs/content/direct/release.md

@@ -21,6 +21,9 @@ Between each release of [ks/OTP](https://github.com/kubestellar/ocm-transport-pl
 
 - Edit `test/e2e/common/setup-kubestellar.sh`: update the setting of `OCM_TRANSPORT_PLUGIN_RELEASE` to the latest.
 
+- Edit `test/e2e/multi-cluster-deployment/README.md`: update the setting of `OCM_TRANSPORT_PLUGIN_RELEASE` to the latest.
+
+
 ### Reacting to a new ocm-status-addon release
 
 Update the references to the ocm-status-addon release in the following files.
@@ -37,6 +40,8 @@ Making a new kubestellar release requires a contributor to do the following thin
 
 - Edit [the examples document](examples.md) to update the self-references for the coming release.
 
+- Update the kubestellar self-reference in `test/e2e/multi-cluster-deployment/README.md`.
+
 - Until we have our first stable release, edit [the README](README.md#latest-stable-release) where it wishes it could cite a stable release but instead cites the latest release, to rever to the coming release.
 
 - Edit [the release notes](release-notes.md).

test/e2e/multi-cluster-deployment/README.md

@@ -37,7 +37,7 @@ $ kubectl config rename-context <default-wec1-context-name> kscore
 2. Run e2e test in your ocp cluster:
 
 ```
- export KUBESTELLAR_VERSION=0.22.0-rc2
+ export KUBESTELLAR_VERSION=0.22.0-rc3
  export OCM_STATUS_ADDON_VERSION=0.2.0-rc8
  export OCM_TRANSPORT_PLUGIN=0.1.6
  bash <(curl -s https://raw.githubusercontent.com/kubestellar/kubestellar/release-$KUBESTELLAR_VERSION/test/e2e/multi-cluster-deployment/run-test.sh) --env ocp