Add documentation for managing ECK file-based password length. #3322
Conversation
…r remote lookup indices (elastic#3317) This PR: - Adds mention of the support for lookup indices from remote clusters in lookup join ES|QL commands from 9.2 - Adds a section about the ability to view/create/edit lookup indices, depending on privileges, when using LOOKUP JOIN in an ES|QL query from Discover Dear reviewers, you can find direct preview links of the edited page in the 1st comment below Closes: elastic#3097
Signed-off-by: Michael Montgomery <[email protected]>
| 2. Restart the ECK operator | ||
|
|
||
| ```shell | ||
| kubectl delete pod -n elastic-system elastic-operator-0 |
There was a problem hiding this comment.
Operator will auto restart when its configuration changes
There was a problem hiding this comment.
Did you base this on a branch with unmerged commits. This seems unrelated.
|
|
||
| 1. Set the `password-length` in the `ConfigMap`. | ||
|
|
||
| ```yaml |
There was a problem hiding this comment.
This feels like it is duplicating https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/configure-eck.
There was a problem hiding this comment.
I would probably just mention the Helm value and ECK config flag and link to the existing docs on how to update it.
| enable-leader-election: true | ||
| elasticsearch-observation-interval: 10s | ||
| ubi-only: false | ||
| password-legnth: 64 |
There was a problem hiding this comment.
| password-legnth: 64 | |
| password-length: 64 |
Maybe just update the example in https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/configure-eck instead.
There was a problem hiding this comment.
Same here: accidentally included?
|
Looks like this PR contains this other unrelated PR #3317. Is it possible to clean it up :) |
|
closing in favor of #3339 which is based off the right branch. |
The following elastic/cloud-on-k8s#8817 is planned to be released with the ECK 3.2/Stack 9.2 release.