Documentation
  • Getting Started
  • Creating a Product
    • Products Overview
    • Making a Helm Chart
      • Converting from docker-compose
      • Interpolated Values
      • Image Pull Secrets
      • Cluster Ingress
      • SSL Certificates
    • Setting up the Registry
      • Google Container Registry
  • Deploying a Product
    • Deployments Overview
    • Deploying on AWS
    • Deploying on GCP
    • Deploying on Azure (beta)
  • Debugging
    • GCP Permissions Errors
    • Volume Classes
Powered by GitBook
On this page
  1. Creating a Product
  2. Making a Helm Chart

Cluster Ingress

This page describes how to ensure that ingress is working properly for your customer's deployment.

Different cloud providers offer different ingress controllers for their various offerings, and adapting your product to the nuances of the different controllers can be cumbersome. To simplify operation, Metamanagement installs the nginx-ingress controller alongside your deployment.

In order to register your Ingress resource to be handled by nginx, you must add the kubernetes.io/ingress.class: nginx label to the resource’s metadata annotations. You must also add the cert-manager.io/cluster-issuer: letsencrypt-prod label to get SSL certs to generate. See for example:

<...>
kind: Ingress
metadata:
  <...>
  annotations:
    kubernetes.io/ingress.class: nginx
    cert-manager.io/cluster-issuer: letsencrypt-prod

If you created your resources using Kompose, your ingress files should be found in <chart-folder>/templates/*-ingress.yaml.

PreviousImage Pull SecretsNextSSL Certificates

Last updated 3 years ago