Helm Configuration¶

Parameters¶

Below is an exhaustive list of Helm parameters you can specify to modify the behavior of the LiteSpeed Ingress Controller.

Specify each parameter using the --set key=value[,key=value] argument to helm install or helm upgrade. For example,

$ helm install ls-k8s-webadc --set image.pullPolicy=Always helm/ls-k8s-webadc

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

$ helm install my-release -f values.yaml helm/ls-k8s-webadc

Global parameters¶

Common parameters¶

LiteSpeed Ingress Controller parameters¶

LiteSpeed Ingress deployment / daemonset parameters¶

Default backend parameters¶

Traffic exposure parameters¶

RBAC parameters¶

Role-Based Access Control parameters include:

Autoscaling parameteters¶

Other parameters¶

Configuration and installation details¶

Rolling VS Immutable tags¶

It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.

Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.

Sidecars and Init Containers¶

If you have a need for additional containers to run within the same pod as the LiteSpeed Ingress Controller (e.g. an additional metrics or logging exporter), you can do so via the sidecars config parameter. Simply define your container according to the Kubernetes container spec.

sidecars:
  - name: your-image-name
    image: your-image
    imagePullPolicy: Always
    ports:
      - name: portname
       containerPort: 1234

Similarly, you can add extra init containers using the initContainers parameter.

initContainers:
  - name: your-image-name
    image: your-image
    imagePullPolicy: Always
    ports:
      - name: portname
        containerPort: 1234

Deploying extra resources¶

There are cases where you may want to deploy extra objects, such a ConfigMap containing your app's configuration or some extra deployment with a micro service used by your app. For covering this case, the chart allows adding the full specification of other objects using the extraDeploy parameter.

Setting Pod's affinity¶

This chart allows you to set your custom affinity using the affinity parameter. Find more information about Pod's affinity in the kubernetes documentation.

As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the bitnami/common chart. To do so, set the podAffinityPreset, podAntiAffinityPreset, or nodeAffinityPreset parameters.

And if necessary you can hard code the node the Deployment schedules a pod to with nodeName.