Prepare for 0.3.0

thepetk · thepetk · commit c82382558c12 · 2024-08-13T15:03:42.000+01:00
Signed-off-by: thepetk &lt;thepetk@gmail.com&gt;
diff --git a/VERSION b/VERSION
@@ -1 +1 @@
-0.2.0
+0.3.0
diff --git a/bundle.Dockerfile b/bundle.Dockerfile
@@ -1,26 +1,12 @@
-#
-# Copyright Red Hat
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
 FROM scratch
 
 # Core bundle labels.
 LABEL operators.operatorframework.io.bundle.mediatype.v1=registry+v1
 LABEL operators.operatorframework.io.bundle.manifests.v1=manifests/
 LABEL operators.operatorframework.io.bundle.metadata.v1=metadata/
 LABEL operators.operatorframework.io.bundle.package.v1=registry-operator
-LABEL operators.operatorframework.io.bundle.channels.v1=beta
-LABEL operators.operatorframework.io.metrics.builder=operator-sdk-v1.28.0
+LABEL operators.operatorframework.io.bundle.channels.v1=alpha
+LABEL operators.operatorframework.io.metrics.builder=operator-sdk-v1.36.0
 LABEL operators.operatorframework.io.metrics.mediatype.v1=metrics+v1
 LABEL operators.operatorframework.io.metrics.project_layout=go.kubebuilder.io/v3
 
diff --git a/bundle/manifests/registry-operator.clusterserviceversion.yaml b/bundle/manifests/registry-operator.clusterserviceversion.yaml
@@ -49,25 +49,24 @@ metadata:
       ]
     capabilities: Basic Install
     categories: OpenShift Optional,Developer Tools
-    containerImage: quay.io/devfile/registry-operator:v0.2.0
-    createdAt: "2023-11-20T18:36:27Z"
+    containerImage: quay.io/devfile/registry-operator:v0.3.0
+    createdAt: "2024-08-13T13:58:24Z"
     description: Deploy and manage Devfile Registries on Kubernetes and OpenShift
       with the Devfile Registry operator.
-    operators.operatorframework.io/builder: operator-sdk-v1.28.0
+    operators.operatorframework.io/builder: operator-sdk-v1.36.0
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
     repository: https://github.com/devfile/registry-operator
     support: Red Hat
-  name: registry-operator.v0.2.0
+  name: registry-operator.v0.3.0
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
   customresourcedefinitions:
     owned:
-    - description: ClusterDevfileRegistriesList is a custom resource where cluster
-        admins can add a list of Devfile Registries to allow devfiles to be visible
-        at the cluster level.  In order to be added to the list, the Devfile Registries
-        must be reachable, supports the Devfile v2.0 spec and above, and is not using
-        the default namespace.
+    - description: |-
+        ClusterDevfileRegistriesList is a custom resource where cluster admins can add a list of Devfile Registries to allow devfiles to be visible
+        at the cluster level.  In order to be added to the list, the Devfile Registries must be reachable, supports the Devfile v2.0 spec and above,
+        and is not using the default namespace.
       displayName: Cluster Devfile Registries List
       kind: ClusterDevfileRegistriesList
       name: clusterdevfileregistrieslists.registry.devfile.io
@@ -95,10 +94,10 @@ spec:
         displayName: Conditions
         path: conditions
       version: v1alpha1
-    - description: DevfileRegistry is a custom resource allows you to create and manage
-        your own index server and registry viewer. In order to be added, the Devfile
-        Registry must be reachable, supports the Devfile v2.0 spec and above, and
-        is not using the default namespace.
+    - description: |-
+        DevfileRegistry is a custom resource allows you to create and manage your own index server and registry viewer.
+        In order to be added, the Devfile Registry must be reachable, supports the Devfile v2.0 spec and above, and is
+        not using the default namespace.
       displayName: Devfile Registry
       kind: DevfileRegistry
       name: devfileregistries.registry.devfile.io
@@ -140,8 +139,9 @@ spec:
       - description: Sets the image pull policy for the container
         displayName: Image Pull Policy
         path: ociRegistry.imagePullPolicy
-      - description: Overrides the container image used for the OCI registry. Recommended
-          to leave blank and default to the image specified by the operator.
+      - description: |-
+          Overrides the container image used for the OCI registry.
+          Recommended to leave blank and default to the image specified by the operator.
         displayName: Oci Registry Image
         path: ociRegistryImage
       - description: Sets the registry viewer container spec to be deployed on the
@@ -159,36 +159,37 @@ spec:
         path: registryViewerImage
       - displayName: Storage
         path: storage
-      - description: Instructs the operator to deploy the DevfileRegistry with persistent
-          storage Disabled by default.
+      - description: |-
+          Instructs the operator to deploy the DevfileRegistry with persistent storage
+          Disabled by default.
         displayName: Enabled
         path: storage.enabled
-      - description: Configures the size of the devfile registry's persistent volume,
-          if enabled. Defaults to 1Gi.
+      - description: |-
+          Configures the size of the devfile registry's persistent volume, if enabled.
+          Defaults to 1Gi.
         displayName: Registry Volume Size
         path: storage.registryVolumeSize
       - displayName: Telemetry
         path: telemetry
-      - description: Specify a telemetry key to allow devfile specific data to be
-          sent to a client's own Segment analytics source. If the write key is specified
-          then telemetry will be enabled
+      - description: |-
+          Specify a telemetry key to allow devfile specific data to be sent to a client's own Segment analytics source.
+          If the write key is specified then telemetry will be enabled
         displayName: Key
         path: telemetry.key
       - description: The registry name (can be any string) that is used as identifier
           for devfile telemetry.
         displayName: Registry Name
         path: telemetry.registryName
-      - description: Specify a telemetry write key for the registry viewer component
-          to allow data to be sent to a client's own Segment analytics source. If
-          the write key is specified then telemetry for the registry viewer component
-          will be enabled
+      - description: |-
+          Specify a telemetry write key for the registry viewer component to allow data to be sent to a client's own Segment analytics source.
+          If the write key is specified then telemetry for the registry viewer component will be enabled
         displayName: Registry Viewer Write Key
         path: telemetry.registryViewerWriteKey
       - displayName: TLS
         path: tls
-      - description: Instructs the operator to deploy the DevfileRegistry with TLS
-          enabled. Enabled by default. Disabling is only recommended for development
-          or test.
+      - description: |-
+          Instructs the operator to deploy the DevfileRegistry with TLS enabled.
+          Enabled by default. Disabling is only recommended for development or test.
         displayName: Enabled
         path: tls.enabled
       - description: Name of an optional, pre-existing TLS secret to use for TLS termination
@@ -204,11 +205,10 @@ spec:
         displayName: URL
         path: url
       version: v1alpha1
-    - description: DevfileRegistriesList is a custom resource where namespace users
-        can add a list of Devfile Registries to allow devfiles to be visible at the
-        namespace level.  In order to be added to the list, the Devfile Registries
-        must be reachable, supports the Devfile v2.0 spec and above, and is not using
-        the default namespace.
+    - description: |-
+        DevfileRegistriesList is a custom resource where namespace users can add a list of Devfile Registries to allow devfiles to be visible
+        at the namespace level.  In order to be added to the list, the Devfile Registries must be reachable, supports the Devfile v2.0 spec
+        and above, and is not using the default namespace.
       displayName: Devfile Registries List
       kind: DevfileRegistriesList
       name: devfileregistrieslists.registry.devfile.io
@@ -448,7 +448,7 @@ spec:
                 - --leader-elect
                 command:
                 - /manager
-                image: quay.io/devfile/registry-operator:v0.2.0
+                image: quay.io/devfile/registry-operator:v0.3.0
                 imagePullPolicy: Always
                 livenessProbe:
                   httpGet:
@@ -569,7 +569,7 @@ spec:
   provider:
     name: Red Hat
     url: https://redhat.com
-  version: 0.2.0
+  version: 0.3.0
   webhookdefinitions:
   - admissionReviewVersions:
     - v1
diff --git a/bundle/metadata/annotations.yaml b/bundle/metadata/annotations.yaml
@@ -4,8 +4,8 @@ annotations:
   operators.operatorframework.io.bundle.manifests.v1: manifests/
   operators.operatorframework.io.bundle.metadata.v1: metadata/
   operators.operatorframework.io.bundle.package.v1: registry-operator
-  operators.operatorframework.io.bundle.channels.v1: beta
-  operators.operatorframework.io.metrics.builder: operator-sdk-v1.28.0
+  operators.operatorframework.io.bundle.channels.v1: alpha
+  operators.operatorframework.io.metrics.builder: operator-sdk-v1.36.0
   operators.operatorframework.io.metrics.mediatype.v1: metrics+v1
   operators.operatorframework.io.metrics.project_layout: go.kubebuilder.io/v3
 
diff --git a/config/manager/kustomization.yaml b/config/manager/kustomization.yaml
@@ -15,4 +15,4 @@ kind: Kustomization
 images:
 - name: controller
   newName: quay.io/devfile/registry-operator
-  newTag: v0.2.0
+  newTag: v0.3.0
diff --git a/config/manifests/bases/registry-operator.clusterserviceversion.yaml b/config/manifests/bases/registry-operator.clusterserviceversion.yaml
@@ -49,23 +49,22 @@ metadata:
       ]
     capabilities: Basic Install
     categories: OpenShift Optional,Developer Tools
-    containerImage: quay.io/devfile/registry-operator:v0.2.0
+    containerImage: quay.io/devfile/registry-operator:v0.3.0
     createdAt: "2023-09-06T19:45:06Z"
     description: Deploy and manage Devfile Registries on Kubernetes and OpenShift
       with the Devfile Registry operator.
     repository: https://github.com/devfile/registry-operator
     support: Red Hat
-  name: registry-operator.v0.2.0
+  name: registry-operator.v0.3.0
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
   customresourcedefinitions:
     owned:
-    - description: ClusterDevfileRegistriesList is a custom resource where cluster
-        admins can add a list of Devfile Registries to allow devfiles to be visible
-        at the cluster level.  In order to be added to the list, the Devfile Registries
-        must be reachable, supports the Devfile v2.0 spec and above, and is not using
-        the default namespace.
+    - description: |-
+        ClusterDevfileRegistriesList is a custom resource where cluster admins can add a list of Devfile Registries to allow devfiles to be visible
+        at the cluster level.  In order to be added to the list, the Devfile Registries must be reachable, supports the Devfile v2.0 spec and above,
+        and is not using the default namespace.
       displayName: Cluster Devfile Registries List
       kind: ClusterDevfileRegistriesList
       name: clusterdevfileregistrieslists.registry.devfile.io
@@ -93,10 +92,10 @@ spec:
         displayName: Conditions
         path: conditions
       version: v1alpha1
-    - description: DevfileRegistry is a custom resource allows you to create and manage
-        your own index server and registry viewer. In order to be added, the Devfile
-        Registry must be reachable, supports the Devfile v2.0 spec and above, and
-        is not using the default namespace.
+    - description: |-
+        DevfileRegistry is a custom resource allows you to create and manage your own index server and registry viewer.
+        In order to be added, the Devfile Registry must be reachable, supports the Devfile v2.0 spec and above, and is
+        not using the default namespace.
       displayName: Devfile Registry
       kind: DevfileRegistry
       name: devfileregistries.registry.devfile.io
@@ -138,8 +137,9 @@ spec:
       - description: Sets the image pull policy for the container
         displayName: Image Pull Policy
         path: ociRegistry.imagePullPolicy
-      - description: Overrides the container image used for the OCI registry. Recommended
-          to leave blank and default to the image specified by the operator.
+      - description: |-
+          Overrides the container image used for the OCI registry.
+          Recommended to leave blank and default to the image specified by the operator.
         displayName: Oci Registry Image
         path: ociRegistryImage
       - description: Sets the registry viewer container spec to be deployed on the
@@ -157,36 +157,37 @@ spec:
         path: registryViewerImage
       - displayName: Storage
         path: storage
-      - description: Instructs the operator to deploy the DevfileRegistry with persistent
-          storage Disabled by default.
+      - description: |-
+          Instructs the operator to deploy the DevfileRegistry with persistent storage
+          Disabled by default.
         displayName: Enabled
         path: storage.enabled
-      - description: Configures the size of the devfile registry's persistent volume,
-          if enabled. Defaults to 1Gi.
+      - description: |-
+          Configures the size of the devfile registry's persistent volume, if enabled.
+          Defaults to 1Gi.
         displayName: Registry Volume Size
         path: storage.registryVolumeSize
       - displayName: Telemetry
         path: telemetry
-      - description: Specify a telemetry key to allow devfile specific data to be
-          sent to a client's own Segment analytics source. If the write key is specified
-          then telemetry will be enabled
+      - description: |-
+          Specify a telemetry key to allow devfile specific data to be sent to a client's own Segment analytics source.
+          If the write key is specified then telemetry will be enabled
         displayName: Key
         path: telemetry.key
       - description: The registry name (can be any string) that is used as identifier
           for devfile telemetry.
         displayName: Registry Name
         path: telemetry.registryName
-      - description: Specify a telemetry write key for the registry viewer component
-          to allow data to be sent to a client's own Segment analytics source. If
-          the write key is specified then telemetry for the registry viewer component
-          will be enabled
+      - description: |-
+          Specify a telemetry write key for the registry viewer component to allow data to be sent to a client's own Segment analytics source.
+          If the write key is specified then telemetry for the registry viewer component will be enabled
         displayName: Registry Viewer Write Key
         path: telemetry.registryViewerWriteKey
       - displayName: TLS
         path: tls
-      - description: Instructs the operator to deploy the DevfileRegistry with TLS
-          enabled. Enabled by default. Disabling is only recommended for development
-          or test.
+      - description: |-
+          Instructs the operator to deploy the DevfileRegistry with TLS enabled.
+          Enabled by default. Disabling is only recommended for development or test.
         displayName: Enabled
         path: tls.enabled
       - description: Name of an optional, pre-existing TLS secret to use for TLS termination
@@ -202,11 +203,10 @@ spec:
         displayName: URL
         path: url
       version: v1alpha1
-    - description: DevfileRegistriesList is a custom resource where namespace users
-        can add a list of Devfile Registries to allow devfiles to be visible at the
-        namespace level.  In order to be added to the list, the Devfile Registries
-        must be reachable, supports the Devfile v2.0 spec and above, and is not using
-        the default namespace.
+    - description: |-
+        DevfileRegistriesList is a custom resource where namespace users can add a list of Devfile Registries to allow devfiles to be visible
+        at the namespace level.  In order to be added to the list, the Devfile Registries must be reachable, supports the Devfile v2.0 spec
+        and above, and is not using the default namespace.
       displayName: Devfile Registries List
       kind: DevfileRegistriesList
       name: devfileregistrieslists.registry.devfile.io
@@ -289,4 +289,4 @@ spec:
   provider:
     name: Red Hat
     url: https://redhat.com
-  version: 0.2.0
+  version: 0.3.0
