Assign clear ownership for each element of large-scale container orchestration across the functions involved.
Designing Large-Scale Container Orchestration Systems
Turn large-scale container orchestration from a stated policy into a practice your organisation can evidence.
📍 Tripoli🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Most outages involving large-scale container orchestration are triggered by a change somebody considered routine. Technical debt in the practice within technology and systems delivery is borrowed against future delivery capacity, at compound interest. The content is relevant to those who own this aspect of technology and systems delivery and to those who are held accountable for its results. Participants finish able to explain large-scale container orchestration to a non-specialist audience without losing precision. The teaching approach is deliberately practical: participants build a technical standard for the practice within technology and systems delivery as they go. Post-incident reviews keep identifying weaknesses in this area of technology and systems delivery that were visible long before the incident. It concentrates on the parts of large-scale container orchestration that determine outcomes and treats the rest proportionately. Buying a tool rarely fixes the practice within technology and systems delivery; the underlying capability has to be built internally first. The programme ends where implementation begins, with the wider technology and systems delivery agenda broken into steps someone can start on Monday.
Expected Learning Outcomes
Control technical debt in large-scale container orchestration deliberately rather than by neglect.
Design a practical operating method for large-scale container orchestration that fits the organisation's size and maturity.
Define the availability, performance and recovery targets for large-scale container orchestration.
Establish monitoring and alerting on large-scale container orchestration that reflects user experience.
Translate policy on large-scale container orchestration into procedures that hold up under day-to-day pressure.
Plan capacity for large-scale container orchestration against measured growth rather than optimism.
Who Should Attend
Service desk and support leads handling incidents in large-scale container orchestration.
Consultants and advisers supporting clients on large-scale container orchestration.
Solution architects designing large-scale container orchestration.
Project managers delivering changes to large-scale container orchestration.
Vendor managers overseeing suppliers involved in large-scale container orchestration.
Coordinators responsible for keeping records and documentation of large-scale container orchestration current.
Course Modules
Large-scale container orchestration: architecture and designing for failure
2 sessions · 8 pointsSession 1Proving the backup of large-scale container orchestration by restoring it
- Agree what will be standardised in large-scale container orchestration and what will not.
- Establish the boundary of large-scale container orchestration and record what sits outside it.
- Decide what will be stopped to create capacity for large-scale container orchestration.
- Build the internal briefing that explains large-scale container orchestration to those affected.
Session 2Making releases of large-scale container orchestration routine instead of risky
- Plan the sequence in which improvements to large-scale container orchestration will be introduced.
- Confirm the support model and escalation path for large-scale container orchestration.
- Anticipate the objections large-scale container orchestration will raise and prepare the answers.
- Reduce the variation in how large-scale container orchestration is carried out between teams.
Large-scale container orchestration: monitoring, alerting and observability
2 sessions · 8 pointsSession 1Escalation and decision rights in large-scale container orchestration
- Review logging on large-scale container orchestration for coverage and retention.
- Record the technical debt in large-scale container orchestration and schedule repayment.
- State the availability and recovery objectives for large-scale container orchestration as numbers.
- Review access rights on large-scale container orchestration and remove what is no longer needed.
Session 2Building the method for large-scale container orchestration step by step
- Identify the data already collected that bears on large-scale container orchestration.
- Confirm every release of large-scale container orchestration can be rolled back within a defined time.
- Document the runbook for large-scale container orchestration to the level a new engineer could use.
- Set out how exceptions to large-scale container orchestration are requested and approved.
Large-scale container orchestration: change control and rollback
2 sessions · 8 pointsSession 1Reviewing large-scale container orchestration when nothing has gone wrong
- Apply change control to large-scale container orchestration including emergency changes.
- Restore a backup of large-scale container orchestration in a test environment and time it.
- Rank the weaknesses in large-scale container orchestration by consequence rather than by ease of fixing.
- Close out actions on large-scale container orchestration rather than leaving them open indefinitely.
Session 2Retiring the legacy part of large-scale container orchestration
- Configure alerting on large-scale container orchestration that reflects what users experience.
- Define incident severity levels for large-scale container orchestration and the response each triggers.
- Confirm data retention and deletion rules applied within large-scale container orchestration.
- Set delivery and reliability indicators for large-scale container orchestration the team trusts.
Large-scale container orchestration: build, pipeline and release discipline
2 sessions · 8 pointsSession 1Setting availability and recovery targets for large-scale container orchestration honestly
- Record the rationale for each significant choice made about large-scale container orchestration.
- Rehearse the briefing on large-scale container orchestration that would follow an incident.
- Set out the decisions in large-scale container orchestration that require sign-off and by whom.
- Identify single points of dependency in large-scale container orchestration and reduce them.
Session 2The change to large-scale container orchestration that caused the last outage
- Run a load test on large-scale container orchestration at expected peak plus a margin.
- Identify the single points of failure in large-scale container orchestration.
- Estimate the resource large-scale container orchestration requires to run as designed.
- Assess the exit route from any cloud or vendor dependency in large-scale container orchestration.
Choose the package that suits you
Silver Package
At least 3 people
USD1,250
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Gold Package
At least 3 people
USD1,850
- 5-night stay in a 5-star hotel
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.