From d923ea73d383d8b0d4c20a9d186c06633d9a4adb Mon Sep 17 00:00:00 2001 From: Denise Schannon Date: Sat, 23 Mar 2019 23:53:06 -0700 Subject: [PATCH] update notice on self signed for kafka and fluentd --- .../en/cluster-admin/tools/logging/fluentd/_index.md | 4 +++- .../en/cluster-admin/tools/logging/kafka/_index.md | 10 ++-------- 2 files changed, 5 insertions(+), 9 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-admin/tools/logging/fluentd/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/logging/fluentd/_index.md index 987a400c7c0..b3c5ec6a655 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/logging/fluentd/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/logging/fluentd/_index.md @@ -29,4 +29,6 @@ After adding all the Fluentd servers, you have the option to select **Enable Gzi ## SSL Configuration -If your Fluentd servers are using TLS, you need to select **Use TLS**. If you are using a self-signed certificate, provide the **CA Certificate PEM**. You can copy and paste the certificate or upload it using the **Read from a file** button. +If your Fluentd servers are using TLS, you need to select **Use TLS**. Provide the **CA Certificate PEM**. You can copy and paste the certificate or upload it using the **Read from a file** button. + +>**Note:** Fluentd does not support self signed certificates. diff --git a/content/rancher/v2.x/en/cluster-admin/tools/logging/kafka/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/logging/kafka/_index.md index 71358a6c721..acb64a55cc2 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/logging/kafka/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/logging/kafka/_index.md @@ -26,15 +26,9 @@ If your Kafka cluster is using SSL for the **Broker**, you need to complete the 1. Provide the **Client Private Key** and **Client Certificate**. You can either copy and paste them or upload them by using the **Read from a file** button. - - You can use either a self-signed certificate or one provided by a certificate authority. +1. Provide the **CA Certificate PEM**. You can either copy and paste the certificate or upload it using the **Read from a file** button. - - You can generate a self-signed certificate using an openssl command. For example: - - ``` - openssl req -x509 -newkey rsa:2048 -keyout myservice.key -out myservice.cert -days 365 -nodes -subj "/CN=myservice.example.com" - ``` - -1. If you are using a self-signed certificate, provide the **CA Certificate PEM**. You can either copy and paste the certificate or upload it using the **Read from a file** button. +>**Note:** Kafka does not support self signed certificates. ### SASL configuration