website-and-documentation/content/en/docs/components/kubernetes.md
Stephan Lo 82d424aeca fix(docs): remove Backstage component and add editorial headers
- Remove Backstage component page (not in product structure)
- Add editorial status alert to all draft pages with:
  * Jira ticket reference placeholder
  * Assignee field
  * Draft status indicator
  * Last updated date
  * TODO checklist for completion
- Update component template with editorial header
- Use Docsy alert shortcode (warning style) for professional appearance
2025-11-16 13:42:58 +01:00

62 lines
1.6 KiB
Markdown

---
title: "Kubernetes"
linkTitle: "Kubernetes"
weight: 2
description: >
Container orchestration platform for deploying and managing applications.
---
{{% alert title="Draft" color="warning" %}}
**Editorial Status**: This page is currently being developed.
* **Jira Ticket**: TBD
* **Assignee**: Team
* **Status**: Draft - Template populated
* **Last Updated**: 2025-11-16
* **TODO**:
* [ ] Add cluster access procedures
* [ ] Document namespace structure
* [ ] Include deployment examples
* [ ] Add resource management guidelines
{{% /alert %}}
## Overview
Kubernetes provides the foundation for container orchestration in the EDP, enabling deployment, scaling, and management of containerized applications.
## Key Features
* Container orchestration and scheduling
* Service discovery and load balancing
* Storage orchestration
* Self-healing and automated rollouts
* Configuration and secret management
## Purpose in EDP
Kubernetes serves as the runtime platform for all EDP components and user applications, providing standardized deployment and operations.
## Getting Started
[To be documented: Quick start for deploying to Kubernetes in EDP]
## Integration Points
* **ArgoCD**: Kubernetes deployment automation
* **Crossplane**: Infrastructure provisioning on Kubernetes
* **VictoriaMetrics/Prometheus**: Kubernetes metrics collection
* **Backstage**: Kubernetes resource visualization
## Status
**Maturity**: Production
## Documentation Notes
This is a template page. Team members should fill in:
* Cluster access procedures
* Namespace organization
* Resource quotas and limits
* Network policies
* Storage classes and PV management