VictoriaLogs Single #

[]

Add extra specs dynamically to this chart

fluent-bit.config.filters: |
  [FILTER]
      Name kubernetes
      Match kube.*
      Merge_Log On
      Keep_Log On
      K8S-Logging.Parser On
      K8S-Logging.Exclude On
  [FILTER]
      Name                nest
      Match               *
      Wildcard            pod_name
      Operation lift
      Nested_under kubernetes
      Add_prefix   kubernetes_

FluentBit configuration filters

fluent-bit.config.outputs: |
  [OUTPUT]
      Name http
      Match kube.*
      Host '{{ include "victoria-logs.server.fullname" . }}'
      port 9428
      compress gzip
      uri /insert/jsonline?_stream_fields=stream,kubernetes_pod_name,kubernetes_container_name,kubernetes_namespace_name&_msg_field=log&_time_field=date
      format json_lines
      json_date_format iso8601
      header AccountID 0
      header ProjectID 0

Note that Host must be replaced to match your VictoriaLogs service name Default format points to VictoriaLogs service.

/var/log

varlog

/var/lib/docker/containers

varlibdockercontainers

true

/var/log

varlog

/var/lib/docker/containers

varlibdockercontainers

false

Enable deployment of fluent-bit

{}

auto

""

[]

""

null

Overrides the full name of server component

server

Server container name

false

See kubectl explain poddisruptionbudget.spec for more. Details are here

{}

true

Print chart notes

{}

Pod affinity

""

Container workdir

{}

Use an alternate scheduler, e.g. “stork”. ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/ schedulerName:

true

Enable deployment of server component. Deployed as StatefulSet

[]

Additional environment variables (ex.: secret tokens, flags) https://github.com/VictoriaMetrics/VictoriaMetrics#environment-variables

[]

envflag.enable: "true"
envflag.prefix: VM_
loggerFormat: json

Extra command line arguments for container of component

[]

Extra containers to run in a pod with Victoria Logs container

[]

Additional hostPath mounts

{}

Sts/Deploy additional labels

[]

Extra Volume Mounts for the container

[]

Extra Volumes for the pod

IfNotPresent

Image pull policy

""

Image registry

victoriametrics/victoria-logs

Image repository

""

Image tag

victorialogs

[]

Image pull secrets

null

Ingress annotations

false

Enable deployment of ingress for server component

{}

Ingress extra labels

[]

Prefix

pathType is only for k8s >= 1.1=

[]

Array of TLS objects

[]

Init containers for Victoria Logs Pod

{}

Pod’s node selector. Details are here

- ReadWriteOnce

Array of access modes. Must match those of existing PV or dynamic provisioner. Details are here

{}

Persistant volume annotations

false

Create/use Persistent Volume Claim for server component. Empty dir if false

""

Existing Claim name. If defined, PVC must be created manually before volume will be bound

{}

Bind Persistent Volume by labels. Must match all labels of targeted PV.

/storage

Mount path. Server data Persistent Volume mount root path.

3Gi

Size of the volume. Should be calculated based on the logs you send and retention policy you set.

""

StorageClass to use for persistent volume. Requires server.persistentVolume.enabled: true. If defined, PVC created automatically

""

Mount subpath

{}

Pod’s annotations

{}

Pod’s additional labels

OrderedReady

Pod’s management policy

enabled: true
fsGroup: 2000
runAsNonRoot: true
runAsUser: 1000

Pod’s security context. Details are here

""

Name of Priority Class

failureThreshold: 10
initialDelaySeconds: 30
periodSeconds: 30
tcpSocket: {}
timeoutSeconds: 5

Indicates whether the Container is running. If the liveness probe fails, the kubelet kills the Container, and the Container is subjected to its restart policy. If a Container does not provide a liveness probe, the default state is Success.

failureThreshold: 3
httpGet: {}
initialDelaySeconds: 5
periodSeconds: 15
timeoutSeconds: 5

Indicates whether the Container is ready to service requests. If the readiness probe fails, the endpoints controller removes the Pod’s IP address from the endpoints of all Services that match the Pod. The default state of readiness before the initial delay is Failure. If a Container does not provide a readiness probe, the default state is Success.

{}

Indicates whether the Container is done with potentially costly initialization. If set it is executed first. If it fails Container is restarted. If it succeeds liveness and readiness probes takes over.

1

Replica count

{}

Resource object. Details are here

1

Data retention period in month

allowPrivilegeEscalation: false
capabilities:
    drop:
        - ALL
enabled: true
readOnlyRootFilesystem: true

Security context to be added to server pods

{}

Service annotations

""

Service ClusterIP

[]

Service External IPs. Details are here

""

""

[]

""

{}

Service labels

""

Service load balacner IP

[]

Load balancer source range

9428

Service port

ClusterIP

Service type

{}

Service Monitor annotations

{}

Basic auth params for Service Monitor

false

Enable deployment of Service Monitor for server component. This is Prometheus operator object

{}

Service Monitor labels

[]

Service Monitor metricRelabelings

[]

Service Monitor relabelings

true

Creates statefulset instead of deployment, useful when you want to keep the cache

OrderedReady

Deploy order policy for StatefulSet pods

60

Pod’s termination grace period in seconds

[]

Node tolerations for server scheduling to nodes with taints. Details are here