mirror of https://github.com/k3s-io/k3s
9d2a5fe5e8
Automatic merge from submit-queue Implement dynamic provisioning (beta) of PersistentVolumes via StorageClass Implemented according to PR #26908. There are several patches in this PR with one huge code regen inside. * Please review the API changes (the first patch) carefully, sometimes I don't know what the code is doing... * `PV.Spec.Class` and `PVC.Spec.Class` is not implemented, use annotation `volume.alpha.kubernetes.io/storage-class` * See e2e test and integration test changes - Kubernetes won't provision a thing without explicit configuration of at least one `StorageClass` instance! * Multiple provisioning volume plugins can coexist together, e.g. HostPath and AWS EBS. This is important for Gluster and RBD provisioners in #25026 * Contradicting the proposal, `claim.Selector` and `volume.alpha.kubernetes.io/storage-class` annotation are **not** mutually exclusive. They're both used for matching existing PVs. However, only `volume.alpha.kubernetes.io/storage-class` is used for provisioning, configuration of provisioning with `Selector` is left for (near) future. * Documentation is missing. Can please someone write some while I am out? For now, AWS volume plugin accepts classes with these parameters: ``` kind: StorageClass metadata: name: slow provisionerType: kubernetes.io/aws-ebs provisionerParameters: type: io1 zone: us-east-1d iopsPerGB: 10 ``` * parameters are case-insensitive * `type`: `io1`, `gp2`, `sc1`, `st1`. See AWS docs for details * `iopsPerGB`: only for `io1` volumes. I/O operations per second per GiB. AWS volume plugin multiplies this with size of requested volume to compute IOPS of the volume and caps it at 20 000 IOPS (maximum supported by AWS, see AWS docs). * of course, the plugin will use some defaults when a parameter is omitted in a `StorageClass` instance (`gp2` in the same zone as in 1.3). GCE: ``` apiVersion: extensions/v1beta1 kind: StorageClass metadata: name: slow provisionerType: kubernetes.io/gce-pd provisionerParameters: type: pd-standard zone: us-central1-a ``` * `type`: `pd-standard` or `pd-ssd` * `zone`: GCE zone * of course, the plugin will use some defaults when a parameter is omitted in a `StorageClass` instance (SSD in the same zone as in 1.3 ?). No OpenStack/Cinder yet @kubernetes/sig-storage |
||
|---|---|---|
| .. | ||
| Kubemark_architecture.png | ||
| api-group.md | ||
| apiserver-watch.md | ||
| apparmor.md | ||
| client-package-structure.md | ||
| cluster-deployment.md | ||
| container-init.md | ||
| container-runtime-interface-v1.md | ||
| controller-ref.md | ||
| custom-metrics.md | ||
| deploy.md | ||
| deployment.md | ||
| disk-accounting.md | ||
| federated-api-servers.md | ||
| federation-high-level-arch.png | ||
| federation-lite.md | ||
| federation.md | ||
| flannel-integration.md | ||
| garbage-collection.md | ||
| gpu-support.md | ||
| high-availability.md | ||
| image-provenance.md | ||
| initial-resources.md | ||
| job.md | ||
| kubectl-login.md | ||
| kubelet-eviction.md | ||
| kubelet-systemd.md | ||
| kubelet-tls-bootstrap.md | ||
| kubemark.md | ||
| local-cluster-ux.md | ||
| metrics-plumbing.md | ||
| multiple-schedulers.md | ||
| network-policy.md | ||
| node-allocatable.md | ||
| node-allocatable.png | ||
| performance-related-monitoring.md | ||
| pleg.png | ||
| pod-cache.png | ||
| pod-lifecycle-event-generator.md | ||
| pod-resource-management.md | ||
| pod-security-context.md | ||
| protobuf.md | ||
| release-notes.md | ||
| rescheduler.md | ||
| rescheduling.md | ||
| resource-metrics-api.md | ||
| resource-quota-scoping.md | ||
| runtime-client-server.md | ||
| runtime-pod-cache.md | ||
| runtimeconfig.md | ||
| scalability-testing.md | ||
| scheduledjob.md | ||
| secret-configmap-downwarapi-file-mode.md | ||
| security-context-constraints.md | ||
| self-hosted-kubelet.md | ||
| selinux.md | ||
| service-discovery.md | ||
| service-external-name.md | ||
| templates.md | ||
| volume-ownership-management.md | ||
| volume-provisioning.md | ||
| volume-selectors.md | ||
| volumes.md | ||
