Delete unverified data

README.md

@@ -124,7 +124,7 @@ permissions on entity group with the verbs `get`, `patch` and resources `<resour
 For example, permissions for write status in Custom Resource:
 ```
 - apiGroups:
-  - netcracker.com
+  - qubership.org
   resources:
   - platformmonitorings/status
   verbs:
@@ -134,15 +134,15 @@ For example, permissions for write status in Custom Resource:
 
 To write status to some k8s entity you should specify the entity. There are two ways to do this. The first one is to specify
 full path. For example, you have `ZooKeeperService` custom resource which has
-`metadata.selfLink` field with value - `/apis/netcracker.com/v1/namespaces/zookeeper-service/zookeeperservices/zookeeper`,
+`metadata.selfLink` field with value - `/apis/qubership.org/v1/namespaces/zookeeper-service/zookeeperservices/zookeeper`,
 in the current approach you should specify `STATUS_CUSTOM_RESOURCE_PATH` environment variable with value from `selfLink` without
 `apis` prefix and `namespaces` part:
 ```
-STATUS_CUSTOM_RESOURCE_PATH=netcracker.com/v1/zookeeper-service/zookeeperservices/zookeeper
+STATUS_CUSTOM_RESOURCE_PATH=qubership.org/v1/zookeeper-service/zookeeperservices/zookeeper
 ```
 The second approach is to point the path in parts using the following environment variables:
 ```
-STATUS_CUSTOM_RESOURCE_GROUP=netcracker.com
+STATUS_CUSTOM_RESOURCE_GROUP=qubership.org
 STATUS_CUSTOM_RESOURCE_VERSION=v1 
 STATUS_CUSTOM_RESOURCE_NAMESPACE=zookeeper-service
 STATUS_CUSTOM_RESOURCE_PLURAL=zookeeperservices 

demo/README.md

@@ -7,9 +7,9 @@ Robot Framework file (*.robot) with keywords and test cases, special python file
 `tests_holder.robot` file contains Robot Framework test cases. You can add new test cases or keywords to test `PlatformLibrary`.
 To configure `docker-compose.yml` file you should configure Kubernetes configuration file (set environment, context, etc.),
 mount you host folder which contains "./kube/config" file (or custom kubeconfig), specify `KUBECONFIG` environment variable
-with path to mounted kubeconfig file. For example, you have the following kubeconfig file: C:/Users/aaaa0000/.kube/config,
+with path to mounted kubeconfig file. For example, you have the following kubeconfig file: C:/Users/test/.kube/config,
 you can mount disk "C" to "/mnt" directory in `volumes` block of docker-compose.yml (- C:/:/mnt) and specify `KUBECONFIG` 
-environment variable as /mnt/Users/aaaa0000/.kube/config:
+environment variable as /mnt/Users/test/.kube/config:
 ```yaml
 version: '2'
 services:
@@ -24,7 +24,7 @@ services:
       - ./output:/opt/robot/output
       - C:/:/mnt
     environment:
-      - KUBECONFIG=/mnt/Users/aaaa0000/.kube/config
+      - KUBECONFIG=/mnt/Users/test/.kube/config
       - DEBUG=true
     command: ["run-robot"]
 ```

demo/docker-compose.yml

@@ -15,7 +15,7 @@ services:
       - DEBUG=true
       #variables for writing status in CR
 #      - STATUS_WRITING_ENABLED=true
-#      - STATUS_CUSTOM_RESOURCE_GROUP=netcracker.com
+#      - STATUS_CUSTOM_RESOURCE_GROUP=qubership.org
 #      - STATUS_CUSTOM_RESOURCE_VERSION=v1
 #      - STATUS_CUSTOM_RESOURCE_NAMESPACE=zookeeper-service
 #      - STATUS_CUSTOM_RESOURCE_PLURAL=zookeeperservices

demo/docker/Dockerfile

@@ -1,3 +1,3 @@
-FROM product/prod.platform.streaming_docker-integration-tests:latest
+FROM ghcr.io/netcracker/docker-integration-tests:main
 
 COPY docker/robot  ${ROBOT_HOME}