Skip to main content

HTTP Ingress

HTTP Ingress Overview

If your application accepts inbound HTTP traffic from the Internet then it will need to leverage the Section HTTP Ingress.

Enabling the HTTP Ingress

To enable the HTTP Ingress controller for a Section environment you must define a Kubernetes service with the specific name of ingress-upstream to initiate deployment of private ingress pods for your environment.

You will need to define the YOUR_APP_NAME variable in order to route traffic to an upstream service defined in your environment's namespace.

http-ingress.yaml
apiVersion: v1
kind: Service
metadata:
labels:
app: ingress-upstream
name: ingress-upstream
namespace: default
spec:
ports:
- name: 80-8080
port: 80
protocol: TCP
targetPort: 80
selector:
app: YOUR_APP_NAME
sessionAffinity: None
type: ClusterIP
status:
loadBalancer: {}

Then visit the Section Console to setup DNS and TLS.

Important Billing Note

Use of Section HTTP Ingress causes a deployment of small, special ingress pods that will be charged to your account like any other application containers. You will not be able to see the containers using kubectl, but will be able to see them on dashboards.