Ingress and networking

Add an ingress Helm Chart to an application

Find the Helm Chart provided by ReleaseHub for generating an ingress for your application in our GitHub repository.
You can either copy the contents of the ReleaseHub helm-ingress repository into your source control repository or reference the Helm chart using a remote repository chart:
- name: <service>-ingress
add: release-ingress
directory: <path in your repo to values.yaml>
install: release-ingress/release-ingress
values: values.yaml

Configure the ingress Helm Chart values

You need a values.yaml file in your source control repository to use the Helm Chart.
Customize the values.yaml file to reference the service you would like to expose to the Internet. For example, here is a values.yaml file for a service named frontend:
name: frontend
externalPort: 5000
annotations: nginx "true"

Important version information

If you are using a Kubernetes cluster on v1.20 or below, add the following to your chart's definition to pin the version to an older chart:
- name: <service>-ingress
version: 2.1.0

Add a load balancer to a chart

If you are using AWS with EKS, include the following annotations to your service to create a Network Load Balancer (NLB) and assign an external DNS name. This example configures a TLS-enabled LDAPS port (636) and non-TLS LDAP port (389):
apiVersion: v1
kind: Service
name: fid-service
annotations: external # This creates an NLB ip # Do not touch internet-facing # Or, "private" "true" # Recommended <fill in your ACM certificate here> # Optional for using TLS "636" # Optional for using TLS ELBSecurityPolicy-TLS13-1-2-2021-06 # Optional for using TLS <fill in the hostname to use with a values file or similar>
- port: 389
name: ldap
targetPort: 2389
protocol: TCP
- port: 636
name: ldaps
targetPort: 2636
protocol: TCP
type: LoadBalancer
app: <insert the deployment or pod identifier here>