Chapter 11. Configuring TLS encryption in Eventing

Procedure

1. Create a SelfSigned ClusterIssuer resource as follows:

   apiVersion: cert-manager.io/v1
   kind: ClusterIssuer
   metadata:
     name: knative-eventing-selfsigned-issuer
   spec:
     selfSigned: {}

   Copy to Clipboard Toggle word wrap

2. Apply the ClusterIssuer resource by running the following command:

   $ oc apply -f <filename>

   Copy to Clipboard Toggle word wrap

3. Create a root certificate by using the SelfSigned ClusterIssuer resource as follows:

   apiVersion: cert-manager.io/v1
   kind: Certificate
   metadata:
     name: knative-eventing-selfsigned-ca
     namespace: cert-manager 

   1

   
   spec:
     secretName: knative-eventing-ca 

   2

   
     isCA: true
     commonName: selfsigned-ca
     privateKey:
       algorithm: ECDSA
       size: 256
     issuerRef:
       name: knative-eventing-selfsigned-issuer
       kind: ClusterIssuer
       group: cert-manager.io

   Copy to Clipboard Toggle word wrap

   1

   Specify the cert-manager Operator for Red Hat OpenShift that is used by default.

   2

   Specify the secret where the certificate is stored. The name is later used by the ClusterIssuer for Eventing.

4. Apply the Certificate resource by running the following:

   $ oc apply -f <filename>

   Copy to Clipboard Toggle word wrap

Procedure

1. Create the knative-eventing-ca-issuer ClusterIssuer resource as follows:

   Every Eventing component uses this issuer to issue their server’s certs.

   apiVersion: cert-manager.io/v1
   kind: ClusterIssuer
   metadata:
     name: knative-eventing-ca-issuer
   spec:
     ca:
       secretName: knative-eventing-ca 

   1

   Copy to Clipboard Toggle word wrap

   1

   The secretName value in the cert-manager namespace (default for cert-manager Operator for Red Hat OpenShift) contains the certificate that can be used by Knative Eventing components.

   Note

   The ClusterIssuer name must be knative-eventing-ca-issuer.

2. Apply the ClusterIssuer resource by running the following command:

   $ oc apply -f <filename>

   Copy to Clipboard Toggle word wrap

Procedure

1. Enable the transport-encryption in KnativeEventing as follows:

   apiVersion: operator.knative.dev/v1beta1
   kind: KnativeEventing
   metadata:
     name: knative-eventing
     namespace: knative-eventing
   spec:
   
     # Other spec fields omitted ...
     # ...
   
     config:
       features:
         transport-encryption: strict

   Copy to Clipboard Toggle word wrap

2. Apply the KnativeEventing resource by running the following command:

   $ oc apply -f <filename>

   Copy to Clipboard Toggle word wrap

Procedure

1. Export the CA from the knative-eventing-ca secret in the cert-manager Operator for Red Hat OpenShift namespace (default is cert-manager certificate) by running the following command:

   $ oc get secret -n cert-manager knative-eventing-ca -o=jsonpath='{.data.ca\.crt}' | base64 -d > ca.crt

   Copy to Clipboard Toggle word wrap

2. Create a CA trust bundle in the knative-eventing namespace by running the following command:

   $ oc create configmap -n knative-eventing my-org-selfsigned-ca-bundle --from-file=ca.crt

   Copy to Clipboard Toggle word wrap

3. Label the ConfigMap by running the following command:

   $ oc label configmap -n knative-eventing my-org-selfsigned-ca-bundle networking.knative.dev/trust-bundle=true

   Copy to Clipboard Toggle word wrap

Procedure

1. Create a CA certificate.

2. Add the public key of the new CA certificate to the CA trust bundles.

   Ensure that you also keep the public key of the existing CA.

3. Ensure all clients use the latest CA trust bundles.

   Knative Eventing components automatically reload the updated CA trust bundles. For custom workloads that consume trust bundles, reload or restart them as needed.

4. Update the knative-eventing-ca-issuer ClusterIssuer to reference the secret containing the CA certificate that you created in step 1.

5. Force cert-manager to renew certificates in the knative-eventing namespace.

   For more information about cert-manager, see Reissuance triggered by user actions.

6. As soon as the CA rotation is fully completed, remove the public key of the old CA from the trust bundle config map.

Procedure

1. Create an InMemoryChannel resource as follows:

   apiVersion: messaging.knative.dev/v1
   kind: InMemoryChannel
   metadata:
     name: transport-encryption-test

   Copy to Clipboard Toggle word wrap

2. Apply the InMemoryChannel resource by running the following command:

   $ oc apply -f <filename>

   Copy to Clipboard Toggle word wrap

3. View the InMemoryChannel address by running the following command:

   $ oc get inmemorychannels.messaging.knative.dev transport-encryption-test

   Copy to Clipboard Toggle word wrap

   Example output

   NAME                        URL                                                                                           AGE   READY   REASON
   transport-encryption-test   https://imc-dispatcher.knative-eventing.svc.cluster.local/default/transport-encryption-test   17s   True

   Copy to Clipboard Toggle word wrap