@helm-charts/banzaicloud-stable-logging-operator v0.1.7-0.1.0

@helm-charts/banzaicloud-stable-logging-operator

Logging operator for Kubernetes based on Fluentd and Fluent-bit.

# Default values for logging-operator.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

replicaCount: 1

image:
  repository: banzaicloud/logging-operator
  tag: 0.1.6
  pullPolicy: IfNotPresent

nameOverride: ''
fullnameOverride: ''

# Namespace to watch fot LoggingOperator CRD
watchNamespace: ''

tls:
  enabled: false
  secretName: ''
  sharedKey: ''

fluentbit:
  enabled: true
  namespace: ''
  image:
    tag: 'latest'
    repository: 'fluent/fluent-bit'
    pullPolicy: 'IfNotPresent'

fluentd:
  enabled: true
  namespace: ''
  image:
    tag: 'v1.4.2'
    repository: 'banzaicloud/fluentd'
    pullPolicy: 'IfNotPresent'
  volumeModImage:
    tag: 'latest'
    repository: 'busybox'
    pullPolicy: 'IfNotPresent'
  configReloaderImage:
    tag: 'v0.2.2'
    repository: 'jimmidyson/configmap-reload'
    pullPolicy: 'IfNotPresent'
  fluentdPvcSpec:
    accessModes:
      - ReadWriteOnce
    resources:
      requests:
        storage: 21Gi

grafana:
  dashboard:
    enabled: true

## Role Based Access
## Ref: https://kubernetes.io/docs/admin/authorization/rbac/
##

rbac:
  enabled: true

## Define resources requests and limits for single Pods.
## ref: https://kubernetes.io/docs/user-guide/compute-resources/
## We usually recommend not to specify default resources and to leave this as a conscious
## choice for the user. This also increases chances charts run on environments with little
## resources, such as Minikube. If you do want to specify resources, uncomment the following
## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
##
resources:
  {}
  # limits:
  #   cpu: 100m
  #   memory: 128Mi
  # requests:
  #   cpu: 100m
  #   memory: 128Mi

## Define which Nodes the Pods are scheduled on.
## ref: https://kubernetes.io/docs/user-guide/node-selection/
##
nodeSelector: {}

## If specified, the pod's tolerations.
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
##
tolerations: []
# - key: "key"
#   operator: "Equal"
#   value: "value"
#   effect: "NoSchedule"

## Assign the Logging operator to run on specific nodes
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/
##
affinity: {}
# requiredDuringSchedulingIgnoredDuringExecution:
#   nodeSelectorTerms:
#   - matchExpressions:
#     - key: kubernetes.io/e2e-az-name
#       operator: In
#       values:
#       - e2e-az1
#       - e2e-az2

## SecurityContext holds pod-level security attributes and common container settings.
## This defaults to non root user with uid 1000 and gid 2000.	*v1.PodSecurityContext	false
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
##
securityContext:
  runAsNonRoot: true
  runAsUser: 1000
  fsGroup: 2000

Logging Operator Chart

Logging Operator Managed centralized logging component fluentd and fluent-bit instance on cluster.

tl;dr:

$ helm repo add banzaicloud-stable http://kubernetes-charts.banzaicloud.com/branch/master
$ helm repo update
$ helm install banzaicloud-stable/logging-operator

Introduction

This chart bootstraps an Logging Operator deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

• Kubernetes 1.8+ with Beta APIs enabled

Installing the Chart

To install the chart with the release name my-release:

$ helm install --name my-release banzaicloud-stable/logging-operator

The command deploys logging-operator on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The following tables lists the configurable parameters of the logging-operator chart and their default values.

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example:

$ helm install --name my-release -f values.yaml banzaicloud-stable/logging-operator

Tip: You can use the default values.yaml