Tectonic clusters include an Ingress Controller to expose the Tectonic Console and Tectonic Identity services. Ingress controllers watch the Kubernetes API for Ingress resources and update their configuration to expose Kubernetes services. When service traffic is routed through Ingress controllers, services of type LoadBalancer, NodePort, and HostPort are not required. Ingress resources can have rules which match hostnames, match paths, and perform TLS termination.
1.5.5-tectonic.3, the Tectonic Ingress Controller can be used for user applications as well.
Create an Ingress resource for a service
hello, using the
kubernetes.io/ingress.class annotation. Without the annotation, the Tectonic Ingress controller will ignore the Ingress resource.
apiVersion: extensions/v1beta1 kind: Ingress metadata: name: hello annotations: kubernetes.io/ingress.class: "tectonic" spec: rules: - host: hello.example.com http: paths: - path: / backend: serviceName: hello servicePort: 80
View Ingress resources in the Tectonic Console:
Or by using
$ kubectl get ingress NAME HOSTS ADDRESS PORTS AGE hello hello.example.com 172.18.0.22,172.18.0.23 80 1h
Next, test that traffic to
hello.example.com reaches the cluster's Ingress Controllers.
On Tectonic bare metal, add a DNS record on your network which resolves
hello.example.com to any worker node(s), similar to how the Tectonic DNS entry was set up using Tectonic Installer. (To test, add an
For Tectonic AWS, add a DNS CNAME record
hello.example.com to your Tectonic ELB. It ends in
-con and can be found on your AWS dashboard.
Visit the example application
http://hello.example.com. Learn more about Ingress and add TLS termination for HTTPS apps.
Using Tectonic's built-in Ingress Controller works well for everyday HTTP workloads. However, you may run an application that requires more customized logic. For example, complex header manipulation as the routing rules are applied.
There are several different Ingress Controllers available. Nginx and haproxy are the most popular. Ingress controllers are usually deployed as a Deployment/DaemonSet and a corresponding Service. For more information, see the selected Controller's documentation.
When selecting Ingress Controller options, be certain to consider the following flags:
--ingress-class=my-custom-ingressallows for rules to target this ingress controller.
--watch-namespace=examplewill ensure that only a specific namespace is watched for ingress rules. This can prevent others from using your Ingress Controller.
serviceAccountNameparameter equal to a Service Account with the correct RBAC policy. Read more about service accounts.
Here is a full example:
apiVersion: apps/v1beta2 kind: Deployment metadata: name: production-ingress namespace: production labels: k8s-app: ingress spec: replicas: 2 selector: matchLabels: k8s-app: ingress template: metadata: labels: k8s-app: ingress spec: containers: - name: nginx-ingress-lb image: gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.11 args: - /nginx-ingress-controller - --default-backend-service=$(POD_NAMESPACE)/default-http-backend - --configmap=$(POD_NAMESPACE)/production-ingress-conf - --watch-namespace=$(POD_NAMESPACE) - --ingress-class=my-custom-ingress # use downward API env: - name: POD_NAME valueFrom: fieldRef: fieldPath: metadata.name - name: POD_NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace ports: - name: http containerPort: 80 - name: https containerPort: 443 - name: health containerPort: 10254 readinessProbe: httpGet: path: /healthz port: 10254 scheme: HTTP livenessProbe: initialDelaySeconds: 10 timeoutSeconds: 1 httpGet: path: /healthz port: 10254 scheme: HTTP dnsPolicy: ClusterFirst restartPolicy: Always terminationGracePeriodSeconds: 60 serviceAccountName: production-ingress-serviceaccount
To ensure that your rules are satisfied by only your Ingress Controller, specify the Ingress class annotation on your rules:
metadata: name: custom-rules annotations: kubernetes.io/ingress.class: "my-custom-ingress"
When rules are defined and the Ingress Controller is running, traffic to your Service will be routed appropriately.
By default, Ingress limits HTTP headers to 8KB. This limit may cause problems with applications that send very large headers, such as Tectonic Console when users are members of a very large number of groups. To increase the limit, set the
large-client-header-buffers flag to
4 64k on the Ingress Configmap
tectonic-custom-error. This will allocate 4 buffers of 64 kilobytes each to the Ingress HTTP header limit.
For more information, see the nginx documentation on the large-client-header-buffers flag.