Skip to content

Prep for 5.0.0 release #780

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 2, 2021
Merged

Prep for 5.0.0 release #780

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
# To re-generate a bundle for another specific version without changing the standard setup, you can:
# - use the WMCO_VERSION as arg of the bundle target (e.g make bundle WMCO_VERSION=0.0.2)
# - use environment variables to overwrite this value (e.g export WMCO_VERSION=0.0.2)
WMCO_VERSION ?= 4.0.0
WMCO_VERSION ?= 5.0.0

# CHANNELS define the bundle channels used in the bundle.
# Add a new line here if you would like to change its default config. (E.g CHANNELS = "preview,fast,stable")
Expand Down
10 changes: 5 additions & 5 deletions bundle/manifests/windows-machine-config-operator.clusterserviceversion.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,14 +8,14 @@ metadata:
certified: "false"
createdAt: REPLACE_DATE
description: An operator that enables Windows container workloads on OCP
olm.skipRange: '>=3.0.0 <4.0.0'
olm.skipRange: '>=4.0.0 <5.0.0'
operatorframework.io/cluster-monitoring: "true"
operatorframework.io/suggested-namespace: openshift-windows-machine-config-operator
operators.operatorframework.io/builder: operator-sdk-v2.0.0+git
operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
repository: https://github.com/openshift/windows-machine-config-operator
support: Red Hat
name: windows-machine-config-operator.v4.0.0
name: windows-machine-config-operator.v5.0.0
namespace: placeholder
spec:
apiservicedefinitions: {}
Expand All @@ -34,8 +34,8 @@ spec:

### Pre-requisites
* A Red Hat OpenShift subscription
* OCP 4.9 cluster running on Azure, AWS or vSphere configured with hybrid OVN Kubernetes networking
* [WMCO prerequisites](https://docs.openshift.com/container-platform/4.9/windows_containers/understanding-windows-container-workloads.html#wmco-prerequisites__understanding-windows-container-workloads)
* OCP 4.10 cluster running on Azure, AWS or vSphere configured with hybrid OVN Kubernetes networking
* [WMCO prerequisites](https://docs.openshift.com/container-platform/4.10/windows_containers/understanding-windows-container-workloads.html#wmco-prerequisites__understanding-windows-container-workloads)

### Usage
Once the `openshift-windows-machine-config-operator` namespace has been created, a secret must be created containing
Expand Down Expand Up @@ -420,4 +420,4 @@ spec:
minKubeVersion: 1.22.0
provider:
name: Red Hat
version: 4.0.0
version: 5.0.0
2 changes: 1 addition & 1 deletion bundle/windows-machine-config-operator.package.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
channels:
- currentCSV: windows-machine-config-operator.v4.0.0
- currentCSV: windows-machine-config-operator.v5.0.0
channels: alpha
packageName: windows-machine-config-operator
6 changes: 3 additions & 3 deletions config/manifests/bases/windows-machine-config-operator.clusterserviceversion.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ metadata:
certified: "false"
createdAt: REPLACE_DATE
description: An operator that enables Windows container workloads on OCP
olm.skipRange: '>=3.0.0 <4.0.0'
olm.skipRange: '>=4.0.0 <5.0.0'
operatorframework.io/cluster-monitoring: "true"
operatorframework.io/suggested-namespace: openshift-windows-machine-config-operator
repository: https://github.com/openshift/windows-machine-config-operator
Expand All @@ -32,8 +32,8 @@ spec:

### Pre-requisites
* A Red Hat OpenShift subscription
* OCP 4.9 cluster running on Azure, AWS or vSphere configured with hybrid OVN Kubernetes networking
* [WMCO prerequisites](https://docs.openshift.com/container-platform/4.9/windows_containers/understanding-windows-container-workloads.html#wmco-prerequisites__understanding-windows-container-workloads)
* OCP 4.10 cluster running on Azure, AWS or vSphere configured with hybrid OVN Kubernetes networking
* [WMCO prerequisites](https://docs.openshift.com/container-platform/4.10/windows_containers/understanding-windows-container-workloads.html#wmco-prerequisites__understanding-windows-container-workloads)

### Usage
Once the `openshift-windows-machine-config-operator` namespace has been created, a secret must be created containing
Expand Down