Changes auth.enableLoopbackUser parameter description (#16958)

* Changes auth.enableLoopbackUser parameter description

Signed-off-by: Rafael Rios Saavedra <rrios@vmware.com>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Signed-off-by: Rafael Rios Saavedra <rrios@vmware.com>

* Update README.md

Signed-off-by: Rafael Rios Saavedra <rrios@vmware.com>

---------

Signed-off-by: Rafael Rios Saavedra <rrios@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Rafael Ríos Saavedra
2023-05-30 11:00:35 +02:00
committed by GitHub
parent 911006d10e
commit 7bd397aa2e
2 changed files with 3 additions and 3 deletions

View File

@@ -94,7 +94,7 @@ The command removes all the Kubernetes components associated with the chart and
| `auth.password` | RabbitMQ application password | `""` |
| `auth.securePassword` | Whether to set the RabbitMQ password securely. This is incompatible with loading external RabbitMQ definitions and 'true' when not setting the auth.password parameter. | `true` |
| `auth.existingPasswordSecret` | Existing secret with RabbitMQ credentials (must contain a value for `rabbitmq-password` key) | `""` |
| `auth.enableLoopbackUser` | Enable Loopback user access? Be advised, that enabling the loopback user is a possible security risk! | `false` |
| `auth.enableLoopbackUser` | If enabled, the user `auth.username` can only connect from localhost | `false` |
| `auth.erlangCookie` | Erlang cookie to determine whether different nodes are allowed to communicate with each other | `""` |
| `auth.existingErlangSecret` | Existing secret with RabbitMQ Erlang cookie (must contain a value for `rabbitmq-erlang-cookie` key) | `""` |
| `auth.tls.enabled` | Enable TLS support on RabbitMQ | `false` |
@@ -724,4 +724,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.

View File

@@ -142,7 +142,7 @@ auth:
## existingPasswordSecret: name-of-existing-secret
##
existingPasswordSecret: ""
## @param auth.enableLoopbackUser Enable Loopback user access? Be advised, that enabling the loopback user is a possible security risk!
## @param auth.enableLoopbackUser If enabled, the user `auth.username` can only connect from localhost
##
enableLoopbackUser: false
## @param auth.erlangCookie Erlang cookie to determine whether different nodes are allowed to communicate with each other