SIG Apps

Meetings

Joining the mailing list for the group will typically add invites for the following meetings to your calendar.

• Regular SIG Meeting (calendar) : Mondays at 9:00 PT (Pacific Time) (biweekly). Convert to your timezone.
  • Meeting notes and Agenda.
  • Meeting recordings.
• Subproject Agent Sandbox Meeting (calendar) : Mondays at 9:00 PT (Pacific Time) (biweekly). Convert to your timezone.
  • Meeting notes and Agenda.
  • Meeting recordings.

Leadership

Chairs

The Chairs of the SIG run operations and processes governing the SIG.

• Janet Kuo (@janetkuo), Google
• Kenneth Owens (@kow3ns), Snowflake
• Maciej Szulik (@soltysh), Defense Unicorns

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

• Janet Kuo (@janetkuo), Google
• Kenneth Owens (@kow3ns), Snowflake
• Maciej Szulik (@soltysh), Defense Unicorns

Emeritus Leads

• Matt Farina (@mattfarina)
• Adnan Abdulhussein (@prydonius)

Contact

• Slack: #sig-apps
• Mailing list
• Open Community Issues/PRs
• GitHub Teams:
  • @kubernetes/sig-apps-api-reviews - API Changes and Reviews
  • @kubernetes/sig-apps-bugs - Bug Triage and Troubleshooting
  • @kubernetes/sig-apps-feature-requests - Feature Requests
  • @kubernetes/sig-apps-misc - General Discussion
  • @kubernetes/sig-apps-pr-reviews - PR Reviews
  • @kubernetes/sig-apps-proposals - Design Proposals
  • @kubernetes/sig-apps-test-failures - Test Failures and Triage
• Steering Committee Liaison: Paco Xu 徐俊杰 (@pacoxu)

Working Groups

The following working groups are sponsored by sig-apps:

• WG Batch
• WG Checkpoint Restore
• WG Data Protection
• WG Node Lifecycle
• WG Workload Conformance
• WG Workload-aware Scheduling

Subprojects

The following subprojects are owned by sig-apps:

agent-devops

• Owners:
  • kubernetes-sigs/devops-bench
  • kubernetes-sigs/kube-agents

agent-sandbox

Easy management of isolated, stateful, singleton workloads, ideal for use cases like AI agent runtimes

• Owners:
  • kubernetes-sigs/agent-sandbox
• Contact:
  • Slack: #agent-sandbox

application

Application metadata descriptor CRD

• Owners:
  • kubernetes-sigs/application
  • kubernetes-sigs/mcp-lifecycle-operator

examples

• Owners:
  • kubernetes/examples

execution-hook

• Owners:
  • kubernetes-sigs/execution-hook

kjob

• Owners:
  • kubernetes-sigs/kjob

kompose

• Owners:
  • kubernetes/kompose
• Contact:
  • Slack: #kompose

workload-class

A high-level Kubernetes control layer for managing workload outcomes and disruption guardrails during maintenance.

• Owners:
  • kubernetes-sigs/workload-class

workloads-api

The core workloads API, which is composed of the CronJob, DaemonSet, Deployment, Job, ReplicaSet, ReplicationController, PodDisruptionBudget and StatefulSet kinds

• Owners:
  • kubernetes-sigs/jobset
  • kubernetes-sigs/lws
  • kubernetes/kubernetes/pkg/apis/apps
  • kubernetes/kubernetes/pkg/apis/batch
  • kubernetes/kubernetes/pkg/apis/core/v1
  • kubernetes/kubernetes/pkg/apis/extensions
  • kubernetes/kubernetes/pkg/apis/policy
  • kubernetes/kubernetes/pkg/controller/cronjob
  • kubernetes/kubernetes/pkg/controller/daemon
  • kubernetes/kubernetes/pkg/controller/deployment
  • kubernetes/kubernetes/pkg/controller/disruption
  • kubernetes/kubernetes/pkg/controller/history
  • kubernetes/kubernetes/pkg/controller/job
  • kubernetes/kubernetes/pkg/controller/replicaset
  • kubernetes/kubernetes/pkg/controller/replication
  • kubernetes/kubernetes/pkg/controller/statefulset
  • kubernetes/kubernetes/pkg/registry/apps
  • kubernetes/kubernetes/pkg/registry/batch
  • kubernetes/kubernetes/staging/src/k8s.io/api/apps
  • kubernetes/kubernetes/staging/src/k8s.io/api/batch
  • kubernetes/kubernetes/staging/src/k8s.io/api/extensions
  • kubernetes/kubernetes/staging/src/k8s.io/api/policy
  • kubernetes/kubernetes/test/e2e/apps
  • kubernetes/kubernetes/test/integration/daemonset
  • kubernetes/kubernetes/test/integration/deployment

Goals

• Discuss running and defining applications in Kubernetes (e.g., APIs, SDKs, Controllers, package management tools, etc.)
• Work on improvements to the Workload API
• Suggest Kubernetes features where we see friction
• Be the voice of the people running applications in Kubernetes (developers and devops)
• Help people get involved in the Kubernetes community
• Show early features/demos of tools that make running apps easier

Non-goals

• Do not endorse one particular ecosystem tool
• Do not pick which apps to run on top of Kubernetes
• Do not recommend one way to do things (e.g., picking a template language)

Helm and Charts

Helm, Charts and its other subprojects have moved to the CNCF. See Helm’s community repository for information about the Helm project.