Managing Ingress

Overview

Fissile does not manage ingress by itself, not directly.

It only provides a variable usable in charts which when set is expected to activate ingress-related templating in the chart, and which will suppress the standard support for services.loadbalanced provided by fissile.

API to role manifests

The new variable is named services.ingress.

Its default value is nil, leaving the existing machinery for services.loadbalanced active.

When set to a string the existing machinery for services.loadbalanced is disabled, even (especially) if services.loadbalanced is set to true.

The chart derived from the role manifest is expected to activate all the kubernetes objects related to ingress, like the ingress specification and related TLS certificate definitions.

Note that none of these will be generated by fissile. It is expected that the developer adds suitable definitions to the objects and templates generated by fissile.

API to operators

An operator wishing to use ingress for a chart supporting it has to set services.ingress to the name of the ingress controller to take responsibility for the ingress specification of the chart (Example: nginx-ingress for the NginX Ingress Controller).

Note that depending on the nature of the specifications in the chart the operator may have to perform additional commands to set up required TLS certificates and the like. It is the responsibility of the chart developer to provide the necessary additional instructions.