WG06 Meeting minutes 21/05/2026

Agenda

  • Keptn: update on the life cycle orchestration tool (precheck/postinstallation/smart remediation) - Cuemby 30'
  • GitOps Telco Hackathon Follow-up: let’s continue defining the perimeter of the event
    • Introduction to E// MPN Operator - Swisscom 15'
    • DT OCAS operators - DT 15'

Replay

Replay

Support

Minutes

Quick Recap

The meeting focused on presentations and discussions about lifecycle management tools and operators for telco workloads.

The CUEMBY team presented their prototype for remediation patterns using Keptn, demonstrating 2 scenarios including auto-rollback patterns and horizontal autoscaling, with Martin Quintero showing how the system can detect SLO breaches and automatically create revert commits through GitOps workflows. Angel clarified that while Keptn version 1 is being archived, they continue supporting the lifecycle toolkit version 2, which operates in an operator-style manner.

Swisscom's Alexander and Alessio presented their MPN (Mobile Private Network) operator architecture using KRO and SDC, showing how they handle high-level intent processing and generate configuration resources for network functions.

Maulik from Deutsche Telekom shared their OCAS suite of operators including infrastructure provisioning, service management, and certificate monitoring tools, along with a config validator that can check YAML/JSON schemas against IETF YANG models.

The group discussed plans for an upcoming hackathon focused on Kubernetes operators to help telcos with their GitOps journey, with Julie from Working Group 2 emphasizing the importance of operator-vendor collaboration under the Linux Foundation banner.

Next Steps

  • Angel: Share the CUEMBY team's presentation materials and demo videos with the meeting attendees for further review.
  • Aug.-Wilh.: Make available video materials from KubeCon 2026
  • Julie: Send an email to all participants detailing the logistical and technical requirements for the hackathon event, including Linux Foundation and SYLVA event constraints.
  • All Working Group 6 members: Contribute to the hackathon page (GitLab) with suggestions, merge requests, and proposals for operators, audience, and format, aiming to define the technical perimeter by end of June.
  • Maulik: Discuss internally and potentially organize a short session to evaluate the open sourcing of the config validator tool, including management responsibilities.
  • All interested parties: Use Slack channel and/or organize additional meetings to continue hackathon planning and operator selection discussions.
  • Morgan: Include all relevant links and reviews in the meeting minutes and coordinate with CUEMBY team for review.
  • All participants: Contribute to the SYLVA GitLab "kanopy" subgroup with relevant open source enablers, recipes, or mirrors to increase visibility and collaboration.