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
- Managed operations teams
Managed operations teams
A managed operations team needs to know which environment a workload observation describes and which person owns the response. Cluster, service and people references help a shift handoff carry that context. The incident record keeps the service issue and its updates together; change review records the intervention decision.
How Container & K8s Management is set up for you
Environment register
Record cluster provider, version, environment and owner before observations arrive.
Shift context
Use dated workload observations and incident updates to show what changed during investigation.
Accountable decisions
Name a change approver for scheduled work and a responder for incident closure.
Event review
Keep provider event identifiers and failed receipt outcomes available for reconciliation.
A managed operations team needs to know which environment a workload observation describes and which person owns the response. Cluster, service and people references help a shift handoff carry that context. The incident record keeps the service issue and its updates together; change review records the intervention decision.
Start with a small named set of clusters and services whose ownership the team can verify. Choose a workload with a known namespace and record a normal observation before testing a readiness gap. Have one responder open an incident, then ask another to pick up the case using the cluster context, assigned person and attributed updates. The second person should be able to explain the current state without an oral handoff.
Prepare a change for the affected service. Review the risk, window and rollback plan, then record either a verified or rolled-back result. Compare the observations around the window and keep the incident outcome separate from the change outcome.
If events come from a monitoring provider, configure mapping and event identity before enabling routine intake. Review rejected or failed receipts against provider evidence so a missing intake event does not masquerade as a healthy workload.
[Follow the change path](/container-k8s-management/processes/change-review) and [integration controls](/container-k8s-management/integrations).
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.