These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Container & K8s Management
- Who it's for
- Software platform teams
Software platform teams
A platform team often supports several environments with similar workload names. Container & K8s Management gives the team a cluster register, dated readiness observations and a service record that names the owner. A responder can investigate an issue using the environment and service context before deciding who should act.
How Container & K8s Management is set up for you
Cluster ownership
Keep production and test clusters distinct by environment, provider and named person.
Readiness evidence
Record desired and ready replicas for a workload at a specific time and cluster.
Service response
Open an incident against the affected service and asset, assign a person and retain attributed updates.
Controlled change
Review risk, schedule and rollback plan before implementing a production change.
A platform team often supports several environments with similar workload names. Container & K8s Management gives the team a cluster register, dated readiness observations and a service record that names the owner. A responder can investigate an issue using the environment and service context before deciding who should act.
Start with a production cluster, a test cluster and one service that the team can trace end to end. Record a workload observation in both environments. Choose a case where production readiness falls below the desired count, then rehearse incident ownership and an update from the investigating person. Use a later observation to assess whether the workload recovered.
Add the change path with a realistic window and rollback plan. The Change Approver should see enough context to decide whether the proposal is safe for that service. The Platform Operator records the implementation result. The Incident Responder then reviews the service condition before closing the incident. These decisions remain separate even when the same team discusses them in one operations call.
Agree on the external telemetry and Kubernetes connection if observations will be collected automatically. Reconcile its cluster and namespace mapping before using it in a live response.
[Review cluster records](/container-k8s-management/modules/clusters) and [the rehearsal plan](/container-k8s-management/implementation).
Features to start with
Roles on the team
- Platform Operator
- Maintains the cluster register and records workload observations and implementation evidence.
- Incident Responder
- Owns investigation and attributed updates for assigned service incidents.
- Service Owner
- Maintains service context and owns problem investigation for that service.
- Change Approver
- Reviews change risk, schedule and rollback plan before a change is implemented.
- Admin
- Configures access, people mappings and event receipt handling.
Set up Container & K8s Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.