Home/

...

/

Creating Ingress Resources Based on Paths

Creating Ingress Resources Based on Paths

In this lesson, first, we will look into the definition of an Ingress resource and then create it.

Defining an Ingress Resource

We’ll try to make our go-demo-2-api Service available through the port 80. We’ll do that by defining an Ingress resource with the rule to forward all requests with the path starting with /demo to the Service go-demo-2-api.

Looking into the Definition

Let’s take a look at the Ingress’ YAML definition.

Press + to interact
cat ingress/go-demo-2-ingress.yml

The output is as follows.

Press + to interact
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: go-demo-2
  annotations:
    kubernetes.io/ingress.class: "nginx"
    ingress.kubernetes.io/ssl-redirect: "false"
    nginx.ingress.kubernetes.io/ssl-redirect: "false"
spec:
  rules:
  - http:
      paths:
      - path: /demo
        backend:
          serviceName: go-demo-2-api
          servicePort: 8080
  • Line 5: This time, metadata contains a field we haven’t used before. The annotations section allows us to provide additional information to the Ingress Controller. As you’ll see soon, Ingress API specification is concise and limited. That is done on purpose. The specification API defines only the fields that are mandatory for all Ingress Controllers. All the additional info an Ingress Controller needs is specified through annotations. That way, the community behind the Controllers can progress at great speed, while still providing basic general compatibility and standards.

ℹ️ The list of general ...

Access this course and 1400+ top-rated courses and projects.