This project welcomes contributions and suggestions. If you wonder what the Azure Container Compute team is working on, check out the Project Board. If you would like to see the Azure Container Compute Upstream team work on something, first check if there is an existing issue. If there isn't, please create a new one. If there is existing information elsewhere on the internet, please include the links.
This project is not setup for contributing code. It is intended only for tracking issues.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This list of projects is maintained by the Azure container compute upstream team. This list is intended to help you make informed decisions about what projects to use (or not use) in the context of your goals (e.g. proof of concept vs. production). To make this decision you need to consider your goals, your need for formal support, the project's maturity, governance, version level, and your willingness to work in open source.
Projects listed on this page are open source that Microsoft maintain or contribute to. These projects are NOT covered by the Microsoft Azure support policy. To get help please search the open issues on the project using the links in the table. To communicate with the Azure Container Compute Upstream team please use the issues in this repo. If your issue isn't already represented, please open a new one. However, if you consume one of these projects as a part of a Microsoft or Azure product or service, you may be eligible for support through that product or service.
| Project Area | Project & (artifacts) | Goal | Project State & API Version |
Communication | Use on Azure |
|---|---|---|---|---|---|
| Kubernetes Cluster Management | |||||
| Cluster API Azure Provider (releases) Tests |
Self-managed clusters on Azure using Cluster API | CNCF: incubating API: v1alpha4 |
#cluster-api-azure kubernetes-sig-cluster-lifecycle@googlegroups.com GitHub issues |
||
| AKS Engine (releases) |
Self-managed clusters on Azure | Azure: winding down API: N/A |
#aks-engine-users GitHub issues |
||
| Kubernetes Enhancements | |||||
| Virtual Kubelet (releases) |
Enable services to masquerade as kubelet - serverless | CNCF: sandbox API: N/A |
#virtual-kubelet GitHub issues |
AKS Virtual Nodes | |
| Windows containers (kubernetes releases) Tests |
Run Windows server containers with Kubernetes | Kubernetes: stable API: N/A |
#sig-windows kubernetes-sig-windows@googlegroups.com Windows Community Forum GitHub issues |
||
| IPv4/v6 Dual-Stack (kubernetes releases) Tests |
IPv4/IPv6 dual-stack enables the allocation of both IPv4 and IPv6 addresses to Pods and Services. | Kubernetes: IPv6: beta Dual-stack: GA |
#sig-network kubernetes-sig-network@googlegroups.com GitHub issues |
||
| Cloud Native Governance and Security | |||||
| AAD Pod Identity (releases) |
Enables K8s applications to access cloud resources securely with Azure Active Directory | Azure: winding down API: v1 |
GitHub issues GitHub Project |
||
| OPA Gatekeeper (releases) |
K8s native Open Policy Agent policy enforcement | CNCF: graduated API: Config: v1alpha1; ConstraintTemplate: v1beta1; Constraints: v1beta1 |
#kubernetes-policy GitHub issues |
||
| Secrets Store CSI Driver (releases) Builds |
Integrates secrets stores with Kubernetes via a Container Storage Interface (CSI) volume | Kubernetes: GA API: v1 |
#csi-secrets-store GitHub issues |
||
| Azure KeyVault Provider for Secrets Store CSI Driver (releases) |
Enables mounting AKV secrets as volumes in K8s pods | Azure: GA API: N/A |
GitHub issues | Use with AKS | |
| KMS Plugin for Key Vault (releases) |
Enables encryption at rest of Kubernetes data in etcd using Azure Key Vault | Azure: incubation API: N/A |
GitHub issues | Use with AKS Engine | |
| Azure Workload Identity (releases) |
Uses Kubernetes primitives to associate managed identities for Azure resources and identities in Azure Active Directory (AAD) with pods based on Workload Identity federation | Azure: incubation API: N/A |
GitHub issues | How to use | |
| Cloud Native Service Mesh | |||||
| Service Mesh Interface (SMI) Spec | A standard interface for service meshes on Kubernetes | CNCF: sandbox APIs: Traffic Access Control: v1alpha3; Traffic Metrics: v1alpha1; Traffic Specs: v1alpha4; Traffic Split: v1alpha4 |
#smi GitHub issues |
||
| Open Service Mesh (OSM) | A lightweight, extensible, cloud native service mesh | CNCF: sandbox APIs: N/A |
#openservicemesh GitHub issues |
||
| Container Runtime | |||||
| Moby (releases) |
Toolkit for app containerization | Moby: ?? API: N/A |
#opencontainers Moby Forums GitHub issues |
||
| Containerd (releases) |
Complete container lifecycle management on Linux and Windows hosts | CNCF: graduated API: N/A |
#opencontainers dev@opencontainers.org GitHub issues |
||
| Platforms | |||||
| Brigade | Event-driven scripting for Kubernetes | CNCF: Sandbox API: v2 |
#brigade channel on Kubernetes Slack GitHub Issues |
||
| Deployment Tools | |||||
| Porter | Package your application artifact, client tools, configuration and deployment logic together as a versioned bundle that you can distribute, and then install with a single command | CNCF: Sandbox Stable: v0.38.x Prerelease: v1.0.0-alpha |
Mailing list, slack, etc Project Board |
Azure Service Operator, Azure Trusted Research Environments | |
| CNAB Specification | Cloud Native Application Bundle Specification implemented by Porter | Spec: 1.1 | #cnab on CNCF Slack Issues |
Open source project maturity can be assessed on many dimensions including age, number of contributors, diversity of contributor employers, and many more. Two you should consider are represented in the table as:
- Project state - The first entry in the Maturity column represents the project's status. Projects in the CNCF (kubernetes, kubernetes-sigs, prometheus, etc) use the CNCF maturity model. Projects in the Azure, Microsoft, or deislabs GitHub orgs are working towards using the guaduation guidelines defined in this repo.
- API or Feature Versions if relevant, are listed as the second entry of the Maturity column, and follow the Kubernetes convention except where noted