Merge branch 'main' into upgrade_vbatts_tar-split

docs/index.md

@@ -60,8 +60,6 @@
 
 [Prow Test Clusters](/docs/prow/test-clusters.md) - This document gathers information about test clusters that Prow jobs build. All test clusters are built in the `sap-kyma-prow-workloads` project.
 
-[Tide Introduction](/docs/prow/tide-introduction-notes.md) - Along with the Prow upgrade, we want to introduce Tide for merging the PRs automatically.
-
 [Prow Workload Clusters](/docs/prow/workload-clusters.md) - This document describes workload clusters on which Prow schedules Pods to execute the logic of a given Prow job. All workload clusters are aggregated under the `kyma-prow` Google Cloud project. We use two workload clusters for trusted and untrusted Prow jobs.
 
 [Prow Runtime Images](/images/README.md) - This directory contains images that can be used as runtime images for all ProwJobs in Kyma's Prow Instance.

docs/prow/authorization.md

@@ -42,7 +42,6 @@ Following roles exist on Prow cluster:
 | **plank** | - `prowjobs.prow.k8s.io` <br> - `pods` | create, list, update <br> create, list, delete |
 | **sinker** | - `prowjobs.prow.k8s.io` <br> - `pods` | delete, list <br> delete, list |
 | **hook** | - `prowjobs.prow.k8s.io` <br> - `configmaps` | create, get <br> get, update |
-| **tide** | - `prowjobs.prow.k8s.io` |  create, list  |
 | **crier** | - `prowjobs.prow.k8s.io` | get, watch <br> list, patch |
 
 ## User Permissions on GitHub

docs/prow/prow-architecture.md

@@ -38,9 +38,6 @@ Branch Protector is a Prow component that is responsible for defining branch pro
 ### gcsweb
 gcsweb is a lightweight web frontend for GCS which allows you to access the content of the **artifacts** tab in Spyglass without the need to log in. For more information on gcsweb read [this](https://github.com/kubernetes/k8s.io/tree/main/apps/gcsweb) document.
 
-### Tide
-Tide is a Prow component that automatically checks the acceptance criteria against opened PRs in the repository. If the given PR passes all the criteria, Tide automatically merges it.
-
 ## Plugins
 There are different kinds of plugins that react to GitHub events forwarded by the Hook component. Plugins are configured per repository using `plugins.yaml`.
 For more information about installed plugins in the `kyma-project` organisation, refer to the [plugins.yaml](../../prow/plugins.yaml) file.

docs/prow/prow-cluster-update.md

@@ -13,7 +13,6 @@ To update a Prow cluster follow these steps:
     * gcr.io/k8s-prow/sinker
     * gcr.io/k8s-prow/deck
     * gcr.io/k8s-prow/horologium
-    * gcr.io/k8s-prow/tide
 3. Copy the commit ID into a comment at the top of the file to keep track of the current release used for the deployments.
 4. Use your preferred diff tool to check and copy the stability update in a Prow component and additional configurations on existing components.
 5. Open both [`config.yaml`](../../prow/config.yaml) in the current project and [`config.yaml`](https://github.com/kubernetes/test-infra/blob/2c8e0dbb96b4c1a86d42275dfbed5474a6d05def/prow/config.yaml) in the Kubernetes project and copy new tags for these containers:

prow/cluster/components/deck_deployment.yaml

@@ -44,7 +44,6 @@ spec:
           - name: http
             containerPort: 8080
         args:
-        - --tide-url=http://tide/
         - --hook-url=http://hook:8888/plugin-help
         - --redirect-http-to=status.build.kyma-project.io
         - --oauth-url=/github-login

prow/cluster/deploy.sh

@@ -41,9 +41,6 @@ prow_components=(
 "statusreconciler_rbac.yaml"
 "statusreconciler_deployment.yaml"
 "status-kyma-prow_managedcertificate.yaml"
-"tide_rbac.yaml"
-"tide_deployment.yaml"
-"tide_service.yaml"
 "tls-ing_ingress.yaml"
 "web_server_deployment.yaml"
 )