diff --git a/docs/_print/index.html b/docs/_print/index.html index 20044d2e4..6d2593f15 100644 --- a/docs/_print/index.html +++ b/docs/_print/index.html @@ -251,8 +251,10 @@

2 - Install

REVISION: 1 TEST SUITE: None
-

Note: Helm has a known issue in version 3.13.0 that requires users to log in to the registry, even though the repo is public. -Upgrade to 3.13.1 or higher to avoid having to log in, see: https://github.com/kube-logging/logging-operator/issues/1522

+

Note:

Note: By default, the Logging operator Helm chart doesn’t install the logging resource. If you want to install it with Helm, set the logging.enabled value to true.

For details on customizing the installation, see the Helm chart values.

Validate the deployment

To verify that the installation was successful, complete the following steps.

  1. Check the status of the pods. You should see a new logging-operator pod.

    kubectl -n logging get pods
@@ -2998,8 +3000,10 @@ 
    5.3 - Store Nginx Access Logs in Am
 REVISION: 1
 TEST SUITE: None
    -

    Note: Helm has a known issue in version 3.13.0 that requires users to log in to the registry, even though the repo is public. -Upgrade to 3.13.1 or higher to avoid having to log in, see: https://github.com/kube-logging/logging-operator/issues/1522

  2. +

    Note:

      +
    • +

      Helm has a known issue in version 3.13.0 that requires users to log in to the registry, even though the repo is public.

      Upgrade to 3.13.1 or higher to avoid having to log in, see: https://github.com/kube-logging/logging-operator/issues/1522

    • +

      If you’re installing the Helm chart from Terraform, reference the repository as repository = "oci://ghcr.io/kube-logging/helm-charts/" (without the logging-operator suffix). Otherwise, you’ll get a 403 Forbidden error.

  • Create AWS secret

    If you have your $AWS_ACCESS_KEY_ID and $AWS_SECRET_ACCESS_KEY set you can use the following snippet.

        kubectl -n logging create secret generic logging-cloudwatch --from-literal "awsAccessKeyId=$AWS_ACCESS_KEY_ID" --from-literal "awsSecretAccessKey=$AWS_SECRET_ACCESS_KEY"

    Or set up the secret manually.

        kubectl -n logging apply -f - <<"EOF"
@@ -3093,8 +3097,10 @@ 
    5.4 - Transport all logs into Amazo
 REVISION: 1
 TEST SUITE: None
    -

    Note: Helm has a known issue in version 3.13.0 that requires users to log in to the registry, even though the repo is public. -Upgrade to 3.13.1 or higher to avoid having to log in, see: https://github.com/kube-logging/logging-operator/issues/1522

  • +

    Note:

  • Validate your deployment.

    • Configure the Logging operator

    1. Create AWS secret

      @@ -3222,8 +3228,10 @@

      5.5 - Store NGINX access logs in El REVISION: 1 TEST SUITE: None
      -

      Note: Helm has a known issue in version 3.13.0 that requires users to log in to the registry, even though the repo is public. -Upgrade to 3.13.1 or higher to avoid having to log in, see: https://github.com/kube-logging/logging-operator/issues/1522

    2. +

      Note:

    3. Validate your deployment.

    Configure the Logging operator

    1. Create the logging resource.

      kubectl -n logging apply -f - <<"EOF"
@@ -3468,8 +3476,10 @@ 
      Deploy the Logging o
 REVISION: 1
 TEST SUITE: None
      -

      Note: Helm has a known issue in version 3.13.0 that requires users to log in to the registry, even though the repo is public. -Upgrade to 3.13.1 or higher to avoid having to log in, see: https://github.com/kube-logging/logging-operator/issues/1522

    Configure the Logging operator

      +

      Note:

    Configure the Logging operator

    1. Create the logging resource with a persistent syslog-ng installation.

      kubectl apply -f - <<"EOF"
 apiVersion: logging.banzaicloud.io/v1beta1
@@ -3587,8 +3597,10 @@ 
      5.9 - Transport Nginx Access Logs i
 REVISION: 1
 TEST SUITE: None
      -

      Note: Helm has a known issue in version 3.13.0 that requires users to log in to the registry, even though the repo is public. -Upgrade to 3.13.1 or higher to avoid having to log in, see: https://github.com/kube-logging/logging-operator/issues/1522

    2. +

      Note:

    3. Validate your deployment.

    4. Create the logging resource.

      kubectl -n logging apply -f - <<"EOF"
 apiVersion: logging.banzaicloud.io/v1beta1
@@ -3707,8 +3719,10 @@ 
      5.10 - Store Nginx Access Logs in G
 REVISION: 1
 TEST SUITE: None
      -

      Note: Helm has a known issue in version 3.13.0 that requires users to log in to the registry, even though the repo is public. -Upgrade to 3.13.1 or higher to avoid having to log in, see: https://github.com/kube-logging/logging-operator/issues/1522

    5. +

      Note:

    6. Create the logging resource.

      kubectl -n logging apply -f - <<"EOF"
 apiVersion: logging.banzaicloud.io/v1beta1
 kind: Logging
@@ -4936,8 +4950,10 @@ 
      7.2 - Monitor your logging pipeline
 REVISION: 1
 TEST SUITE: None
      -

      Note: Helm has a known issue in version 3.13.0 that requires users to log in to the registry, even though the repo is public. -Upgrade to 3.13.1 or higher to avoid having to log in, see: https://github.com/kube-logging/logging-operator/issues/1522

    Install Minio

      +

      Note:

    Install Minio

    1. Create Minio Credential Secret

      kubectl -n logging create secret generic logging-s3 --from-literal=accesskey='AKIAIOSFODNN7EXAMPLE' --from-literal=secretkey='wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY'
    2. diff --git a/docs/commercial-support/index.html b/docs/commercial-support/index.html index ba1742388..7be2d3048 100644 --- a/docs/commercial-support/index.html +++ b/docs/commercial-support/index.html @@ -24,12 +24,12 @@ Axoflow If your company offers support for Logging operator and would like to be listed on this page, open a documentation issue."> - + - + @@ -588,7 +588,7 @@

      Commercial support for the Logging operator

      If you encounter problems while using the Logging operator the documentation does not address, open an issue or talk to us on Discord or on the CNCF Slack.

      The following companies provide commercial support for the Logging operator:

      If your company offers support for Logging operator and would like to be listed on this page, open a documentation issue.

      -Last modified August 5, 2024: Merge pull request #250 from kube-logging/containerd-fix-to-fluentbit-examples (9560233) +Last modified August 8, 2024: Merge pull request #251 from kube-logging/terraform-403-helm (81e5509)

    Community

    If you have questions about Logging operator or its components, get in touch with us on Slack!

    First, register on the CNCF Slack, then visit the #logging-operator Slack channel.

    Alternatively, you can also find us on Discord.

    If you’d like to contribute, see our contribution guidelines for details.

    -Last modified August 5, 2024: Merge pull request #250 from kube-logging/containerd-fix-to-fluentbit-examples (9560233) +Last modified August 8, 2024: Merge pull request #251 from kube-logging/terraform-403-helm (81e5509)