public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 20:48:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'v2.5.6' into istio-resources

Browse Source
This commit is contained in:
Catherine Luse
2021-02-23 19:56:16 -07:00
committed by GitHub
parent e996e66725 84f908742f
commit acb9b43417
3 changed files with 31 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.5/en/admin-settings/rbac/global-permissions/_index.md
+17
View File
@@ -43,6 +43,20 @@ CATTLE_RESTRICTED_DEFAULT_ADMIN=true
```
### List of `restricted-admin` Permissions
The permissions for the `restricted-admin` role differ based on the Rancher version.
{{% tabs %}}
{{% tab "v2.5.6" %}}
The `restricted-admin` permissions are as follows:
- Has full admin access to all downstream clusters managed by Rancher.
- Can add other users and assign them to clusters outside of the local cluster.
- Can create other restricted admins.
{{% /tab %}}
{{% tab "v2.5.0-v2.5.5" %}}
The `restricted-admin` permissions are as follows:
- Has full admin access to all downstream clusters managed by Rancher.
@@ -51,6 +65,9 @@ The `restricted-admin` permissions are as follows:
- Can create other restricted admins.
- Cannot grant any permissions in the local cluster they don't currently have. (This is how Kubernetes normally operates)
{{% /tab %}}
{{% /tabs %}}
### Upgrading from Rancher with a Hidden Local Cluster
Prior to Rancher v2.5, it was possible to run the Rancher server using this flag to hide the local cluster:
content/rancher/v2.5/en/logging/_index.md
+7
View File
@@ -314,6 +314,13 @@ spec:
In the above example, we ensure that our pod only runs on Linux nodes, and we add a `toleration` for the taint we have on all of our Linux nodes.
You can do the same with Rancher's existing taints, or with your own custom ones.
# Working with a Custom Docker Root Directory
_Applies to v2.5.6+_
If using a custom Docker root directory, you can set `global.dockerRootDirectory` in `values.yaml`.
This will ensure that the Logging CRs created will use your specified path rather than the default Docker `data-root` location.
### Windows Support
Clusters with Windows workers support exporting logs from Linux nodes, but Windows node logs are currently unable to be exported.
content/rancher/v2.x/en/logging/v2.5/_index.md
+7
View File
@@ -276,6 +276,13 @@ Let's break down what is happening here. First, we create a deployment of a cont
> **Note on syslog** Official `syslog` support is coming in Rancher v2.5.4. However, this example still provides an overview on using unsupported plugins.
# Working with a Custom Docker Root Directory
_Applies to v2.5.6+_
If using a custom Docker root directory, you can set `global.dockerRootDirectory` in `values.yaml`.
This will ensure that the Logging CRs created will use your specified path rather than the default Docker `data-root` location.
# Working with Taints and Tolerations
"Tainting" a Kubernetes node causes pods to repel running on that node.