9.8. Using Serving with OpenShift ingress sharding

Procedure

• Use a label selector in the IngressController CR to configure OpenShift Serverless to match specific ingress shards with different domains:

  Example IngressController CR

  apiVersion: operator.openshift.io/v1
  kind: IngressController
  metadata:
    name: ingress-dev 

  1

  
    namespace: openshift-ingress-operator
  spec:
    routeSelector:
      matchLabels:
        router: dev 

  2

  
    domain: "dev.serverless.cluster.example.com" 

  3

  
    # ...
  ---
  apiVersion: operator.openshift.io/v1
  kind: IngressController
  metadata:
    name: ingress-prod 

  4

  
    namespace: openshift-ingress-operator
  spec:
    routeSelector:
      matchLabels:
        router: prod 

  5

  
    domain: "prod.serverless.cluster.example.com" 

  6

  
    # ...

  1

  Name of the first ingress shard.

  2

  A label selector to match the ingress-dev shard.

  3

  A custom domain for the ingress-dev shard.

  4

  Name of the second ingress shard.

  5

  A label selector to match the ingress-prod shard.

  6

  A custom domain for the ingress-prod shard.

Procedure

• In the KnativeServing CR, configure Serving to use the same domains and labels as your ingress shards by adding the spec.config.domain field:

  Example KnativeServing CR

  spec:
    config:
      domain: 

  1

  
        dev.serverless.cluster.example.com: |
          selector:
            router: dev
        prod.serverless.cluster.example.com: |
          selector:
            router: prod
    # ...

  1

  These values need to match the values in the ingress shard configuration.

Procedure

• In your Service CR, add the label selector that matches a specific shard:

  Example Service CR

  apiVersion: serving.knative.dev/v1
  kind: Service
  metadata:
    name: hello-dev
    labels:
      router: dev 

  1

  
  spec:
    template:
      spec:
        containers:
        - image: docker.io/openshift/hello-openshift
  ---
  apiVersion: serving.knative.dev/v1
  kind: Service
  metadata:
    name: hello-prod
    labels:
      router: prod 

  2

  
  spec:
    template:
      spec:
        containers:
        - image: docker.io/openshift/hello-openshift
    # ...

  1 2

  The labels must match the configuration in the KnativeServing CR.