kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #11606 from olemarkus/docs-snapshot-controller 

Add documentation about snapshot-controller
This commit is contained in:
Kubernetes Prow Robot 2021-05-26 22:18:23 -07:00 committed by GitHub
parent 46e1616467 4323a10130
commit adbbc6831d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 27 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/addons.md
View File

@ -190,6 +190,30 @@ The kOps CLI requires additional IAM permissions to manage the requisite EventBr
**Warning: If you switch between the two operating modes on an existing cluster, the old resources have to be manually deleted. For IMDS to Queue Processor, this means deleting the k8s nth daemonset. For Queue Processor to IMDS, this means deleting the k8s nth deployment and the AWS resources: the SQS queue, EventBridge rules, and ASG Lifecycle hooks.**
#### Snapshot controller
{{ kops_feature_table(kops_added_default='1.21', k8s_min='1.20') }}
Snapshot controller implements the [volume snapshot features](https://kubernetes.io/docs/concepts/storage/volume-snapshots/) of the Container Storage Interface (CSI).
You can enable the snapshot controller by adding the following to the cluster spec:
```yaml
spec:
snapshotController:
enabled: true
```
Note that the in-tree volume drivers do not support this feature. If you are running a cluster on AWS, you can enable the EBS CSI driver by adding the following:
```yaml
spec:
cloudConfig:
awsEBSCSIDriver:
enabled: true
```
## Static addons
The command `kops create cluster` does not support specifying addons to be added to the cluster when it is created. Instead they can be added after cluster creation using kubectl. Alternatively when creating a cluster from a yaml manifest, addons can be specified using `spec.addons`.

4
docs/releases/1.21-NOTES.md
View File

@ -32,13 +32,15 @@ See the [warm pool](https://kops.sigs.k8s.io/instance_groups/#warmpool-aws-only)
* kOps can now use Node Termination Handler's Queue Processor mode, which offers more functionality than the IMDS Processor mode. See [the addons page](https://kops.sigs.k8s.io/addons/#queue-processor-mode) for more information.
* New addon for the [CSI snapshot-controller](https://kops.sigs.k8s.io/addons/#snapshot-controller).
# Breaking changes
* Support for Kubernetes versions 1.13 and 1.14 has been removed.
# Required Actions
* To support [Node Termination Handler's Queue Process mode](/addons/#node-termination-handler), AWS cluster deletion now requires the kops CLI have `sqs:ListQueues` and `events:ListRules` permissions regardless of whether or not the addon is used.
* To support [Node Termination Handler's Queue Process mode](https://kops.sigs.k8s.io/addons/#node-termination-handler), AWS cluster deletion now requires the kops CLI have `sqs:ListQueues` and `events:ListRules` permissions regardless of whether or not the addon is used.
# Deprecations