40ef612781
Automatic merge from submit-queue (batch tested with PRs 43177, 43202) Rename default storageclasses From UX perspective, 'default' is a bad name for the default storage class: ``` $ kubectl get storageclass NAME TYPE default (default) kubernetes.io/aws-ebs ``` This is sort of OK, it gets more confusing when user is not happy with the preinstalled default storage class and creates its own and makes it default: ``` NAME TYPE default kubernetes.io/aws-ebs iops (default) kubernetes.io/aws-ebs ``` This PR uses name of the underlying storage as name of the default storage class: ``` NAME TYPE gp2 (default) kubernetes.io/aws-ebs ``` On GCE (and many others): ``` NAME TYPE standard (default) kubernetes.io/gce-pd ``` Detailed list of names of new default storage classes: * AWS: `gp2` * GCE: `standard` (from pd-standard) * vSphere: `thin` * Cinder does not have a default - it's up to OpenStack admin to set some default and it can change at any time, using `standard` as the class name. * I was not able to find details about Azure, using `standard` too. @justinsb @jingxu97 @kerneltime @colemickens, PTAL quickly so we can catch 1.6. ```release-note NONE ``` For 1.6 release manager, this PR just renames objects in addon manager. |
||
|---|---|---|
| .github | ||
| api | ||
| build | ||
| cluster | ||
| cmd | ||
| docs | ||
| examples | ||
| federation | ||
| Godeps | ||
| hack | ||
| hooks | ||
| logo | ||
| pkg | ||
| plugin | ||
| staging | ||
| test | ||
| third_party | ||
| translations | ||
| vendor | ||
| .bazelrc | ||
| .gazelcfg.json | ||
| .generated_files | ||
| .gitattributes | ||
| .gitignore | ||
| BUILD.bazel | ||
| CHANGELOG.md | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| labels.yaml | ||
| LICENSE | ||
| Makefile | ||
| Makefile.generated_files | ||
| OWNERS | ||
| OWNERS_ALIASES | ||
| README.md | ||
| Vagrantfile | ||
| WORKSPACE | ||
Kubernetes
Kubernetes is an open source system for managing containerized applications across multiple hosts, providing basic mechanisms for deployment, maintenance, and scaling of applications.
Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practices from the community.
Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF). If you are a company that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's involved and how Kubernetes plays a role, read the CNCF announcement.
To start using Kubernetes
See our documentation on kubernetes.io.
Try our interactive tutorial.
Take a free course on Scalable Microservices with Kubernetes.
To start developing Kubernetes
The community repository hosts all information about building Kubernetes from source, how to contribute code and documentation, who to contact about what, etc.
If you want to build Kubernetes right away there are two options:
You have a working Go environment.
$ go get -d k8s.io/kubernetes
$ cd $GOPATH/src/k8s.io/kubernetes
$ make
You have a working Docker environment.
$ git clone https://github.com/kubernetes/kubernetes
$ cd kubernetes
$ make quick-release
If you are less impatient, head over to the developer's documentation.
Support
If you need support, start with the troubleshooting guide and work your way through the process that we've outlined.
That said, if you have questions, reach out to us one way or another.