Removed overrides from manifest file (gardener#6074)

.docforge/manifest.yaml

@@ -21,22 +21,6 @@ structure:
         - Developers
   nodesSelector:
     path: /docs/concepts
-  nodes:
-    - name: cluster-api.md
-      source: https://github.com/gardener/gardener/blob/master/docs/concepts/cluster-api.md
-      properties:
-        frontmatter:
-          title: Cluster API
-    - name: apiserver.md
-      source: https://github.com/gardener/gardener/blob/master/docs/concepts/apiserver.md
-      properties:
-        frontmatter:
-          title: API Server 
-    - name: apiserver_admission_plugins.md
-      source: https://github.com/gardener/gardener/blob/master/docs/concepts/apiserver_admission_plugins.md
-      properties:
-        frontmatter:
-          title: APIServer Admission Plugins
 - name: deployment
   properties:
     frontmatter:
@@ -47,12 +31,6 @@ structure:
         - Developers
   nodesSelector:
     path: /docs/deployment
-  nodes:
-    - name: gardenlet_api_access.md
-      source: https://github.com/gardener/gardener/blob/master/docs/deployment/gardenlet_api_access.md
-      properties:
-        frontmatter:
-          title: Gardenlet API Access
 - name: development
   properties:
     frontmatter:
@@ -62,12 +40,6 @@ structure:
         - Developers
   nodesSelector:
     path: /docs/development
-  nodes:
-    - name: changing-the-api.md
-      source: https://github.com/gardener/gardener/blob/master/docs/development/changing-the-api.md
-      properties:
-        frontmatter:
-          title: Changing the APIs
 - name: extensions
   properties:
     frontmatter:
@@ -77,57 +49,6 @@ structure:
         - Developers
   nodesSelector:
     path: /docs/extensions
-  nodes:
-    - name: backupbucket.md
-      source: https://github.com/gardener/gardener/blob/master/docs/extensions/backupbucket.md
-      properties:
-        frontmatter:
-          title: BackupBucket
-    - name: backupentry.md
-      source: https://github.com/gardener/gardener/blob/master/docs/extensions/backupentry.md
-      properties:
-        frontmatter:
-          title: BackupEntry
-    - name: ca-rotation.md
-      source: https://github.com/gardener/gardener/blob/master/docs/extensions/ca-rotation.md
-      properties:
-        frontmatter:
-          title: CA Rotation
-    - name: containerruntime.md
-      source: https://github.com/gardener/gardener/blob/master/docs/extensions/containerruntime.md
-      properties:
-        frontmatter:
-          title: ContainerRuntime
-    - name: controllerregistration.md
-      source: https://github.com/gardener/gardener/blob/master/docs/extensions/controllerregistration.md
-      properties:
-        frontmatter:
-          title: ControllerRegistration
-    - name: controlplane-exposure.md
-      source: https://github.com/gardener/gardener/blob/master/docs/extensions/controlplane-exposure.md
-      properties:
-        frontmatter:
-          title: ControlPlane Exposure
-    - name: controlplane-webhooks.md
-      source: https://github.com/gardener/gardener/blob/master/docs/extensions/controlplane-webhooks.md
-      properties:
-        frontmatter:
-          title: ControlPlane Webhooks
-    - name: controlplane.md
-      source: https://github.com/gardener/gardener/blob/master/docs/extensions/controlplane.md
-      properties:
-        frontmatter:
-          title: ControlPlane
-    - name: dns.md
-      source: https://github.com/gardener/gardener/blob/master/docs/extensions/dns.md
-      properties:
-        frontmatter:
-          title: DNS
-    - name: dnsrecord.md
-      source: https://github.com/gardener/gardener/blob/master/docs/extensions/dnsrecord.md
-      properties:
-        frontmatter:
-          title: DNS Record
 - name: monitoring
   properties:
     frontmatter:
@@ -146,17 +67,6 @@ structure:
         - Developers
   nodesSelector:
     path: /docs/proposals
-  nodes:
-    - name: 08-shoot-apiserver-via-sni.md
-      source: https://github.com/gardener/gardener/blob/master/docs/proposals/08-shoot-apiserver-via-sni.md
-      properties:
-        frontmatter:
-          title: Shoot APIServer via SNI
-    - name: 04-new-core-gardener-cloud-apis.md
-      source: https://github.com/gardener/gardener/blob/master/docs/proposals/04-new-core-gardener-cloud-apis.md
-      properties:
-        frontmatter:
-          title: New Core Gardener Cloud APIs
 - name: usage
   properties:
     frontmatter:
@@ -166,50 +76,4 @@ structure:
         - Operators
         - Users
   nodesSelector:
-    path: /docs/usage
-  nodes:
-    - name: apiserver-sni-injection.md
-      source: https://github.com/gardener/gardener/blob/master/docs/usage/apiserver-sni-injection.md
-      properties:
-        frontmatter:
-          title: APIServer SNI Injection
-    - name: shooted_seed.md
-      source: https://github.com/gardener/gardener/blob/master/docs/usage/shooted_seed.md
-      properties:
-        frontmatter:
-          title: Create a Shooted Seed Cluster
-    - name: csi_components.md
-      source: https://github.com/gardener/gardener/blob/master/docs/usage/csi_components.md
-      properties:
-        frontmatter:
-          title: CSI Components
-    - name: custom-dns.md
-      source: https://github.com/gardener/gardener/blob/master/docs/usage/custom-dns.md
-      properties:
-        frontmatter:
-          title: Custom DNS Configuration
-    - name: dns-autoscaling.md
-      source: https://github.com/gardener/gardener/blob/master/docs/usage/dns-autoscaling.md
-      properties:
-        frontmatter:
-          title: DNS Autoscaling
-    - name: exposureclasses.md
-      source: https://github.com/gardener/gardener/blob/master/docs/usage/exposureclasses.md
-      properties:
-        frontmatter:
-          title: ExposureClasses
-    - name: node-local-dns.md
-      source: https://github.com/gardener/gardener/blob/master/docs/usage/node-local-dns.md
-      properties:
-        frontmatter:
-          title: NodeLocalDNS Configuration
-    - name: openidconnect-presets.md
-      source: https://github.com/gardener/gardener/blob/master/docs/usage/openidconnect-presets.md
-      properties:
-        frontmatter:
-          title: OpenIDConnect Presets
-    - name: reversed-vpn-tunnel.md
-      source: https://github.com/gardener/gardener/blob/master/docs/usage/reversed-vpn-tunnel.md
-      properties:
-        frontmatter:
-          title: Reversed VPN Tunnel
+    path: /docs/usage

docs/concepts/apiserver.md

@@ -1,3 +1,7 @@
+---
+title: API Server
+---
+
 # Gardener API server
 
 The Gardener API server is a Kubernetes-native extension based on its [aggregation layer](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/).

docs/concepts/apiserver_admission_plugins.md

@@ -1,3 +1,7 @@
+---
+title: APIServer Admission Plugins
+---
+
 # Admission Plugins
 
 Similar to the kube-apiserver, the gardener-apiserver comes with a few in-tree managed admission plugins.

docs/concepts/cluster-api.md

@@ -1,3 +1,7 @@
+---
+title: Cluster API
+---
+
 # Relation between Gardener API and Cluster API (SIG Cluster Lifecycle)
 
 In essence, the Cluster API harmonizes how to get to clusters, while Gardener goes one step further and also harmonizes the clusters themselves. The Cluster API delegates the specifics to so-called providers for infrastructures or control planes via specific CR(D)s while Gardener only has one cluster CR(D). Different Cluster API providers, e.g. for AWS, Azure, GCP, etc. give you vastly different Kubernetes clusters. In contrast, Gardener gives you the exact same clusters with the exact same K8s version, operating system, control plane configuration like for API server or kubelet, add-ons like overlay network, HPA/VPA, DNS and certificate controllers, ingress and network policy controllers, control plane monitoring and logging stacks, down to the behavior of update procedures, auto-scaling, self-healing, etc. on all supported infrastructures. These homogeneous clusters are an essential goal for Gardener as its main purpose is to simplify operations for teams that need to develop and ship software on Kubernetes clusters on a plethora of infrastructures (a.k.a. multi-cloud).

docs/deployment/gardenlet_api_access.md

@@ -1,3 +1,7 @@
+---
+title: Gardenlet API Access
+---
+
 # Scoped API Access for Gardenlets
 
 By default, `gardenlet`s have administrative access in the garden cluster.

docs/development/changing-the-api.md

@@ -1,3 +1,7 @@
+---
+title: Changing the APIs
+---
+
 # Extending the API
 
 This document describes the steps that need to be performed when changing the API.

docs/extensions/backupbucket.md

@@ -1,3 +1,7 @@
+---
+title: BackupBucket
+---
+
 # Contract: `BackupBucket` resource
 
 The Gardener project features a sub-project called [etcd-backup-restore](https://github.com/gardener/etcd-backup-restore) to take periodic backups of etcd backing Shoot clusters. It demands the bucket (or its equivalent in different object store providers) to be created and configured externally with appropriate credentials. The `BackupBucket` resource takes this responsibility in Gardener.

docs/extensions/backupentry.md

@@ -1,3 +1,7 @@
+---
+title: BackupEntry
+---
+
 # Contract: `BackupEntry` resource
 
 The Gardener project features a sub-project called [etcd-backup-restore](https://github.com/gardener/etcd-backup-restore) to take periodic backups of etcd backing Shoot clusters. It demands the bucket (or its equivalent in different object store providers) access credentials to be created and configured externally with appropriate credentials. The `BackupEntry` resource takes this responsibility in Gardener to provide this information by creating a secret specific to the component. Said that, the core motivation for introducing this resource was to support retention of backups post deletion of `Shoot`. The etcd-backup-restore components takes responsibility of garbage collecting old backups out of the defined period. Once a shoot is deleted, we need to persist the backups for few days. Hence, Gardener uses the `BackupEntry` resource for this housekeeping work post deletion of a `Shoot`. The `BackupEntry` resource is responsible for shoot specific prefix under referred bucket.

docs/extensions/ca-rotation.md

@@ -1,3 +1,7 @@
+---
+title: CA Rotation
+---
+
 # CA Rotation in Extensions
 
 [GEP-18](../proposals/18-shoot-CA-rotation.md) proposes adding support for automated rotation of Shoot cluster certificate authorities (CAs).

docs/extensions/containerruntime.md

@@ -1,3 +1,7 @@
+---
+title: ContainerRuntime
+---
+
 # Gardener Container Runtime Extension
 
 At the lowest layers of a Kubernetes node is the software that, among other things, starts and stops containers. It is called “Container Runtime”. 

docs/extensions/controllerregistration.md

@@ -1,3 +1,7 @@
+---
+title: ControllerRegistration
+---
+
 # Registering Extension Controllers
 
 Extensions are registered in the garden cluster via [`ControllerRegistration`](../../example/25-controllerregistration.yaml) resources.

docs/extensions/controlplane-exposure.md

@@ -1,3 +1,7 @@
+---
+title: ControlPlane Exposure
+---
+
 # Contract: `ControlPlane` resource with purpose `exposure`
 
 Some Kubernetes clusters require an additional deployments required by the seed cloud provider in order to work properly, e.g. AWS Load Balancer Readvertiser.

docs/extensions/controlplane-webhooks.md

@@ -1,3 +1,7 @@
+---
+title: ControlPlane Webhooks
+---
+
 # Controlplane customization webhooks
 
 Gardener creates the Shoot controlplane in several steps of the Shoot flow. At different point of this flow, it:

docs/extensions/controlplane.md

@@ -1,3 +1,7 @@
+---
+title: ControlPlane
+---
+
 # Contract: `ControlPlane` resource
 
 Most Kubernetes clusters require a `cloud-controller-manager` or CSI drivers in order to work properly.

docs/extensions/dns.md

@@ -1,3 +1,7 @@
+---
+title: DNS
+---
+
 # Contract: `DNSProvider` and `DNSEntry` resources
 
 Every shoot cluster requires external DNS records that are publicly resolvable.

docs/extensions/dnsrecord.md

@@ -1,3 +1,7 @@
+---
+title: DNS Record
+---
+
 # Contract: `DNSRecord` resources
 
 Every shoot cluster requires external DNS records that are publicly resolvable.

docs/proposals/04-new-core-gardener-cloud-apis.md

@@ -1,3 +1,7 @@
+---
+title: New Core Gardener Cloud APIs
+---
+
 # New `core.gardener.cloud/v1beta1` APIs required to extract cloud-specific/OS-specific knowledge out of Gardener core
 
 ## Table of Contents

docs/proposals/08-shoot-apiserver-via-sni.md

@@ -1,3 +1,7 @@
+---
+title: Shoot APIServer via SNI
+---
+
 # SNI Passthrough proxy for kube-apiservers
 
 This GEP tackles the problem that today a single `LoadBalancer` is needed for every single Shoot cluster's control plane.

docs/usage/apiserver-sni-injection.md

@@ -1,3 +1,7 @@
+---
+title: APIServer SNI Injection
+---
+
 # APIServerSNI environment variable injection
 
 If the Gardener administrator has enabled `APIServerSNI` feature gate for a particular Seed cluster, then in each Shoot cluster's `kube-system` namespace a `DaemonSet` called `apiserver-proxy` is deployed. It routes traffic to the upstream Shoot Kube APIServer. See the [APIServer SNI GEP](../proposals/08-shoot-apiserver-via-sni.md) for more details.

docs/usage/csi_components.md

@@ -1,3 +1,7 @@
+---
+title: CSI Components
+---
+
 # (Custom) CSI Components
 
 Some provider extensions for Gardener are using CSI components to manage persistent volumes in the shoot clusters.

docs/usage/custom-dns.md

@@ -1,3 +1,7 @@
+---
+title: Custom DNS Configuration
+---
+
 # Custom DNS Configuration
 
 Gardener provides Kubernetes-Clusters-As-A-Service where all the system components (e.g., kube-proxy, networking, dns, ...) are managed.

docs/usage/dns-autoscaling.md

@@ -1,3 +1,7 @@
+---
+title: DNS Autoscaling
+---
+
 # DNS Autoscaling
 
 This is a short guide describing different options how to automatically scale CoreDNS in the shoot cluster.

docs/usage/exposureclasses.md

@@ -1,3 +1,7 @@
+---
+title: ExposureClasses
+---
+
 # ExposureClasses
 
 The Gardener API server provides a cluster-scoped `ExposureClass` resource.

docs/usage/node-local-dns.md

@@ -1,3 +1,7 @@
+---
+title: NodeLocalDNS Configuration
+---
+
 # NodeLocalDNS Configuration
 
 This is a short guide describing how to enable DNS caching on the shoot cluster nodes.

docs/usage/openidconnect-presets.md

@@ -1,3 +1,7 @@
+---
+title: OpenIDConnect Presets
+---
+
 # ClusterOpenIDConnectPreset and OpenIDConnectPreset
 
 This page provides an overview of ClusterOpenIDConnectPresets and OpenIDConnectPresets, which are objects for injecting [OpenIDConnect Configuration](https://openid.net/connect/) into `Shoot` at creation time. The injected information contains configuration for the Kube API Server and optionally configuration for kubeconfig generation using said configuration.

docs/usage/reversed-vpn-tunnel.md

@@ -1,3 +1,7 @@
+---
+title: Reversed VPN Tunnel
+---
+
 # Reversed VPN Tunnel Setup and Configuration 
 
 This is a short guide describing how to enable tunneling traffic from shoot cluster to seed cluster instead of the default "seed to shoot" direction. 

docs/usage/shooted_seed.md

@@ -1,3 +1,7 @@
+---
+title: Create a Shooted Seed Cluster
+---
+
 # Create Shooted Seed Cluster
 
 Create managed seed (aka "shooted seed") cluster with the `shoot.gardener.cloud/use-as-seed` annotation.