AKS Engine: legacy tool for Kubernetes on Azure (see status)
Перейти к файлу
Mark Rossetti f700c4746c fix: ensure cni conf json is valid when exception list contains a single address (#2157) 2019-10-14 20:17:31 -04:00
.chglog chore: add security to changelog commit titles (#1415) 2019-05-30 17:21:47 -07:00
.codecov test: remove dependency on httpmock for Azure Stack unit tests (#1589) 2019-07-08 15:28:05 -07:00
.github chore: add note about apimodel in issue template (#1478) 2019-06-14 09:16:40 -07:00
.pipelines feat: add support for Kubernetes 1.17.0-alpha.1 (#2112) 2019-10-09 00:13:29 -04:00
.prowci docs: update prow docs (#1364) 2019-05-28 10:54:14 -07:00
cmd feat: container monitoring addon supports other Azure clouds (#2031) 2019-10-02 15:18:44 -07:00
docs docs: tidying up (#2126) 2019-10-08 15:40:52 -07:00
examples feat: add linux support for kubenet + containerd (#2050) 2019-10-10 16:31:23 -07:00
extensions chore: remove oms extension docs since they are obsolete (#1900) 2019-09-04 09:47:14 -07:00
jenkins
loc
packer Use WindowsServer VHDs with Oct patches (#2155) 2019-10-14 15:57:25 -07:00
parts fix: ensure cni conf json is valid when exception list contains a single address (#2157) 2019-10-14 20:17:31 -04:00
pkg fix: ensure cni conf json is valid when exception list contains a single address (#2157) 2019-10-14 20:17:31 -04:00
releases chore: rev AKS VHDs to 2019.10.09 (#2136) 2019-10-10 11:12:55 -07:00
scripts feat: add build and deploy windows zip file support on Azure Stack (#1888) 2019-09-06 16:34:18 -07:00
test/e2e test: make AfterSuite log output optional (#2139) 2019-10-14 08:29:22 -07:00
translations
vendor fix: improve container monitoring add-on (#1686) 2019-08-29 09:13:09 -07:00
.devcontainer.json chore: update go toolchain to 1.12.10 (#2034) 2019-09-26 15:06:08 -07:00
.gitattributes
.gitignore feat: Support kubectl port-forward with k8s 1.15 on Windows nodes (#1543) 2019-07-11 09:17:23 -06:00
.golangci.yml style: check for unused parameters (#1323) 2019-05-17 09:47:42 -07:00
CODE_OF_CONDUCT.md docs: use Microsoft's standard code of conduct for GitHub (#1659) 2019-07-23 13:53:43 -07:00
CONTRIBUTING.md
Gopkg.lock fix: improve container monitoring add-on (#1686) 2019-08-29 09:13:09 -07:00
Gopkg.toml chore: update az go sdk to v32.5 and autorest v13 (#1793) 2019-08-22 13:26:30 -07:00
Jenkinsfile test: Add 'latestReleasedVersion' target to Jenkins jobs (#2133) 2019-10-11 11:08:30 -04:00
LICENSE
Makefile chore: update go toolchain to 1.12.10 (#2034) 2019-09-26 15:06:08 -07:00
OWNERS docs: Add devigned as owner (#1784) 2019-08-15 18:04:17 -07:00
README.md
README_zh-CN.md
labels.yaml
main.go
makedev.ps1 fix: verify LCOW in makedev.ps1 (#2037) 2019-09-27 13:20:26 -04:00
packer.mk ci: add VHD rg cleanup script (#1837) 2019-08-26 14:36:23 -04:00
test.mk chore: create parallel Jenkins pipeline for e2e tests (#1875) 2019-08-30 12:51:24 -04:00
versioning.mk

README.md

AKS Engine - Units of Kubernetes on Azure!

Build Status Coverage Status GoDoc Go Report Card

AKS Engine is the easiest way to provision a self-managed Kubernetes cluster on Azure.

Overview

AKS Engine provides convenient tooling to quickly bootstrap Kubernetes clusters on Azure. By leveraging ARM (Azure Resource Manager), AKS Engine helps you create, destroy and maintain clusters provisioned with basic IaaS resources in Azure. AKS Engine is also the library used by AKS for performing these operations to provide managed service implementations.

Getting started

Depending on how new you are to AKS Engine, you can try a tutorial, or just dive straight into the documentation.

Please see the FAQ for answers about AKS Engine and its progenitor ACS-Engine.

Sharpen your skills

The official AKS Engine documentation covers everything you need to know about AKS Engine (and then some).

Join the community

Want to get involved? The community guide covers everything you need to know about the AKS Engine community and how you can contribute.

Code of conduct

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.