public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-14 00:53:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix RKE addons list and add/remove/switch behavior

Browse Source
This commit is contained in:
Sebastiaan van Steenis
2019-10-29 13:50:32 +01:00
committed by Denise
parent a65c745994
commit d6aa6531ae
3 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rke/latest/en/config-options/add-ons/_index.md
+1 -2
View File
@@ -13,12 +13,11 @@ RKE supports configuring pluggable add-ons in the cluster YML. Add-ons are used
These add-ons require images that can be found under the [`system_images` directive]({{< baseurl >}}/rke/latest/en/config-options/system-images/). For each Kubernetes version, there are default images associated with each add-on, but these can be overridden by changing the image tag in `system_images`.
There are a few things worth noting:
* In addition to these pluggable add-ons, you can specify an add-on that you want deployed after the cluster deployment is complete.
* RKE only adds additional add-ons when using `rke up` multiple times. RKE does **not** support removing of cluster add-ons when doing `rke up` with a different list of add-ons.
* As of v0.1.8, RKE will update an add-on if it is the same name.
* Prior to v0.1.8, update any add-ons by using `kubectl edit`.
## Critical and Non-Critical Add-ons
As of version v0.1.7, add-ons are split into two categories:
content/rke/latest/en/config-options/add-ons/dns/_index.md
+2
View File
@@ -16,6 +16,8 @@ RKE provides the following DNS providers that can be deployed as add-ons:
CoreDNS was made the default in RKE v0.2.5 when using Kubernetes 1.14 and higher. If you are using an RKE version lower than v0.2.5, kube-dns will be deployed by default.
> **Note:** If you switch from one DNS provider to another, the existing DNS provider will be removed before the new one is deployed.
# CoreDNS
_Available as of v0.2.5_
content/rke/latest/en/config-options/add-ons/network-plugins/_index.md
+3 -1
View File
@@ -10,6 +10,8 @@ RKE provides the following network plug-ins that are deployed as add-ons:
- Canal
- Weave
> **Note:** After you launch the cluster, you cannot change your network provider. Therefore, choose which network provider you want to use carefully, as Kubernetes doesn’t allow switching between network providers. Once a cluster is created with a network provider, changing network providers would require you tear down the entire cluster and all its applications.
By default, the network plug-in is `canal`. If you want to use another network plug-in, you need to specify which network plug-in to enable at the cluster level in the `cluster.yml`.
```yaml
@@ -96,4 +98,4 @@ Weave encryption can be enabled by passing a string password to the network prov
## Custom Network Plug-ins
It is possible to add a custom network plug-in by using the [user-defined add-on functionality]({{<baseurl>}}/rke/latest/en/config-options/add-ons/user-defined-add-ons/) of RKE. In the `addons` field, you can add the add-on manifest of a cluster that has the network plugin-that you want, as shown in [this example.]({{<baseurl>}}/rke/latest/en/config-options/add-ons/network-plugins/custom-network-plugin-example)
It is possible to add a custom network plug-in by using the [user-defined add-on functionality]({{<baseurl>}}/rke/latest/en/config-options/add-ons/user-defined-add-ons/) of RKE. In the `addons` field, you can add the add-on manifest of a cluster that has the network plugin-that you want, as shown in [this example.]({{<baseurl>}}/rke/latest/en/config-options/add-ons/network-plugins/custom-network-plugin-example)