ritazh / container-compute-upstream

This project captures asks, work in progress, and completed work for the Microsoft Container Compute Upstream team in the form of issues and a project board

Contributing

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 [e-mail] with any additional questions or comments.

Azure Container Compute Upstream Projects

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.

Support

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 list

Project Area	Project & (artifacts)	Goal	Project State & API Version	Communication	Use on Azure
Kubernetes Cluster Management
	AKS Engine (releases)	Self-managed clusters on Azure	Azure: incubating API: N/A	#aks-engine-users GitHub issues	Azure Kubernetes Service Azure Stack Hub
	Cluster API Azure Provider (releases) Tests	Self-managed clusters on Azure using Cluster API	CNCF: incubating API: v1alpha3	#cluster-api-azure [e-mail] GitHub issues
Kubernetes Azure Cloud Provider
	In-tree (legacy) (releases) Tests	Use Azure infra for K8s	CNCF: graduated API: stable	#provider-azure [e-mail] GitHub issues	Azure Kubernetes Service Use with AKS Engine
	Cluster Autoscaler Azure Provider (releases) Tests	Use cluster data to scale out/back nodes	CNCF: N/A API: stable	same slack and email GitHub issues	Azure Kubernetes Service Use with AKS Engine
	Out-of-tree Provider (releases) Tests	Use Azure infra for K8s	CNCF: N/A API: alpha	same slack and email GitHub issues	Use with AKS Engine
	Azure Disk CSI Driver (releases) Tests	Enable use of Azure disk volume	CNCF: N/A API: N/A	same slack and email GitHub issues	Use with AKS Engine
	Azure File CSI Driver (releases) Tests	Enable use of Azure disk volume	CNCF: N/A API: N/A	same slack and email GitHub issues	Use with AKS Engine
	Azure Blobfuse CSI Driver (releases) Tests	Enable use of azure-storage-fuse	CNCF: N/A API: N/A	same slack and email 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	CNCF: stable API: N/A	#sig-windows [e-mail] Windows Community Forum GitHub issues	AKS Windows AKS Engine Windows
	IPv4/v6 Dual Stack (kubernetes releases) Tests	IPv4/IPv6 dual-stack enables the allocation of both IPv4 and IPv6 addresses to Pods and Services.	CNCF: stable Feature: alpha	#sig-network [e-mail] GitHub issues	Use with AKS Engine
Cloud Native Governance and Security
	AAD Pod Identity (releases)	Enables K8s applications to access cloud resources securely with Azure Active Directory	Azure: incubation API: v1	GitHub issues GitHub Project	Use with AKS Use with AKS Engine
	OPA Gatekeeper (releases)	K8s native Open Policy Agent policy enforcement	CNCF: incubating API: v1alpha1 and v1beta1	#kubernetes-policy GitHub issues	Azure Policy for AKS Azure Policy for AKS Engine Azure Policy for Azure Arc connected clusters
	Keyvault Flexvol (releases)	Mount Azure Keyvault secrets into pods	Azure: incubation API: N/A	GitHub issues	Use with AKS
	Secrets Store CSI Driver (releases) Builds	Integrates secrets stores with Kubernetes via a Container Storage Interface (CSI) volume	CNCF: N/A API: v1alpha1	#sig-auth GitHub issues
	Azure KeyVault Provider for Secrets Store CSI Driver (releases)	Enables mounting AKV secrets as volumes in K8s pods	Azure: sandbox API: N/A	GitHub issues
Cloud Native Service Mesh
	Service Mesh Interface (SMI) Spec	A standard interface for service meshes on Kubernetes	CNCF: sandbox (pending) APIs: Traffic Split v1alpha3; Traffic Target v1alpha1; Traffic Spec v1alpha2; Traffic Metrics v1alpha1	#general GitHub issues
Container Runtime
	Moby (releases)	Toolkit for app containerization	Moby: ?? API: N/A	#opencontainers Moby Forums GitHub issues	Azure Kubernetes Service Azure Stack Hub) many more
	Containerd (releases)	Complete container lifecycle management on Linux and Windows hosts	CNCF: graduated API: N/A	#opencontainers [e-mail] GitHub issues	Use with AKS Engine

Maturity

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