kube-logging / kube-logging.github.io Goto Github PK

https://kube-logging.dev/4.2/docs/configuration/extensions/tailer-webhook/

The following things should be fixed:

• File tailer example has a second container which is not needed, the snippet's indentation is not right either
• kubectl get pod test-pod -o json | jq '.spec.containers | map(.name)' output should be the actual output
• kubectl logs test-pod test; echo $? should use the actual name and it's output should have a few more lines
• Using the annotation for the caBundle injection as mentioned above it:

For example: you can inject the CA with a simple cert-manager cert-manager.io/inject-ca-from: logging/webhook-tls annotation on the mutatingwebhookconfiguration resource.

Like this:

---
apiVersion: admissionregistration.k8s.io/v1
kind: MutatingWebhookConfiguration
metadata:
  name: sample-webhook-cfg
  namespace: logging
  labels:
    app: sample-webhook
  annotations:
    cert-manager.io/inject-ca-from: logging/webhook-tls
webhooks:
  - name: sample-webhook.banzaicloud.com
    clientConfig:
      service:
        name: logging-webhooks
        namespace: logging
        path: "/tailer-webhook"
    rules:
      - operations: [ "CREATE" ]
        apiGroups: [""]
        apiVersions: ["v1"]
        resources: ["pods"]
        scope: "*"
    failurePolicy: Ignore
    sideEffects: None
    admissionReviewVersions: [v1]

• We should also expand it with a section that describes using the cert-manager to issue a simple certificate.

Describe the bug
Doc says Elasticsearch instead of kafka.

Create an Elasticsearch output definition.

Steps to reproduce the issue:
Go to https://banzaicloud.com/docs/one-eye/logging-operator/quickstarts/kafka-nginx/

Expected behavior
It should say kafka.

https://github.com/kube-logging/kube-logging.github.io/blob/master/content/docs/quickstarts/single.md

FluentbitAgents are not processed, No fluentd are deployed.

Setting logging.enabled: true fixes it

Documentation for the relabeling feature:
kube-logging/logging-operator#1294

Describe the bug
There are two kind of descriptors of the detectExceptions. Once it represented as an array in filters, once it's an element of the filters.spec.

Describe the bug
The example configuration for the Amazon Elatsearch output is incorrect. It appears that it was copied from the Amazon Kinesis Stream documentation.

Steps to reproduce the issue:
Read example output configuration for Amazon Elasticsearch output plugin:
https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/aws_elasticsearch/#example-output-configurations

Expected behavior
Example configuration should be for Amazon Elaticsearch, not Amazon Kinesis Stream.

Screenshots

This issue was automatically created by Allstar.

Security Policy Violation
Dismiss stale reviews not configured for branch master

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

cluster output manifest

apiVersion: logging.banzaicloud.io/v1beta1
kind: SyslogNGClusterOutput
metadata:
 name: loki-output
 namespace: logging
spec:
  loki:
    url: https://devops249.ef.com/loki/api/v1/push
    labels:
      "app_kubernetes_io_name": "${json#kubernetes#labels#app.kubernetes.io/name}"
      "app_kubernetes_io_instance": "${json#kubernetes#labels#app.kubernetes.io/instance}"
      "app_kubernetes_io_component": "${json#kubernetes#labels#app.kubernetes.io/component}"
      "namespace_name": ${json#kubernetes#namespace_name}
      "pod_name": ${json#kubernetes#pod_name}
    timestamp: "msg"
    template: "$ISODATE $HOST $MSGHDR$MSG"
    auth:
      insecure: {}
      tls:
         peer_verify: false

get the pods

root@devops248:/tmp# k -n logging get pods
NAME                                               READY   STATUS      RESTARTS   AGE
logging-operator-ff99697f7-2hj7h                   1/1     Running     0          26h
logging-operator-ff99697f7-htpx5                   1/1     Running     0          26h
logging-operator-ff99697f7-rm5w6                   1/1     Running     0          26h
logging-operator-ff99697f7-wbnxl                   1/1     Running     0          26h
logging-operator-ff99697f7-xwjsn                   1/1     Running     0          26h
syslog-ng-logging-fluentbit-pk45j                  1/1     Running     0          3h26m
syslog-ng-logging-syslog-ng-0                      2/2     Running     0          3h26m
syslog-ng-logging-syslog-ng-configcheck-b947403f   0/1     Error       0          5s
syslog-ng-logging-syslog-ng-configcheck-f0aad5ab   0/1     Completed   0          2m1s

logs for the config pod

root@devops248:/tmp# k -n logging logs -f syslog-ng-logging-syslog-ng-configcheck-b947403f
Setting current version as config version; version='4.5'
Error parsing within destination, syntax error, unexpected KW_TLS, expecting ')' in /etc/syslog-ng/config/syslog-ng.conf:18:26-18:29:
13              };
14          };
15      };
16
17      destination "clusteroutput_logging_loki-output" {
18---->     loki(auth(insecure() tls(peer_verify(no))) labels(
18---->                          ^^^
19              "app_kubernetes_io_component" => "${json#kubernetes#labels#app.kubernetes.io/component}"
20              "app_kubernetes_io_instance" => "${json#kubernetes#labels#app.kubernetes.io/instance}"
21              "app_kubernetes_io_name" => "${json#kubernetes#labels#app.kubernetes.io/name}"
22              "namespace_name" => "${json#kubernetes#namespace_name}"
23              "pod_name" => "${json#kubernetes#pod_name}"

however the CRDS say this is an object under the loki's
link to CRD object

enhance k8s metada link goes to repo that does not exist, is there a repo I can view to understand and configure the plugin better?
https://github.com/SumoLogic/sumologic-kubernetes-collection/tree/main/fluent-plugin-enhance-k8s-metadata

my use case is to append namespace labels pod logs collected by the logging operator at /var/log/containers
is there a method this can be accomplished now?
Here are some of the previous issues on this topic that i've viewed, doesnt seem like this feature has been added, would appreciate any help on configuring enhance k8s metadata or otherwise!
kube-logging/logging-operator#1148
kube-logging/logging-operator#704

https://kube-logging.dev/docs/logging-infrastructure/fluentbit/

• We should update examples to use fluentbitagent everywhere
• We should have have a loggingRef example as well

The YAML example at the top of this page https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/opensearch/ shows a ssl_version option being configured. However, when a ClusterOutput is created as YAML using that option, the change is not saved.

Weirdly, there seems to be a description of the ssl_version option next to an unrelated option, remove_keys_on_update:

If you want to configure SSL/TLS version, you can specify ssl_version parameter. [SSLv23, TLSv1, TLSv1_1, TLSv1_2] Remove keys on update will not update the configured keys in OpenSearch when a record is being updated. This setting only has any effect if the write operation is update or upsert.

I'm guessing what happened is that the version option was removed and the docs have yet to reflect this.

The links are not working

Deploy the Logging operator from Kubernetes Manifests >
Create a ServiceAccount and install cluster roles >
https://raw.githubusercontent.com/banzaicloud/logging-operator-docs/master/docs/deploy/manifests/rbac.yaml -> Error 404 File not found

Could you please double check the links?

The documentation for Redis ClusterOutputs specifies TTL for keys: https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/redis/#ttl-int-optional-output-config-ttl

What unit is that in? Seconds?