Merge pull request #22 from Netcracker/feature/return_api_group

feat: return api group

Author: mrMigles

SECURITY.md

@@ -1,8 +1,8 @@
 # Security Reporting Process
 
-Please, report any security issue to `opensourcegroup@qubership.org` where the issue will be triaged appropriately.
+Please, report any security issue to `opensourcegroup@netcracker.com` where the issue will be triaged appropriately.
 
-If you know of a publicly disclosed security vulnerability please IMMEDIATELY email `opensourcegroup@qubership.org`
+If you know of a publicly disclosed security vulnerability please IMMEDIATELY email `opensourcegroup@netcracker.com`
 to inform the team about the vulnerability, so we may start the patch, release, and communication process.
 
 # Security Release Process

docs/public/disasterRecovery.md

@@ -83,7 +83,7 @@ backupDaemon:
   persistentVolume: null
   s3:
     enabled: true
-    url: "http://s3-storage.environment.openshift.sdntest.qubership.org"
+    url: "http://s3-storage.environment.openshift.sdntest.netcracker.com"
     bucket: "rabbitmqbucket"
     keyId: "s3keyid"
     keySecret: "s3keysecret"

docs/public/installation.md

@@ -53,7 +53,7 @@ To avoid using `cluster-wide` rights during the deployment, the following condit
     name: deploy-user-role
   rules:
     - apiGroups:
-        - qubership.org
+        - netcracker.com
       resources:
         - "*"
       verbs:
@@ -1411,7 +1411,7 @@ For example:
 kubect get rabbitmqservices rabbitmq -o yaml
 ```
 
-## Deployer Job Failed With Unknown Fields in Rabbitmqservices.qubership.org
+## Deployer Job Failed With Unknown Fields in Rabbitmqservices.netcracker.com
 
 It can be an issue with CRD changes. Refer to [CRD Upgrade](#crd-upgrade) for details.
 

docs/sources/crds/oc311crd.yaml

@@ -1,10 +1,10 @@
 apiVersion: apiextensions.k8s.io/v1beta1
 kind: CustomResourceDefinition
 metadata:
-  name: rabbitmqservices.qubership.org
+  name: rabbitmqservices.netcracker.com
 spec:
   scope: Namespaced
-  group: qubership.org
+  group: netcracker.com
   version: v1alpha
   subresources:
     status: {}

operator/charts/helm/rabbitmq/crds/crd.yaml

@@ -2,10 +2,10 @@ apiVersion: apiextensions.k8s.io/v1
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    crd.qubership.org/version: 0.10.0
-  name: rabbitmqservices.qubership.org
+    crd.netcracker.com/version: 0.10.0
+  name: rabbitmqservices.netcracker.com
 spec:
-  group: qubership.org
+  group: netcracker.com
   scope: Namespaced
   names:
     kind: RabbitMQService

operator/charts/helm/rabbitmq/values.yaml

@@ -26,7 +26,7 @@ global:
   securityContext: {}
   disableRunAsNonRoot: false
   disasterRecovery:
-    siteManagerApiGroup: "qubership.org"
+    siteManagerApiGroup: "netcracker.com"
 
 operator:
   resources:
@@ -39,7 +39,7 @@ operator:
   customLabels: {}
   securityContext: {}
   priorityClassName: ""
-  apiGroup: "qubership.org"
+  apiGroup: "netcracker.com"
   pullPolicy: "Always"
   restartScheduler:
     dockerImage: bitnami/kubectl:1.30.6

operator/deploy/cr.yaml

@@ -1,4 +1,4 @@
-apiVersion: qubership.org/v1
+apiVersion: netcracker.com/v1
 kind: RabbitMQService
 metadata:
   name: rabbitmq-service

operator/deploy/crd.yaml

@@ -1,10 +1,10 @@
 apiVersion: apiextensions.k8s.io/v1beta1
 kind: CustomResourceDefinition
 metadata:
-  name: rabbitmqservices.qubership.org
+  name: rabbitmqservices.netcracker.com
 spec:
   scope: Namespaced
-  group: qubership.org
+  group: netcracker.com
   version: v1
   names:
     kind: RabbitMQService

operator/deploy/deploy.md

@@ -6,7 +6,7 @@ To deploy RabbitMQ with an operator in OpenShift/Kubernetes:
 1. Replace the `REPLACE_IMAGE` value in the **/deploy/operator.yaml** file with the required operator image. You can replace the image using the following command:
 
    ```
-   sed -i 's|REPLACE_IMAGE|artifactorycn.qubership.org:17008/thirdparty/thirdparty.platform.services_rabbitmq:rabbitmq-operator_latest_operator|g' deploy/operator.yaml
+   sed -i 's|REPLACE_IMAGE|artifactorycn.netcracker.com:17008/thirdparty/thirdparty.platform.services_rabbitmq:rabbitmq-operator_latest_operator|g' deploy/operator.yaml
    ``` 
 
    You can also specify the `LOGLEVEL` environment variable in order to set the logging level of the operator in the **/deploy/operator.yaml** file. Another available environment variable is `OPERATOR_DELETE_RESOURCES`, which specifies whether the operator should delete all RabbitMQ resources when the RabbitMQ Custom Resource (CR) is deleted. When not specified, the value is `False`. **Warning:** If `OPERATOR_DELETE_RESOURCES` is set to `True`, the RabbitMQ operator must be up and running when you are deleting the CR. Otherwise, the delete operation may be stuck for an extended period of time, and may stop you from deleting the namespace. 

operator/deploy/role.yaml

@@ -5,7 +5,7 @@ metadata:
   name: rabbitmq-operator
 rules:
 - apiGroups:
-  - qubership.org
+  - netcracker.com
   resources:
   - "*"
   verbs: