- General Architecture
- Gardener landing page
gardener.cloud - "Gardener, the Kubernetes Botanist" blog on kubernetes.io
- "Gardener Project Update" blog on kubernetes.io
- APIServerSNI environment variable injection
- Audit a Kubernetes cluster
- Auto-Scaling for shoot clusters
- Cleanup of Shoot clusters in deletion
- Custom
containerdconfiguration - Custom
CoreDNSconfiguration - (Custom) CSI components
- Default Seccomp Profile
- DNS Autoscaling
- DNS Search Path Optimization
- Dockershim removal
- ExposureClasses
- Gardener configuration and usage
- Hibernate a Cluster
ManagedIstiofeature- Network Policies in the Shoot Cluster
NodeLocalDNSfeature- OpenIDConnect presets
- Projects
- Project Namespace Access
- Register Shoot as Seed
- Reversed Cluster VPN
- Seed Bootstrapping
- Seed Settings
- Shoot Cluster Purposes
- Shoot Scheduling Profiles
- Shoot Credentials Rotation
- Shoot Kubernetes and Operating System Versioning
- Shoot Networking
- Shoot Maintenance
- Shoot
ServiceAccountConfigurations - Shoot Status
- Shoot Info
ConfigMap - Shoot Updates and Upgrades
- Shoot HA Control Plane
- Accessing Shoot Clusters
- Supported Kubernetes versions
- Tolerations
- Trigger shoot operations
- Troubleshooting guide
- Trusted TLS certificate for shoot control planes
- Controlling the Kubernetes versions for specific worker pools
- Migrating from
PodSecurityPolicys to PodSecurity admission controller
authentication.gardener.cloudAPI Groupcore.gardener.cloudAPI Groupextensions.gardener.cloudAPI Groupoperations.gardener.cloudAPI Groupresources.gardener.cloudAPI Groupseedmanagement.gardener.cloudAPI Groupsettings.gardener.cloudAPI Group
- GEP: Gardener Enhancement Proposal Description
- GEP: Template
- GEP-1: Gardener extensibility and extraction of cloud-specific/OS-specific knowledge
- GEP-2:
BackupInfrastructureCRD and Controller Redesign - GEP-3: Network extensibility
- GEP-4: New
core.gardener.cloud/v1alpha1APIs required to extract cloud-specific/OS-specific knowledge out of Gardener core - GEP-5: Gardener Versioning Policy
- GEP-6: Integrating etcd-druid with Gardener
- GEP-7: Shoot Control Plane Migration
- GEP-8: SNI Passthrough proxy for kube-apiservers
- GEP-9: Gardener integration test framework
- GEP-10: Support additional container runtimes
- GEP-11: Utilize API Server Network Proxy to Invert Seed-to-Shoot Connectivity
- GEP-12: OIDC Webhook Authenticator
- GEP-13: Automated Seed Management
- GEP-14: Reversed Cluster VPN
- GEP-15: Manage Bastions and SSH Key Pair Rotation
- GEP-16: Dynamic kubeconfig generation for Shoot clusters
- GEP-17: Shoot Control Plane Migration "Bad Case" Scenario
- GEP-18: Automated Shoot CA Rotation
- GEP-19: Monitoring Stack - Migrating to the prometheus-operator
- GEP-20: Highly Available Shoot Control Planes
- Getting started locally (using the local provider)
- Setting up a development environment (using a cloud provider)
- Testing (Unit, Integration, E2E Tests)
- Test Machinery Tests
- Dependency Management
- Kubernetes Clients in Gardener
- Logging in Gardener Components
- Changing the API
- Secrets Management for Seed and Shoot Clusters
- Releases, Features, Hotfixes
- Adding New Cloud Providers
- Adding Support For A New Kubernetes Version
- Extending the Monitoring Stack
- How to create log parser for container into fluent-bit
- Network Policies in the Seed Cluster
PriorityClassesin Gardener Clusters
- Extensibility overview
- Extension controller registration
Clusterresource- Extension points
- General conventions
- Trigger for reconcile operations
- Deploy resources into the shoot cluster
- Shoot resource customization webhooks
- Logging and monitoring for extensions
- Contributing to shoot health status conditions
- CA Rotation in Extensions
- Blob storage providers
- DNS providers
- IaaS/Cloud providers
- Network plugin providers
- Operating systems
- Container runtimes
- Generic (non-essential) extensions
- Extension Admission
- Heartbeat controller
- Provider Local
- Extending project roles
- Referenced resources
- Control plane migration