chore: Generate bundle for OperatorHub (#16)

JIRA-12610

Signed-off-by: Sergiy Kulanov <[email protected]>
Change-Id: I3deb1893b956ec2b043023bdd61d49833177a09e

README.md

@@ -24,37 +24,37 @@ _**NOTE:** Operator is platform-independent, that is why there is a unified inst
 In order to install the Nexus operator, follow the steps below:
 
 1. To add the Helm EPAMEDP Charts for local client, run "helm repo add":
+
      ```bash
      helm repo add epamedp https://epam.github.io/edp-helm-charts/stable
      ```
+
 2. Choose available Helm chart version:
+
      ```bash
      helm search repo epamedp/nexus-operator -l
      NAME                        CHART VERSION   APP VERSION     DESCRIPTION
-     epamedp/nexus-operator      2.13.0          2.13.0          A Helm chart for EDP Nexus Operator
-     epamedp/nexus-operator      2.12.1          2.12.1          A Helm chart for EDP Nexus Operator
+     epamedp/nexus-operator      3.0.0          3.0.0          A Helm chart for EDP Nexus Operator
      ```
 
     _**NOTE:** It is highly recommended to use the latest released version._
 
 3. Full chart parameters available in [deploy-templates/README.md](deploy-templates/README.md).
 
-4. Install operator in the <edp-project> namespace with the helm command; find below the installation command example:
+4. Install operator in the `nexus-operator` namespace with the helm command; find below the installation command example:
+
     ```bash
-    helm install nexus-operator epamedp/nexus-operator --version <chart_version> --namespace <edp-project> --set name=nexus-operator --set global.platform=<platform_type> --set global.dnsWildCard=<cluster_DNS_wildcard>
+    helm install nexus-operator epamedp/nexus-operator --version <chart_version> --namespace nexus-operator
     ```
-5. Check the <edp-project> namespace that should contain operator deployment with your operator in a running status.
+
+5. Check the `nexus-operator` namespace that should contain operator deployment with your operator in a running status.
 
 ## Local Development
 
 In order to develop the operator, first set up a local environment. For details, please refer to the [Local Development](https://epam.github.io/edp-install/developer-guide/local-development/) page.
 
 Development versions are also available, please refer to the [snapshot helm chart repository](https://epam.github.io/edp-helm-charts/snapshot/) page.
 
-To generate deep copy files you can use [deepcopy-gen](https://pkg.go.dev/k8s.io/gengo/examples/deepcopy-gen) tool
-Example of usage: `deepcopy-gen -i ./v1alpha1 -o ./v1alpha1`
-
 ### Related Articles
 
-* [Architecture Scheme of Nexus Operator](documentation/arch.md)
-* [Install EDP](https://epam.github.io/edp-install/operator-guide/install-edp/)
+* [Install EDP](https://epam.github.io/edp-install/operator-guide/install-edp/)

bundle/manifests/edp.epam.com_nexuses.yaml

@@ -2,7 +2,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.11.4
+    controller-gen.kubebuilder.io/version: v0.13.0
   creationTimestamp: null
   name: nexuses.edp.epam.com
 spec:

bundle/manifests/edp.epam.com_nexusroles.yaml

@@ -2,7 +2,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.11.4
+    controller-gen.kubebuilder.io/version: v0.13.0
   creationTimestamp: null
   name: nexusroles.edp.epam.com
 spec:

bundle/manifests/edp.epam.com_nexususers.yaml

@@ -2,7 +2,7 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.11.4
+    controller-gen.kubebuilder.io/version: v0.13.0
   creationTimestamp: null
   name: nexususers.edp.epam.com
 spec: