Covers deploying and operating applications in Kubernetes. We focus on the developer and devops experience of running applications in Kubernetes. We discuss how to define and run apps in Kubernetes, demo relevant tools and projects, and discuss areas of friction that can lead to suggesting improvements or feature requests.
The charter defines the scope and governance of the Apps Special Interest Group.
Joining the mailing list for the group will typically add invites for the following meetings to your calendar.
- Regular SIG Meeting: Mondays at 9:00 PT (Pacific Time) (biweekly). Convert to your timezone.
The Chairs of the SIG run operations and processes governing the SIG.
The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.
- Matt Farina (@mattfarina)
- Adnan Abdulhussein (@prydonius)
- 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: Bob Killen (@mrbobbytables)
The following working groups are sponsored by sig-apps:
The following subprojects are owned by sig-apps:
Application metadata descriptor CRD
- Owners:
- Owners:
- Owners:
- Owners:
- Contact:
- Slack: #kompose
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/pkg/registry/extensions
- kubernetes/kubernetes/staging/src/k8s.io/api/apps
- kubernetes/kubernetes/staging/src/k8s.io/api/batch
- kubernetes/kubernetes/staging/src/k8s.io/api/core/v1
- 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
- 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
- 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, Charts and its other subprojects have moved to the CNCF. See Helm's community repository for information about the Helm project.