remove console-backend-service (kyma-project#12306)

* remove console-backend-service

* bump images

* remove reference to cbs from main readme.md

* remove cbs from CODEOWNERS

* update to please governance test

* remove unnecessary command

* revert change to application gateway

CODEOWNERS

@@ -79,9 +79,6 @@
 # The `application-connector-ingress` chart
 /resources/application-connector-ingress/ @akgalwas @janmedrek @franpog859 @Maladie @rafalpotempa @koala7659 @ralikio @everesio
 
-# The `console` subchart
-/resources/console/ @dariadomagala @parostatkiem @akucharska @Wawrzyn321 @kwiatekus
-
 # The `dex` subchart
 /resources/dex/ @strekm @werdes72 @Tomasz-Smelcerz-SAP @mjakobczyk @dariusztutaj
 
@@ -195,13 +192,6 @@ components/etcd-tls-setup-job/ @PK85 @piotrmiskiewicz @ksputo @szwedm @voigt @wo
 # Application broker Component
 /components/application-broker/ @PK85 @piotrmiskiewicz @ksputo @szwedm @voigt @wozniakjan @adamwalach @lilitgh
 
-# Console Backend Service Component
-/components/console-backend-service/ @dariadomagala @parostatkiem @akucharska @Wawrzyn321 @kwiatekus
-/components/console-backend-service/internal/gqlschema @dariadomagala @parostatkiem @akucharska @Wawrzyn321 @kwiatekus @m00g3n @pPrecel @dbadura @tgorgol @rJankowski93
-/components/console-backend-service/internal/domain/*.go @dariadomagala @parostatkiem @akucharska @Wawrzyn321 @kwiatekus @m00g3n @pPrecel @dbadura @tgorgol @rJankowski93
-/components/console-backend-service/internal/domain/serverless @m00g3n @pPrecel @dbadura @tgorgol @rJankowski93
-/components/console-backend-service/internal/domain/rafter @m00g3n @pPrecel @dbadura @tgorgol @rJankowski93
-
 # Connector Service Component
 /components/connector-service/ @akgalwas @janmedrek @franpog859 @Maladie @rafalpotempa @koala7659 @ralikio
 
@@ -287,9 +277,6 @@ components/etcd-tls-setup-job/ @PK85 @piotrmiskiewicz @ksputo @szwedm @voigt @wo
 # apiserver-proxy tests
 /tests/integration/apiserver-proxy/ @strekm @werdes72 @Tomasz-Smelcerz-SAP @mjakobczyk @dariusztutaj
 
-# Console Backend Service tests
-/tests/console-backend-service/ @dariadomagala @parostatkiem @akucharska @Wawrzyn321 @kwiatekus
-
 # Rafter tests
 /tests/rafter/ @m00g3n @pPrecel @dbadura @tgorgol @rJankowski93
 

README.md

@@ -34,7 +34,7 @@ Kyma comes with the ready-to-use code snippets that you can use to test the exte
 ## Development
 
 Develop on your remote repository forked from the original repository in Go.
-See the example that uses the [`console-backend-service`](components/console-backend-service) project located in the `components` directory but applies to any Go project. This set of instructions uses the recommended [`git workflow`](https://kyma-project.io/community/contributing/#git-workflow-git-workflow) and the general [contribution flow](https://kyma-project.io/community/contributing/#contributing-rules-contributing-rules-contribute-code-or-content). Read also the [`CONTRIBUTING.md`](CONTRIBUTING.md) document that includes the contributing rules specific for this repository.
+Read also the [`CONTRIBUTING.md`](CONTRIBUTING.md) document that includes the contributing rules specific for this repository.
 
 Follow these steps:
 
@@ -50,25 +50,16 @@ Follow these steps:
 
     Follow the steps described in the [`git-workflow.md`](https://kyma-project.io/community/contributing/03-git-workflow/) document to configure your fork.
 
-3. Install dependencies.
-
-    Go to the main directory of the project in your workspace location and install the required dependencies:
-
-    ```bash
-    cd components/console-backend-service
-    dep ensure -vendor-only
-    ```
-
-4. Build the project.
+3. Build the project.
 
     Every project runs differently. Follow instructions in the main `README.md` document of the given project to build it.
 
-5. Create a branch and start to develop.
+4. Create a branch and start to develop.
 
     Do not forget about creating unit and acceptance tests if needed. For the unit tests, follow the instructions specified in the main `README.md` document of the given project. For the details concerning the acceptance tests, go to the corresponding directory inside the `tests` directory.
     Find the information on how to run changes on the cluster without a Docker image in the [Develop a service locally without using Docker](https://kyma-project.io/docs/kyma/latest/03-tutorials/01-develop-service-local-no-docker-kyma/) document.
 
-6. Test your changes.
+5. Test your changes.
 
 ## Kyma users
 

components/application-gateway/README.md

@@ -84,17 +84,6 @@ See an example in `pkg/apis/istio/v1alpha2`.
 
 3. Go to the project root directory and run `./hack/update-codegen.sh`. The script generates a new client in `pkg/apis/client/clientset`.
 
-
-### Contract between the Application Gateway and the Console Backend Service
-
-The Console Backend Service must check the status of the Application Gateway instance that represents the Application.
-In the current solution, the Console Backend Service iterates through services to find those which match the criteria, and then uses the health endpoint to determine the status.
-The Console Backend Service has the following obligatory requirements:
-- The Kubernetes service uses the `application` key, with the value as the name of the Application.
-- The Kubernetes service contains one port with the `http-api-port` name. The system uses this port for the status check.
-- Find the Kubernetes service in the `kyma-integration` Namespace. You can change its location in the `console-backend` chart configuration.
-- The `/v1/health` endpoint returns a status of `HTTP 200`. Any other status code indicates the service is not healthy.
-
 ### Contribution
 
 To learn how you can contribute to this project, see the [Contributing](/CONTRIBUTING.md) document.

components/application-operator/charts/application/templates/authorization-policy.yaml

@@ -37,14 +37,4 @@ spec:
               - DELETE
             paths:
               - /{{ .Release.Name }}/v1/metadata*
-    - from:
-      - source:
-          principals:
-          - cluster.local/ns/kyma-system/sa/{{ .Values.authorizationPolicy.serviceAccount.consoleBackendService }}
-      to:
-      - operation:
-          methods:
-          - GET
-          paths:
-          - /v1/health
 {{- end }}

components/application-operator/charts/application/values.yaml

@@ -61,10 +61,5 @@ eventPublisherProxy:
     name: eventing-event-publisher-proxy
     namespace: kyma-system
 
-# console-backend is a ServiceAccount which is installed as a part of *core* chart
-authorizationPolicy:
-  serviceAccount:
-    consoleBackendService: console-backend
-
 podSecurityPolicy:
   runAsUser: 1000