- General Architecture
- Gardener landing page
gardener.cloud
- "Gardener, the Kubernetes Botanist" blog on kubernetes.io
- Audit a Kubernetes cluster
- Cluster purposes
- Custom
CoreDNS
configuration - Trusted TLS certificate for shoot control planes
- Gardener configuration and usage
- OpenIDConnect presets
- Supported Kubernetes versions
- Trigger shoot operations
- Troubleshooting guide
- GEP-1: Gardener extensibility and extraction of cloud-specific/OS-specific knowledge
- GEP-2:
BackupInfrastructure
CRD and Controller Redesign - GEP-3: Network extensibility
- GEP-4: New
core.gardener.cloud/v1alpha1
APIs 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
- Setting up a local development environment
- Unit Testing and Dependency Management
- Features, Releases and Hotfixes
- Adding New Cloud Providers
- Extending the Monitoring Stack
- How to create log parser for container into fluent-bit
- Extensibility overview
- Extension controller registration
Cluster
resource- Extension points
- General conventions
- Trigger for reconcile operations
- Deploy resources into the shoot cluster
- Shoot resource customization webhooks
- Logging and Monitoring configuration
- Contributing to shoot health status conditions
- Blob storage providers
- DNS providers
- IaaS/Cloud providers
- Network plugin providers
- Operating systems
- Container runtimes
- Generic (non-essential) extensions
- Extending project roles