@helm-charts/elastic-kibana v6.5.4-alpha2-0.1.0

@helm-charts/elastic-kibana

Kibana

---
elasticsearchURL: 'http://elasticsearch-master:9200'

replicas: 1

# Extra environment variables to append to this nodeGroup
# This will be appended to the current 'env:' key. You can use any of the kubernetes env
# syntax here
extraEnvs:
#  - name: MY_ENVIRONMENT_VAR
#    value: the_value_goes_here

# A list of secrets and their paths to mount inside the pod
# This is useful for mounting certificates for security and for mounting
# the X-Pack license
secretMounts:
#  - name: elastic-certificates
#    secretName: elastic-certificates
#    path: /usr/share/elasticsearch/config/certs

image: 'docker.elastic.co/kibana/kibana'
imageTag: '6.5.4'
imagePullPolicy: 'IfNotPresent'

resources:
  requests:
    cpu: '100m'
    memory: '500m'
  limits:
    cpu: '1000m'
    memory: '1Gi'

# By default this will make sure two pods don't end up on the same node
# Changing this to a region would allow you to spread pods across regions
antiAffinityTopologyKey: 'kubernetes.io/hostname'

# Hard means that by default pods will only be scheduled if there are enough nodes for them
# and that they will never end up on the same node. Setting this to soft will do this "best effort"
antiAffinity: 'hard'

httpPort: 5601

# This is the max unavailable setting for the pod disruption budget
# The default value of 1 will make sure that kubernetes won't allow more than 1
# of your pods to be unavailable during maintenance
maxUnavailable: 1

updateStrategy:
  type: 'Recreate'

service:
  type: ClusterIP
  port: 5601

# Set this if you are setting server.ssl.enabled in Kibana.
# This value is a hostname accepted by the SSL certificate provided to kibana.
# Configuring this allows the readinessProbe to successfully check Kibana over HTTPS.
kibanaSSLHostname: localhost

ingress:
  enabled: false
  annotations:
    {}
    # kubernetes.io/ingress.class: nginx
    # kubernetes.io/tls-acme: "true"
  path: /
  hosts:
    - chart-example.local
  tls: []
  #  - secretName: chart-example-tls
  #    hosts:
  #      - chart-example.local

readinessProbe:
  failureThreshold: 3
  initialDelaySeconds: 10
  periodSeconds: 10
  successThreshold: 3
  timeoutSeconds: 5

imagePullSecrets: []
nodeSelector: {}
tolerations: []
affinity: {}

Kibana Helm Chart

This functionality is in alpha status and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but alpha features are not subject to the support SLA of official GA features.

This helm chart is a lightweight way to configure and run our official Kibana docker image

Requirements

• Kubernetes 1.8/1.9/1.10/1.11
• Helm

Installing

• Add the elastic helm charts repo

  helm repo add elastic https://helm.elastic.co

• Install it

  helm install --name kibana elastic/kibana --version 6.5.4-alpha2

Configuration

Examples

In examples/ you will find some example configurations. These examples are used for the automated testing of this helm chart

Default

• Deploy the default Elasticsearch helm chart
• Deploy Kibana with the default values

  cd examples/default
  make

• You can now setup a port forward and access Kibana at http://localhost:5601

  kubectl port-forward deployment/helm-kibana-default-kibana 5601

Security

• Deploy a security enabled Elasticsearch cluster
• Deploy Kibana with the security example

  cd examples/security
  make

• You can now setup a port forward and access Kibana at http://localhost:5601 with the credentials elastic:changeme

  kubectl port-forward deployment/helm-kibana-default-kibana 5601

Testing

This chart uses pytest to test the templating logic. The dependencies for testing can be installed from the requirements.txt in the parent directory.

pip install -r ../requirements.txt
make test

You can also use helm template to look at the YAML being generated

make template

It is possible to run all of the tests and linting inside of a docker container

make test