Fix to replace NetCracker-Specific

Author: Clive Dias

README.md

@@ -31,30 +31,6 @@
   helm install rabbitmq ./ -f sample.yaml -n <TARGET_NAMESPACE>
   ```
 
-#### Application deployer
-
-1. Build a manifest using [Manifest building guide](#manifest).
-2. Prepare Cloud Deploy Configuration:
-   1. Go to the [APP-Deployer infrastructure configuration](https://cloud-deployer.qubership.org/job/INFRA/job/groovy.deploy.v3/).
-   2. INFRA --> Clouds -->  find your cloud --> Namespaces --> find your namespace.
-   3. If the namespace is **not presented** then:
-      1. Click `Create` button and specify: namespace and credentials. 
-      2. Click `Save`.
-      3. Go to your namespace configuration and specify the parameters for service installing.
-   4. If the namespace is presented then: just check the parameters or change them.
-3. To deploy service using APP-Deployer:
-   1. Go to the [APP-Deployer groovy deploy page](https://cloud-deployer.qubership.org/job/INFRA/job/groovy.deploy.v3/).
-   2. Go to the `Build with Parameters` tab.
-   3. Specify:
-      1. Project: it is your cloud and namespace.
-      2. The list is based on the information from the [APP-Deployer infrastructure configuration](https://cloud-deployer.qubership.org/job/INFRA/job/groovy.deploy.v3/). 
-      3. Deploy mode - `Rolling Update`. 
-      4. Artifact descriptor version --> the **application manifest**.
-
-#### ArgoCD
-
-The information about ArgoCD deployment can be found in [Platform ArgoCD guide](https://bass.qubership.org/display/PLAT/ArgoCD+guide).
-
 ### Smoke tests
 
 There is no smoke tests.
@@ -72,36 +48,6 @@ There are no well-defined rules for troubleshooting, as each task is unique, but
 * Logs from all RabbitMQ service pods.
 
 Also, developer can take a look on [Troubleshooting guide](/docs/public/troubleshooting.md).
-
-#### APP-Deployer job typical errors
-
-##### Application does not exist in the CMDB
-
-The error like "ERROR: Application does not exist in the CMDB" means that the APP-Deployer doesn't have
-configuration related to the "service-name" from application manifest.
-
-**Solution**: check that the correct manifest is used.
-
-##### CUSTOM_RESOURCE timeout
-
-The error like "CUSTOM_RESOURCE timeout" means the service was deployed to the namespace, but the Custom Resource doesn't have SUCCESS status.
-Usually, it is related to the service state - it might be unhealthy or repeatedly crushing.
-
-**Solution**: there is no ready answer, need to go to namespace & check service state, operator logs to find a root cause and fix it.
-
-## CI/CD
-
-The main CI/CD pipeline is design to automize all basic developer routine start from code quality and finish with
-deploying to stand k8s cluster.
-
-1. `linter` - stage with jobs that run different linter to check code & documentation.
-2. `build` - stage with jobs that build docker images for RabbitMQ components using DP-Builder.
-3. `manifest` - stage with jobs that build manifest for current branch or release manifest using DP-Builder.
-4. `cloudDeploy` - optional stage with job which deploys the manifest to `ci-master`, `miniha`, `k8s1/2` clusters using APP-Deployer.
-5. `cloudDeployTests` - stage with job which deploys manifest with integration tests using APP-Deployer.
-6. `manifestValidation` - optional stage with jobs that validate manifest (check is it ready to be released) and check
-   vulnerabilities.
-
 ## Evergreen strategy
 
 To keep the component up to date, the following activities should be performed regularly:
@@ -115,5 +61,3 @@ To keep the component up to date, the following activities should be performed r
 * [Installation guide](/docs/public/installation.md).
 * [Troubleshooting guide](/docs/public/troubleshooting.md).
 * [Internal Developer Guide](/docs/internal/developing.md).
-* [Cloud INFRA Development process](https://bass.qubership.org/display/PLAT/Cloud+Infra+Platform+services%3A+development+process).
-* [ArgoCD User guide](https://bass.qubership.org/display/PLAT/ArgoCD+guide)

docs/data/capabilities.yaml

@@ -24,12 +24,7 @@ Installation:
       - Kubernetes
       - Openshift
     FullyAutomated: yes
-  AppDeployer:
-    Supported: yes
-    Environment:
-      - Kubernetes
-      - Openshift
-    FullyAutomated: yes
+  
   Ansible:
     Supported: yes
     Environment:
@@ -43,13 +38,7 @@ Upgrade:
       - Openshift
     FullyAutomated: yes
     Downtime: no
-  AppDeployer:
-    Supported: yes
-    Environment:
-      - Kubernetes
-      - Openshift
-    FullyAutomated: yes
-    Downtime: no
+
   Ansible:
     Supported: yes
     Environment: