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

Rename _kops_ to kOps in the docs

This commit is contained in:
Ciprian Hacman 2020-10-21 09:09:52 +03:00
parent 61708eae6b
commit c9cc319423
9 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/cluster_spec.md
View File

@ -415,7 +415,7 @@ spec:
watchIngress: true
```
Default _kops_ behavior is false. `watchIngress: true` uses the default _dns-controller_ behavior which is to watch the ingress controller for changes. Set this option at risk of interrupting Service updates in some cases.
Default kOps behavior is false. `watchIngress: true` uses the default _dns-controller_ behavior which is to watch the ingress controller for changes. Set this option at risk of interrupting Service updates in some cases.
## kubelet

2
docs/getting_started/aws.md
View File

@ -406,7 +406,7 @@ kops delete cluster --name ${NAME} --yes
## Next steps
Now that you have a working _kops_ cluster, read through the [recommendations for production setups guide](production.md)
Now that you have a working kOps cluster, read through the [recommendations for production setups guide](production.md)
## Feedback

2
docs/getting_started/digitalocean.md
View File

@ -71,4 +71,4 @@ kOps for DigitalOcean currently does not support these features:
# Next steps
Now that you have a working _kops_ cluster, read through the [recommendations for production setups guide](production.md) to learn more about how to configure _kops_ for production workloads.
Now that you have a working kOps cluster, read through the [recommendations for production setups guide](production.md) to learn more about how to configure kOps for production workloads.

2
docs/getting_started/gce.md
View File

@ -188,4 +188,4 @@ After you've double-checked you're deleting exactly what you want to delete, run
# Next steps
Now that you have a working _kops_ cluster, read through the [recommendations for production setups guide](production.md) to learn more about how to configure _kops_ for production workloads.
Now that you have a working kOps cluster, read through the [recommendations for production setups guide](production.md) to learn more about how to configure kOps for production workloads.

2
docs/getting_started/openstack.md
View File

@ -219,4 +219,4 @@ spec:
# Next steps
Now that you have a working _kops_ cluster, read through the [recommendations for production setups guide](production.md) to learn more about how to configure _kops_ for production workloads.
Now that you have a working kOps cluster, read through the [recommendations for production setups guide](production.md) to learn more about how to configure kOps for production workloads.

4
docs/getting_started/production.md
View File

@ -1,6 +1,6 @@
# Recommendations for production setups
The getting started-documentation is a fast way of spinning up a Kubernetes cluster, but there are some aspects of _kops_ that require extra consideration. This document will highlight the most important things you should know about before deploying your production workload.
The getting started-documentation is a fast way of spinning up a Kubernetes cluster, but there are some aspects of kOps that require extra consideration. This document will highlight the most important things you should know about before deploying your production workload.
## High availability
@ -10,7 +10,7 @@ Read through the [high availability documentation](../operations/high_availabili
## Networking
The default networking of _kops_, kubenet, is **not** recommended for production. Most importantly, it does not support network policies, nor does it support internal networking.
The default networking of kOps, kubenet, is **not** recommended for production. Most importantly, it does not support network policies, nor does it support internal networking.
Read through the [networking page](../networking.md) and choose a stable CNI.

2
docs/gpu.md
View File

@ -35,7 +35,7 @@ Also note the node label we set. This will be used to ensure the GPU Operator re
## Install GPU Operator
GPU Operator is installed using `helm`. See the [general install instructions for GPU Operator](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/getting-started.html#install-gpu-operator).
In order to match the _kops_ environment, create a `values.yaml` file with the following content:
In order to match the kOps environment, create a `values.yaml` file with the following content:
```yaml
operator:

18
docs/operations/images.md
View File

@ -1,6 +1,6 @@
# Images
As of Kubernetes 1.18 the default images used by _kops_ are the **[official Ubuntu 20.04](#ubuntu-2004-focal)** images.
As of Kubernetes 1.18 the default images used by kOps are the **[official Ubuntu 20.04](#ubuntu-2004-focal)** images.
You can choose a different image for an instance group by editing it with `kops edit ig nodes`. You should see an `image` field in one of the following formats:
@ -22,7 +22,7 @@ You can find the name for an image using:
## Security Updates
Automated security updates are handled by _kops_ for Debian, Flatcar and Ubuntu distros. This can be disabled by editing the cluster configuration:
Automated security updates are handled by kOps for Debian, Flatcar and Ubuntu distros. This can be disabled by editing the cluster configuration:
```yaml
spec:
@ -31,7 +31,7 @@ spec:
## Distros Support Matrix
The following table provides the support status for various distros with regards to _kops_ version:
The following table provides the support status for various distros with regards to kOps version:
| Distro | Experimental | Stable | Deprecated | Removed |
| ------------ | -----------: | -----: | ---------: | ------: |
@ -56,7 +56,7 @@ The following table provides the support status for various distros with regards
Amazon Linux 2 is based on Kernel version **4.14** which fixes some of the bugs present in RHEL/CentOS 7 and effects are less visible, but it's still quite old.
For _kops_ versions 1.16 and 1.17, the only supported Docker version is `18.06.3`. Newer versions of Docker cannot be installed due to missing dependencies for `container-selinux`. This issue is fixed in _kops_ **1.18**.
For kOps versions 1.16 and 1.17, the only supported Docker version is `18.06.3`. Newer versions of Docker cannot be installed due to missing dependencies for `container-selinux`. This issue is fixed in kOps **1.18**.
Available images can be listed using:
@ -212,27 +212,27 @@ aws ec2 describe-images --region us-east-1 --output table \
### CoreOS
Support for CoreOS was removed in _kops_ 1.18.
Support for CoreOS was removed in kOps 1.18.
You should consider using [Flatcar](#flatcar) as a replacement.
### Debian 8 (Jessie)
Support for Debian 8 (Jessie) was removed in _kops_ 1.18.
Support for Debian 8 (Jessie) was removed in kOps 1.18.
### Kope.io
Support for _kope.io_ images is deprecated. These images were the default until Kubernetes 1.18, when they were replaced by the [official Ubuntu 20.04](#ubuntu-2004-focal) images.
The _kope.io_ images were based on [Debian 9 (Stretch)](#debian-9-stretch) and had all packages required by _kops_ pre-installed. Other than that, the changes to the official Debian images were [minimal](https://github.com/kubernetes-sigs/image-builder/blob/master/images/kube-deploy/imagebuilder/templates/1.18-stretch.yml#L174-L198).
The _kope.io_ images were based on [Debian 9 (Stretch)](#debian-9-stretch) and had all packages required by kOps pre-installed. Other than that, the changes to the official Debian images were [minimal](https://github.com/kubernetes-sigs/image-builder/blob/master/images/kube-deploy/imagebuilder/templates/1.18-stretch.yml#L174-L198).
### Ubuntu 16.04 (Xenial)
Support for Ubuntu 16.04 (Xenial) is deprecated and will be removed in _kops_ 1.20.
Support for Ubuntu 16.04 (Xenial) is deprecated and will be removed in kOps 1.20.
## Owner aliases
_kops_ supports owner aliases for the official accounts of supported distros:
kOps supports owner aliases for the official accounts of supported distros:
* `kope.io` => `383156758163`
* `amazon` => `137112412989`

2
docs/releases/1.10-NOTES.md
View File

@ -51,7 +51,7 @@ None known at this time
* Add SubnetType tags to run_in_existing_vpc docs [@tsupertramp](https://github.com/tsupertramp) [#5094](https://github.com/kubernetes/kops/pull/5094)
* Typo fix: actually->actually/overide->override/to to->to [@AdamDang](https://github.com/AdamDang) [#5099](https://github.com/kubernetes/kops/pull/5099) (fixed typo in message for verify - @chrisz100)
* Typo fix detaults->defaults [@AdamDang](https://github.com/AdamDang) [#5067](https://github.com/kubernetes/kops/pull/5067)
* Update upgrade_from_kops_1.6_to_1.7_calico_cidr_migration.md [@AdamDang](https://github.com/AdamDang) [#5107](https://github.com/kubernetes/kops/pull/5107)
* Update upgrade_fromkOps1.6_to_1.7_calico_cidr_migration.md [@AdamDang](https://github.com/AdamDang) [#5107](https://github.com/kubernetes/kops/pull/5107)
* Typo fix: healthly->healthy [@AdamDang](https://github.com/AdamDang) [#5125](https://github.com/kubernetes/kops/pull/5125)
* Remove custom Statement IDs from IAM Policy Statements [@KashifSaadat](https://github.com/KashifSaadat) [#4958](https://github.com/kubernetes/kops/pull/4958)
* Adds new kops logo [@iMartyn](https://github.com/iMartyn) [#5113](https://github.com/kubernetes/kops/pull/5113)