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
- Internal IT operations
Internal IT operations
Internal IT may operate container workloads alongside ordinary service assets and requests. The service record identifies an owner and criticality, while incidents and service requests keep urgent response separate from planned fulfillment. A cluster observation can support the response when a workload is involved.
How Container & K8s Management is set up for you
Service context
Connect assets, incidents, problems, requests and changes to the right service.
Owned response
Assign an incident to a named person and keep dated updates as investigation proceeds.
Request decisions
Review submitted service work before moving it into progress.
Problem follow-up
Give recurring issues an owner and a root cause record.
Internal IT may operate container workloads alongside ordinary service assets and requests. The service record identifies an owner and criticality, while incidents and service requests keep urgent response separate from planned fulfillment. A cluster observation can support the response when a workload is involved.
Choose one active service and its relevant assets. Import the service owner and the people who will act as incident responders and request approvers. Rehearse an incident caused by a readiness gap, recording the affected asset and a dated investigation update. Then submit a routine service request for the same service. The two records should remain easy to distinguish because their status paths and decisions are different.
When an incident exposes a recurring issue, create a problem with an accountable owner. If a production adjustment is needed, draft a change with a planned window and rollback. Ask the Change Approver for the decision and compare later workload observations after the intervention.
Agree on how provider events enter the app. Use event identifiers and receipt outcomes to reconcile external intake, while incident resolution remains a separate service decision.
[Explore the incident path](/container-k8s-management/processes/observation-to-incident) and [request path](/container-k8s-management/processes/request-to-completion).
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.
- Request Approver
- Decides whether a submitted service request proceeds to fulfillment.
- 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.