feat: return api group

mrMigles · mrMigles · commit 5973fb644c36 · 2025-10-19T06:44:16.000Z
diff --git a/SECURITY.md b/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
diff --git a/docs/public/TLS.md b/docs/public/TLS.md
@@ -220,4 +220,4 @@ Automatic re-encrypt Route creation is not supported out of box, need to perform
 **NOTE**: If you can't access the rabbitmq host after Route creation because of "too many redirects" error, then one of the possible root
 causes is there is HTTP traffic between balancers and the cluster. To resolve that issue it's necessary to add the Route name to
 the exception list at the balancers,
-[see documentation](https://git.qubership.org/PROD.Platform.HA/ocp-4-support/-/blob/master/documentation/Maintenance.md#configure-tls-offload-at-the-load-balancer-nodes)
+[see documentation](https://git.netcracker.com/PROD.Platform.HA/ocp-4-support/-/blob/master/documentation/Maintenance.md#configure-tls-offload-at-the-load-balancer-nodes)
diff --git a/docs/public/disasterRecovery.md b/docs/public/disasterRecovery.md
@@ -42,7 +42,7 @@ In Disaster Recovery scheme the `REGION` environment variable is automatically a
 Each backup will contain information about `REGION` as `region` custom parameter. If backup daemon tries to restore backup on `active`
 side it will restore the latest backup from the `other` region. The `standby` to `active` switchover process will be failed if
 there is no backup from the other region. But, the restore process will be skipped in this case without fail if `noWait` site manager parameter is `true`.
-For more information about site manager `noWait` parameter, refer to [Site Manager](https://git.qubership.org/PROD.Platform.HA/github.sync/DRNavigator/-/blob/main/README.md).
+For more information about site manager `noWait` parameter, refer to [Site Manager](https://git.netcracker.com/PROD.Platform.HA/github.sync/DRNavigator/-/blob/main/README.md).
 
 ## Configuration Example
 
@@ -84,7 +84,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"
@@ -139,7 +139,7 @@ backupDaemon:
 You can perform the switchover using the `SiteManager` functionality or RabbitMQ disaster recovery REST server API.
 
 <!-- #GFCFilterMarkerStart# -->
-For more information about `SiteManager`, refer to [Site Manager](https://git.qubership.org/PROD.Platform.HA/github.sync/DRNavigator/-/blob/main/README.md) article.
+For more information about `SiteManager`, refer to [Site Manager](https://git.netcracker.com/PROD.Platform.HA/github.sync/DRNavigator/-/blob/main/README.md) article.
 <!-- #GFCFilterMarkerEnd# -->
 
 If you want to perform a switchover manually, you need to switch `active` RabbitMQ cluster to `standby` mode and then switch `standby` RabbitMQ cluster to `active` mode.
diff --git a/docs/public/installation.md b/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:
@@ -1410,7 +1410,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.
 
diff --git a/docs/sources/crds/oc311crd.yaml b/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: {}
diff --git a/operator/charts/helm/rabbitmq/crds/crd.yaml b/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
diff --git a/operator/charts/helm/rabbitmq/values.yaml b/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
diff --git a/operator/deploy/cr.yaml b/operator/deploy/cr.yaml
@@ -1,4 +1,4 @@
-apiVersion: qubership.org/v1
+apiVersion: netcracker.com/v1
 kind: RabbitMQService
 metadata:
   name: rabbitmq-service
diff --git a/operator/deploy/crd.yaml b/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
diff --git a/operator/deploy/deploy.md b/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. 
diff --git a/operator/deploy/role.yaml b/operator/deploy/role.yaml
@@ -5,7 +5,7 @@ metadata:
   name: rabbitmq-operator
 rules:
 - apiGroups:
-  - qubership.org
+  - netcracker.com
   resources:
   - "*"
   verbs:
diff --git a/operator/operator-robot-image/robot/tests/lib/CloudResourcesLibrary.py b/operator/operator-robot-image/robot/tests/lib/CloudResourcesLibrary.py
@@ -58,7 +58,7 @@ def change_rabbitmq_password_with_operator(self, username, password):
 
     def get_custom_resource(self):
         return self.k8s_lib.get_namespaced_custom_object_status(
-            group='qubership.org',
+            group='netcracker.com',
             version=cr_version,
             namespace=self.namespace,
             plural='rabbitmqservices',
@@ -73,7 +73,7 @@ def set_secret_change_field(self, secret_change):
     def update_custom_resource(self, body):
 
         self._custom_objects_api.patch_namespaced_custom_object(
-            group='qubership.org',
+            group='netcracker.com',
             version=cr_version,
             namespace=self.namespace,
             plural='rabbitmqservices',
diff --git a/operator/operator-robot-image/robot/tests/setup.py b/operator/operator-robot-image/robot/tests/setup.py
@@ -19,7 +19,7 @@
     version='0.0.1',
     packages=find_packages(),
     author='Vitalii Solodilov',
-    author_email='vitalii.solodilov@qubership.org',
+    author_email='vitalii.solodilov@netcracker.com',
     classifiers=[
         'Programming Language:: Python:: 3.6'
     ]
diff --git a/operator/src/handler.py b/operator/src/handler.py
@@ -87,7 +87,7 @@ def __init__(self, obj):
 tests_name = 'rabbitmq-integration-tests'
 nodeport_service_name = 'rabbitmq-nodeport'
 cr_version = "v2"
-api_group = os.getenv("API_GROUP", "qubership.org")
+api_group = os.getenv("API_GROUP", "netcracker.com")
 IN_PROGRESS = "In progress"
 SUCCESSFUL = "Successful"
 FAILED = "Failed"

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-apiVersion: qubership.org/v1`
	`1`	`+apiVersion: netcracker.com/v1`
`2`	`2`	`kind: RabbitMQService`
`3`	`3`	`metadata:`
`4`	`4`	`name: rabbitmq-service`