Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RS Update 6.2.4 docs: Additional fixes and "tpyos" #1512

Merged
merged 4 commits into from
Aug 31, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/rs/installing-upgrading/upgrading.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ To upgrade Redis Enterprise Software, you:

2. _(Optional)_ Upgrade each database in the cluster.

You don't have to upgrade the databases in cluster, however, new features and important fixes might not be enabled until you do so.
You don't have to upgrade the databases in your cluster, however, new features and important fixes might not be enabled until you do so.

## Supported upgrade paths

Expand Down Expand Up @@ -110,7 +110,7 @@ Before upgrading a database:

### Redis database upgrade policy

In version 6.2.4, Redis Enterprise Software introduced the Redis database compatibility upgrade policy (`redis_upgrade_policy`). This policy controls the default value for the Redis database compatibility used to create new and update existing databases. To learn more, see [`rladmin upgrade`]({{< relref "/rs/references/rladmin.md#upgrade" >}}).)
In version 6.2.4, Redis Enterprise Software introduced the Redis database compatibility upgrade policy (`redis_upgrade_policy`). This policy controls the default value for the Redis database compatibility used to create new and update existing databases. To learn more, see [`rladmin upgrade`]({{< relref "/rs/references/rladmin.md#upgrade" >}}).

As of v6.2.4, this policy defaults to `major`, which limits Redis database compatibility to the most recent major release (v6.0, as of this writing.). To create databases using the most recent release of Redis, use `rladmin` to set the policy to `latest`.

Expand Down
5 changes: 4 additions & 1 deletion content/rs/references/rladmin.md
Original file line number Diff line number Diff line change
Expand Up @@ -592,7 +592,7 @@ rladmin tune db <db:id | name>
[ mtls_allow_weak_hashing <enabled | disabled> ]
[ mtls_allow_outdated_cert <enabled | disabled> ]
[ mtls_allow_no_xkusage <enabled | disabled> ]
[ data_internode_encryption <enabled | disabled> ]
[ data_internode_encryption <enable | disable> ]
```

| Optional Parameters | Description |
Expand Down Expand Up @@ -683,10 +683,13 @@ rladmin tune cluster
[ expose_hostnames_for_all_suffixes <enabled | disabled> ]
[ redis_upgrade_policy <latest | major> ]
[ default_redis_version <value> ]
[ data_internode_encryption <enable | disable> ]

```

| Optional Parameters | Description |
| - | - |
| data_internode_encryption | Enables or disables [internode encryption]({{< relref "/rs/security/internode-encryption.md" >}}) for new databases |
| default_concurrent_restore_actions | Default number of concurrent actions during node restore from a snapshot (positive integer or "all") |
| default_redis_version | The default Redis database compatibility version used to create new databases.<br/><br/> The value parameter should be a version number in the form of "x.y" where _x_ represents the major version number and _y_ represents the minor version number. The final value corresponds to the desired version of Redis.<br/><br/>You cannot set _default_redis_version_ to a value higher than that supported by the current _redis_upgrade_policy_ value. |
| expose_hostnames_for_all_suffixes | |
Expand Down
10 changes: 8 additions & 2 deletions content/rs/security/internode-encryption.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,8 +43,8 @@ To enable internode encryption for a database (also called _data plane encryptio

- Use the `rladmin` command-line utility to set the [data_internode_encryption]({{< relref "/rs/references/rladmin.md#tune" >}}) setting for the database:

``` text
rladmin tune db <database_id> data_internode_encryption enabled
``` shell
rladmin tune db <database_id> data_internode_encryption enable
```

- Use the Redis Enterprise Software REST API to set the `data_internode_encryption` setting for the database.
Expand All @@ -56,6 +56,12 @@ To enable internode encryption for a database (also called _data plane encryptio

When you change the data internode encryption setting for a database, all active remote client connections are disconnected. This restarts the internal (DMC) proxy and disconnects all client connections.

To enable data plane encryption by default for new databases, use `rladmin` to tune the cluster:

``` shell
rladmin tune cluster data_internode_encryption enable
```

## Encryption ciphers and settings

To encrypt internode communications, Redis Enterprise Software uses TLS 1.2 and the following Cipher suites:
Expand Down