From cd12c1a051a4cc9f2d2e0a35222729a06e3dafa1 Mon Sep 17 00:00:00 2001
From: Pranav Patil <pranav.patil@netcracker.com>
Date: Wed, 4 Feb 2026 12:21:49 +0500
Subject: [PATCH 1/2] doc-update

---
 documentation/public/architecture.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/public/architecture.md b/documentation/public/architecture.md
index 40388248..3228289f 100644
--- a/documentation/public/architecture.md
+++ b/documentation/public/architecture.md
@@ -126,7 +126,7 @@ services of the standby Kubernetes cluster.
 CR SiteManager description:
 
 ```yaml
-apiVersion: qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: <SERVICE>
@@ -170,7 +170,7 @@ for details;
 Example for `postgres` service:
 
 ```yaml
-apiVersion: qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   annotations:

From d8e057b95f7f0689d035112dbbb4db3e4e38f873 Mon Sep 17 00:00:00 2001
From: Pranav Patil <pranav.patil@netcracker.com>
Date: Wed, 4 Feb 2026 12:29:45 +0500
Subject: [PATCH 2/2] doc-update

---
 ...end-service-names-for-multiple-services.md | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/documentation/internal/design/2-extend-service-names-for-multiple-services.md b/documentation/internal/design/2-extend-service-names-for-multiple-services.md
index b77050e2..173e82bb 100644
--- a/documentation/internal/design/2-extend-service-names-for-multiple-services.md
+++ b/documentation/internal/design/2-extend-service-names-for-multiple-services.md
@@ -75,7 +75,7 @@ Suppose we have two services `serviceA` and `serviceB`, dependent from `serviceA
 
 In services helms:
 ```yaml
-apiVersion: legacy.qubership.org/v2
+apiVersion: netcracker.com/v2
 kind: SiteManager
 metadata:
   name: {{ .Values.namespace }}-serviceA
@@ -84,7 +84,7 @@ spec:
     after: []
     before: []
 ---
-apiVersion: legacy.qubership.org/v2
+apiVersion: netcracker.com/v2
 kind: SiteManager
 metadata:
   name: {{ .Values.namespace }}-serviceB
@@ -97,7 +97,7 @@ spec:
 
 In cluster:
 ```yaml
-apiVersion: legacy.qubership.org/v2
+apiVersion: netcracker.com/v2
 kind: SiteManager
 metadata:
   name: ns1-serviceA
@@ -107,7 +107,7 @@ spec:
     after: []
     before: []
 ---
-apiVersion: legacy.qubership.org/v2
+apiVersion: netcracker.com/v2
 kind: SiteManager
 metadata:
   name: ns2-serviceB
@@ -123,7 +123,7 @@ spec:
 In services helms nothing changes;  
 In cluster:
 ```yaml
-apiVersion: legacy.qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: ns1-serviceA
@@ -133,7 +133,7 @@ spec:
     after: []
     before: []
 ---
-apiVersion: legacy.qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: ns2-serviceB
@@ -148,7 +148,7 @@ spec:
 #### 2. After changing CR names in services helms and redeploy
 In services helms:
 ```yaml
-apiVersion: legacy.qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: serviceA
@@ -157,7 +157,7 @@ spec:
     after: []
     before: []
 ---
-apiVersion: legacy.qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: serviceB
@@ -169,7 +169,7 @@ spec:
 ```
 In cluster:
 ```yaml
-apiVersion: legacy.qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: serviceA
@@ -179,7 +179,7 @@ spec:
     after: []
     before: []
 ---
-apiVersion: legacy.qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: serviceB
@@ -268,7 +268,7 @@ on different sites:
 
 We can add special optional field to define service name for opponent site, e.g. for `site-1`:
 ```yaml
-apiVersion: legacy.qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: sm-dummy
@@ -297,7 +297,7 @@ In sm-client this field can be used to make links between services with differen
 
 We can add special optional field to override service name, e.g. for `site-1`:
 ```yaml
-apiVersion: legacy.qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: sm-dummy
@@ -335,7 +335,7 @@ spec:
 
 We can add special optional field to turn on/off adding namespace to service name (`isUniqueOnCluster`, default is false):
 ```yaml
-apiVersion: legacy.qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: sm-dummy
@@ -374,7 +374,7 @@ is `<cr-name>` like now:
 We can add namespaces only for services with specific volumes (e.g. not stateful). As result, services with 
 another module will have the same name:
 ```yaml
-apiVersion: legacy.qubership.org/v3
+apiVersion: netcracker.com/v3
 kind: SiteManager
 metadata:
   name: sm-dummy