Test Vale errors and warnings

.coderabbit.yml

@@ -2,3 +2,30 @@
 reviews:
   path_filters:
     - "!website/**"
+  poem: false
+  high_level_summary: false
+  changed_files_summary: false
+  sequence_diagrams: false
+  estimate_code_review_effort: false
+  assess_linked_issues: false
+  related_issues: false
+  related_prs: false
+  suggested_labels: false
+  suggested_reviewers: false
+  review_status: false
+  collapse_walkthrough: true
+  request_changes_workflow: false
+  auto_review:
+    enabled: true
+    drafts: false
+    auto_incremental_review: true
+    auto_pause_after_reviewed_commits: 0
+  enable_prompt_for_ai_agents: false
+  path_instructions:
+    - path: "website/**/*.md"
+      instructions: |
+        When reviewing this file, look at the Vale annotations from the GitHub Checks. For each Vale error or warning annotation on a changed line: read the flagged line in context and judge whether the finding is a real issue. Vale sometimes reports false positives — only create a committable suggestion if it is a genuine error or warning. If it is a false positive, add a comment explaining why it is a false positive and how to avoid it (for example, by rephrasing or by adding the term to the appropriate Vale vocabulary).
+  tools:
+    github-checks:
+      enabled: true
+      timeout_ms: 90000

.github/workflows/vale.yml

@@ -15,8 +15,6 @@ concurrency:
 
 permissions:
   contents: read
-  checks: write
-  pull-requests: write
 
 jobs:
   vale:
@@ -26,11 +24,23 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v4
 
-      - name: Vale
-        uses: vale-cli/vale-action@v2.1.1
+      - name: Get changed files
+        id: changed-files
+        uses: tj-actions/changed-files@v45
         with:
-          files: website/
-          vale_flags: "--minAlertLevel=warning"
-          reporter: github-pr-review
-          fail_on_error: true
-          filter_mode: added
+          files: |
+            website/**/*.md
+          files_ignore: |
+            website/about/legal-disclosure.md
+            website/archived/**
+
+      - name: Install Vale
+        if: steps.changed-files.outputs.any_changed == 'true'
+        run: |
+          wget -qO vale.tar.gz https://github.com/errata-ai/vale/releases/download/v3.14.1/vale_3.14.1_Linux_64-bit.tar.gz
+          tar -xzf vale.tar.gz vale
+          sudo mv vale /usr/local/bin/vale
+
+      - name: Run Vale
+        if: steps.changed-files.outputs.any_changed == 'true'
+        run: vale --minAlertLevel=error ${{ steps.changed-files.outputs.all_changed_files }}

website/documentation/guides/administer-shoots/create-delete-shoot.md

@@ -7,17 +7,17 @@ scope: operator
 
 ## Create a Shoot Cluster
 
-As you have already prepared an [example Shoot manifest](https://github.com/gardener/gardener/blob/master/example/90-shoot.yaml) in the steps described in the development documentation, please open another Terminal pane/window with the `KUBECONFIG` environment variable pointing to the Garden development cluster and send the manifest to the Kubernetes API server:
+As you have already prepared an [example Shoot manifest](https://github.com/gardener/gardener/blob/master/example/90-shoot.yaml) in the steps described in the development documentation, please open another Terminal pane/window with the `KUBECONFIG` environment variable pointing to the Garden development cluster and send the manifest to the kubernetes API server:
 
 ```bash
 kubectl apply -f your-shoot-aws.yaml
 ```
 
-You should see that Gardener has immediately picked up your manifest and has started to deploy the Shoot cluster.
+You should see that gardener has immediately picked up your manifest and has started to deploy the controlplane of the Shoot cluster.
 
 In order to investigate what is happening in the Seed cluster, please download its proper Kubeconfig yourself (see next paragraph). The namespace of the Shoot cluster in the Seed cluster will look like that: `shoot-johndoe-johndoe-1`, whereas the first `johndoe` is your namespace in the Garden cluster (also called "project") and the `johndoe-1` suffix is the actual name of the Shoot cluster.
 
-To connect to the newly created Shoot cluster, you must download its Kubeconfig as well. Please connect to the proper Seed cluster, navigate to the Shoot namespace, and download the Kubeconfig from the `kubecfg` secret in that namespace.
+To connect to the newly created Shoot cluster, the user must download its Kubeconfig as well. Please connect to the proper Seed cluster, navigate to the Shoot namespace, and download the Kubeconfig from the `kubecfg` secret in that namespace. This requires a SSH connection to the seed. Note that a VM is also provisioned per worker pool.
 
 ## Delete a Shoot Cluster
 
@@ -27,7 +27,7 @@ In order to delete your cluster, you have to set an annotation confirming the de
 ./hack/usage/delete shoot johndoe-1 johndoe
 ```
 
-(the `hack` bash script can be found at [GitHub](https://github.com/gardener/gardener/blob/master/hack/usage/delete))
+(the `hack` bash script can be found at [Github](https://github.com/gardener/gardener/blob/master/hack/usage/delete))
 
 ## Configure a Shoot Cluster Alert Receiver
 
@@ -36,3 +36,11 @@ The receiver of the Shoot alerts can be configured from the `.spec.monitoring.al
 The alerting for the Shoot clusters is handled by the Prometheus Alertmanager. The Alertmanager will be deployed next to the control plane when the `Shoot` resource specifies `.spec.monitoring.alerting.emailReceivers` and if a [SMTP secret](https://github.com/gardener/gardener/blob/master/example/10-secret-alerting.yaml) exists.
 
 If the field gets removed then the Alertmanager will be also removed during the next reconcilation of the cluster. The opposite is also valid if the field is added to an existing cluster.
+
+## Additional Notes
+
+You can configure an VM instance type for each worker pool. The shoot controller uses a URL-rewriting proxy — make sure you pass an URL to the configuration. For logging, the stack relies on Fluentbit to ship logs to the central backend. See the Github releases page for the latest version of the shoot-oidc-service.
+
+Please ensure the user has to verify the correct RBAC permissions before proceeding.
+
+The reconcilation process will also check for Loadbalancer availability in the target zone.