Chapter 7. Deploying Confidential Containers on IBM Z and IBM LinuxONE

You can deploy Confidential Containers on IBM Z® and IBM® LinuxONE after you deploy OpenShift sandboxed containers.

Important

Confidential Containers on IBM Z® and IBM® LinuxONE is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

Cluster requirements

You have installed Red Hat OpenShift Container Platform 4.15 or later on the cluster where you are installing the Confidential compute attestation Operator.

You deploy Confidential Containers by performing the following steps:

Install the Confidential compute attestation Operator.
Create the route for Trustee.
Enable the Confidential Containers feature gate.
Update the peer pods config map.
Delete the KataConfig custom resource (CR).
Update the peer pods secret.
Re-create the KataConfig CR.
Create the Trustee authentication secret.
Create the Trustee config map.
Obtain the IBM Secure Execution (SE) header.
Configure the SE certificates and keys.
Configure Trustee values, policies, and secrets.
Create the KbsConfig CR.
Verify the Trustee configuration.
Verify the attestation process.

7.1. Installing the Confidential compute attestation Operator

You can install the Confidential compute attestation Operator on IBM Z® and IBM® LinuxONE by using the CLI.

Prerequisites

You have installed the OpenShift CLI (oc).
You have access to the cluster as a user with the cluster-admin role.

Procedure

Create a trustee-namespace.yaml manifest file:

apiVersion: v1
kind: Namespace
metadata:
  name: trustee-operator-system

Create the trustee-operator-system namespace by running the following command:
```
$ oc apply -f trustee-namespace.yaml
```

Create a trustee-operatorgroup.yaml manifest file:

apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: trustee-operator-group
  namespace: trustee-operator-system
spec:
  targetNamespaces:
  - trustee-operator-system

Create the operator group by running the following command:
```
$ oc apply -f trustee-operatorgroup.yaml
```

Create a trustee-subscription.yaml manifest file:

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: trustee-operator
  namespace: trustee-operator-system
spec:
  channel: stable
  installPlanApproval: Automatic
  name: trustee-operator
  source: redhat-operators
  sourceNamespace: openshift-marketplace
  startingCSV: trustee-operator.v0.1.0

Create the subscription by running the following command:
```
$ oc apply -f trustee-subscription.yaml
```
Verify that the Operator is correctly installed by running the following command:
```
$ oc get csv -n trustee-operator-system
```
This command can take several minutes to complete.

Watch the process by running the following command:

$ watch oc get csv -n trustee-operator-system

Example output

NAME                      DISPLAY                        PHASE
trustee-operator.v0.1.0   Trustee Operator  0.1.0        Succeeded

7.2. Enabling the Confidential Containers feature gate

You must enable the Confidential Containers feature gate.

Prerequisites

You have subscribed to the OpenShift sandboxed containers Operator.

Procedure

Create a cc-feature-gate.yaml manifest file:

apiVersion: v1
kind: ConfigMap
metadata:
  name: osc-feature-gates
  namespace: openshift-sandboxed-containers-operator
data:
  confidential: "true"

Create the config map by running the following command:
```
$ oc apply -f cc-feature-gate.yaml
```

7.3. Creating the route for Trustee

You can create a secure route with edge TLS termination for Trustee. External ingress traffic reaches the router pods as HTTPS and passes on to the Trustee pods as HTTP.

Prerequisites

You have installed the Confidential compute attestation Operator.

Procedure

Create an edge route by running the following command:
```
$ oc create route edge --service=kbs-service --port kbs-port \
  -n trustee-operator-system
```
Note
Note: Currently, only a route with a valid CA-signed certificate is supported. You cannot use a route with self-signed certificate.

Set the TRUSTEE_HOST variable by running the following command:

$ TRUSTEE_HOST=$(oc get route -n trustee-operator-system kbs-service \
  -o jsonpath={.spec.host})

Verify the route by running the following command:

$ echo $TRUSTEE_HOST

Example output

kbs-service-trustee-operator-system.apps.memvjias.eastus.aroapp.io

7.4. Updating the peer pods config map

You must update the peer pods config map for Confidential Containers.

Note

Set Secure Boot to true to enable it by default. The default value is false, which presents a security risk.

Procedure

Create a peer-pods-cm.yaml manifest file according to the following example:

apiVersion: v1
kind: ConfigMap
metadata:
  name: peer-pods-cm
  namespace: openshift-sandboxed-containers-operator
data:
  CLOUD_PROVIDER: "libvirt"
  DISABLECVM: "false"
  AA_KBC_PARAMS: "cc_kbc::https://${TRUSTEE_HOST}" 1

1: Specify the host name of the Trustee route.

Create the config map by running the following command:
```
$ oc apply -f peer-pods-cm.yaml
```

Restart the peerpodconfig-ctrl-caa-daemon daemon set by running the following command:

$ oc set env ds/peerpodconfig-ctrl-caa-daemon \
  -n openshift-sandboxed-containers-operator REBOOT="$(date)"

7.5. Deleting the KataConfig custom resource

You can delete the KataConfig custom resource (CR) by using the command line.

Prerequisites

You have installed the OpenShift CLI (oc).
You have access to the cluster as a user with the cluster-admin role.

Procedure

Delete the KataConfig CR by running the following command:
```
$ oc delete kataconfig example-kataconfig
```
Verify that the custom resource was deleted by running the following command:
```
$ oc get kataconfig example-kataconfig
```
Example output
```
No example-kataconfig instances exist
```

7.6. Updating the peer pods secret

You must update the peer pods secret for Confidential Containers.

The secret stores credentials for creating the pod virtual machine (VM) image and peer pod instances.

By default, the OpenShift sandboxed containers Operator creates the secret based on the credentials used to create the cluster. However, you can manually create a secret that uses different credentials.

Prerequisites

REDHAT_OFFLINE_TOKEN. You have generated this token to download the RHEL image at Red Hat API Tokens.
HKD_CRT. The Host Key Document (HKD) certificate enables secure execution on IBM Z®. For more information, see Obtaining a host key document from Resource Link in the IBM documentation.

Procedure

Create a peer-pods-secret.yaml manifest file according to the following example:
```
apiVersion: v1
kind: Secret
metadata:
  name: peer-pods-secret
  namespace: openshift-sandboxed-containers-operator
type: Opaque
stringData:
  REDHAT_OFFLINE_TOKEN: "<rh_offline_token>" 1
  HKD_CRT: "<hkd_crt_value>" 2
```
1
Specify the Red Hat offline token, which is required for the Operator-built image.
2
Specify the HKD certificate value to enable IBM Secure Execution for the Operator-built image.
Create the secret by running the following command:
```
$ oc apply -f peer-pods-secret.yaml
```

7.7. Re-creating the KataConfig custom resource

You must re-create the KataConfig custom resource (CR) for Confidential Containers.

Important

Creating the KataConfig CR automatically reboots the worker nodes. The reboot can take from 10 to more than 60 minutes. Factors that impede reboot time are as follows:

A larger OpenShift Container Platform deployment with a greater number of worker nodes.
Activation of the BIOS and Diagnostics utility.
Deployment on a hard disk drive rather than an SSD.
Deployment on physical nodes such as bare metal, rather than on virtual nodes.
A slow CPU and network.

Prerequisites

You have access to the cluster as a user with the cluster-admin role.

Procedure

Create an example-kataconfig.yaml manifest file according to the following example:

apiVersion: kataconfiguration.openshift.io/v1
kind: KataConfig
metadata:
  name: example-kataconfig
spec:
  enablePeerPods: true
  logLevel: info
#  kataConfigPoolSelector:
#    matchLabels:
#      <label_key>: '<label_value>' 1

1: Optional: If you have applied node labels to install kata-remote on specific nodes, specify the key and value, for example, cc: 'true'.

Create the KataConfig CR by running the following command:
```
$ oc apply -f example-kataconfig.yaml
```
The new KataConfig CR is created and installs kata-remote as a runtime class on the worker nodes.
Wait for the kata-remote installation to complete and the worker nodes to reboot before verifying the installation.
Monitor the installation progress by running the following command:
```
$ watch "oc describe kataconfig | sed -n /^Status:/,/^Events/p"
```
When the status of all workers under kataNodes is installed and the condition InProgress is False without specifying a reason, the kata-remote is installed on the cluster.
Verify that you have built the peer pod image and uploaded it to the libvirt volume by running the following command:
```
$ oc describe configmap peer-pods-cm -n openshift-sandboxed-containers-operator
```
Example output
```
Name: peer-pods-cm
Namespace: openshift-sandboxed-containers-operator
Labels: <none>
Annotations: <none>

Data
====
CLOUD_PROVIDER: libvirt
DISABLECVM: false 1
LIBVIRT_IMAGE_ID: fa-pp-vol 2

BinaryData
====
Events: <none>
```
1
Enables the Confidential VM during IBM Secure Execution for the Operator-built image.
2
Contains a value if you have built the peer pod image and uploaded it to the libvirt volume.
Monitor the kata-oc machine config pool progress to ensure that it is in the UPDATED state, when UPDATEDMACHINECOUNT equals MACHINECOUNT, by running the following command:
```
$ watch oc get mcp/kata-oc
```

Verify the daemon set by running the following command:

$ oc get -n openshift-sandboxed-containers-operator ds/peerpodconfig-ctrl-caa-daemon

Verify the runtime classes by running the following command:

$ oc get runtimeclass

Example output

NAME             HANDLER          AGE
kata             kata             152m
kata-remote      kata-remote      152m

7.8. Creating the Trustee authentication secret

You must create the authentication secret for Trustee.

Prerequisites

You have installed the OpenShift CLI (oc).
You have access to the cluster as a user with the cluster-admin role.

Procedure

Create a private key by running the following command:
```
$ openssl genpkey -algorithm ed25519 > privateKey
```
Create a public key by running the following command:
```
$ openssl pkey -in privateKey -pubout -out publicKey
```

Create a secret by running the following command:

$ oc create secret generic kbs-auth-public-key --from-file=publicKey -n trustee-operator-system

Verify the secret by running the following command:
```
$ oc get secret -n trustee-operator-system
```

7.9. Creating the Trustee config map

You must create the config map to configure the Trustee server.

Note

The following configuration example turns off security features to enable demonstration of Technology Preview features. It is not meant for a production environment.

Prerequisites

You have created a route for Trustee.

Procedure

Create a kbs-config-cm.yaml manifest file:

apiVersion: v1
kind: ConfigMap
metadata:
  name: kbs-config-cm
  namespace: trustee-operator-system
data:
  kbs-config.json: |
    {
      "insecure_http" : true,
      "sockets": ["0.0.0.0:8080"],
      "auth_public_key": "/etc/auth-secret/publicKey",
      "attestation_token_config": {
        "attestation_token_type": "CoCo"
      },
      "repository_config": {
        "type": "LocalFs",
        "dir_path": "/opt/confidential-containers/kbs/repository"
      },
      "as_config": {
        "work_dir": "/opt/confidential-containers/attestation-service",
        "policy_engine": "opa",
        "attestation_token_broker": "Simple",
          "attestation_token_config": {
          "duration_min": 5
          },
        "rvps_config": {
          "store_type": "LocalJson",
          "store_config": {
            "file_path": "/opt/confidential-containers/rvps/reference-values/reference-values.json"
          }
         }
      },
      "policy_engine_config": {
        "policy_path": "/opt/confidential-containers/opa/policy.rego"
      }
    }

Create the config map by running the following command:
```
$ oc apply -f kbs-config-cm.yaml
```

7.10. Configuring the IBM Secure Execution certificates and keys

You must configure the IBM Secure Execution (SE) certificates and keys for your worker nodes.

Prerequisites

You have the IP address of the bastion node.
You have the internal IP addresses of the worker nodes.

Procedure

Obtain the attestation policy fields by performing the following steps:

Create a directory to download the GetRvps.sh script by running the following command:
```
$ mkdir -p Rvps-Extraction/
```

Download the script by running the following command:

$ wget https://github.com/openshift/sandboxed-containers-operator/raw/devel/hack/Rvps-Extraction/GetRvps.sh -O $PWD/GetRvps.sh

Create a subdirectory by running the following command:
```
$ mkdir -p Rvps-Extraction/static-files
```
Go to the static-files directory by running the following command:
```
$ cd Rvps-Extraction/static-files
```

Download the pvextract-hdr tool by running the following command:

$ wget https://github.com/openshift/sandboxed-containers-operator/raw/devel/hack/Rvps-Extraction/static-files/pvextract-hdr -O $PWD/pvextract-hdr

Make the tool executable by running the following command:
```
$ chmod +x pvextract-hdr
```

Download the se_parse_hdr.py script by running the following command:

$ wget https://github.com/openshift/sandboxed-containers-operator/raw/devel/hack/Rvps-Extraction/static-files/se_parse_hdr.py -O $PWD/se_parse_hdr.py

Copy your Host Key Document (HKD) certificate to the static-files directory by running the following command:
```
$ cp ~/path/to/<hkd_cert.crt> .
```
The static-files directory contains the following files:
- HKD.crt
- pvextract-hdr
- se_parse_hdr.py
Go to the Rvps-Extraction directory by running the following command:
```
$ cd ..
```

List your Network Block Devices (NBDs) by running the following command:

$ lsblk

Example output

nbd0                                           43:0    0  100G  0 disk
├─nbd0p1                                       43:1    0  255M  0 part
├─nbd0p2                                       43:2    0    6G  0 part
│ └─luks-e23e15fa-9c2a-45a5-9275-aae9d8e709c3 253:2    0    6G  0 crypt
└─nbd0p3                                       43:3    0 12.4G  0 part
nbd1                                           43:32   0   20G  0 disk
├─nbd1p1                                       43:33   0  255M  0 part
├─nbd1p2                                       43:34   0    6G  0 part
│ └─luks-5a540f7c-c0cb-419b-95e0-487670d91525 253:3    0    6G  0 crypt
└─nbd1p3                                       43:35   0 86.9G  0 part
nbd2                                           43:64   0    0B  0 disk
nbd3                                           43:96   0    0B  0 disk
nbd4                                           43:128  0    0B  0 disk
nbd5                                           43:160  0    0B  0 disk
nbd6                                           43:192  0    0B  0 disk
nbd7                                           43:224  0    0B  0 disk
nbd8                                           43:256  0    0B  0 disk
nbd9                                           43:288  0    0B  0 disk
nbd10                                          43:320  0    0B  0 disk

Note

You can use NBDs from nbd0 to nbd15 to run the script. The default is nbd3. Replace the NBD value in the GetRvps.sh script with the one you are using to run the script.

Make the GetRvps.sh script executable by running the following command:
```
$ chmod +x GetRvps.sh
```

Run the script:

$ ./GetRvps.sh

Example output

***Installing necessary packages for RVPS values extraction ***
Updating Subscription Management repositories.
Last metadata expiration check: 0:37:12 ago on Mon Nov 18 09:20:29 2024.
Package python3-3.9.19-8.el9_5.1.s390x is already installed.
Package python3-cryptography-36.0.1-4.el9.s390x is already installed.
Package kmod-28-10.el9.s390x is already installed.
Dependencies resolved.
Nothing to do.
Complete!
***Installation Finished ***
1) Generate the RVPS From Local Image from User pc
2) Generate RVPS from Volume
3) Quit
Please enter your choice:

Enter 2 to generate the Reference Value Provider Service from the volume:
```
Please enter your choice: 2
```
Enter fa-pp for the libvirt pool name:
```
Enter the Libvirt Pool Name: fa-pp
```
Enter the libvirt gateway URI:
```
Enter the Libvirt URI Name: <libvirt-uri> 1
```
1
Specify the LIBVIRT_URI value that you used to create the peer pods secret.

Enter fa-pp-vol for the libvirt volume name:

Enter the Libvirt Volume Name: fa-pp-vol

Example output

Downloading from PODVM Volume...

mount: /mnt/myvm: special device /dev/nbd3p1 does not exist.
Error: Failed to mount the image. Retrying...
Mounting on second attempt passed
/dev/nbd3 disconnected
SE header found at offset 0x014000
SE header written to '/roothuddleyes/sandboxed-containers-operator/hack/Rvps-Extraction/output-files/hdr.bin' (640 bytes)
se.tag: 8ed6bc93307de4a5988a8ce0b80af390
se.image_phkh:  92d0aff6eb86720b6b1ea0cb98d2c99ff2ab693df3efff2158f54112f6961111
provenance = ewogICAgInNlLmF0dGVzdGF0aW9uX3Boa2giOiBbCiAgICAgICAgIjkyZDBhZmY2ZWI4NjcxOWI2YjFlYTBjYjk4ZDJjOTlmZjJlYzY5M2RmM2VmZmYyMTU4ZjU0MTEyZjY5NjE1MDgiCiAgICBdLAogICAgInNlLnRhZyI6IFsKICAgICAgICAiOGVkNmFkOTMzMDdkZTRhNTk4OGE4Y2UwYjgwZmIzOTUiCiAgICBdLAogICAgInNlLmltYWdlX3Boa2giOiBbCiAgICAgICAgIjkyZDBhZmY2ZWI4NjcxOWI2YjFlYTBjYjk4ZDJjOTlmZjJlYzY5M2RmM2VmZmYyMTU4ZjU0MTEyZjY5NjE1MDgiCiAgICBdLAogICAgInNlLnVzZXJfZGF0YSI6IFsKICAgICAgICAiMDAiCiAgICBdLAogICAgInNlLnZlcnNpb24iOiBbCiAgICAgICAgIjI1NiIKICAgIF0KfQo=
-rw-r--r--. 1 root root 640 Nov 18 10:01 /root/sandboxed-containers-operator/hack/Rvps-Extraction/output-files/hdr.bin
-rw-r--r--. 1 root root 446 Nov 18 10:01 /root/sandboxed-containers-operator/hack/Rvps-Extraction/output-files/ibmse-policy.rego
-rw-r--r--. 1 root root 561 Nov 18 10:01 /root/sandboxed-containers-operator/hack/Rvps-Extraction/output-files/se-message

Obtain the certificates and certificate revocation lists (CRLs) by performing the following steps:

Create a temporary directory for certificates by running the following command:
```
$ mkdir /tmp/ibmse/certs
```

Download the ibm-z-host-key-signing-gen2.crt certificate by running the following command:

$ wget https://www.ibm.com/support/resourcelink/api/content/public/ibm-z-host-key-signing-gen2.crt -O /tmp/ibmse/certs/ibm-z-host-key-signing-gen2.crt

Download the DigiCertCA.crt certificate by running the following command:

$ wget https://www.ibm.com/support/resourcelink/api/content/public/DigiCertCA.crt -O /tmp/ibmse/certs/DigiCertCA.crt

Create a temporary directory for the CRLs by running the following command:
```
$ mkdir /tmp/ibmse/crls
```

Download the ibm-z-host-key-gen2.crl file by running the following command:

$ wget https://www.ibm.com/support/resourcelink/api/content/public/ibm-z-host-key-gen2.crl -O /tmp/ibmse/crls/ibm-z-host-key-gen2.crl

Download the DigiCertTrustedRootG4.crl file by running the following command:

$ wget http://crl3.digicert.com/DigiCertTrustedRootG4.crl -O /tmp/ibmse/crls/DigiCertTrustedRootG4.crl

Download the DigiCertTrustedG4CodeSigningRSA4096SHA3842021CA1.crl file by running the following command:

$ wget http://crl3.digicert.com/DigiCertTrustedG4CodeSigningRSA4096SHA3842021CA1.crl -O /tmp/ibmse/crls/DigiCertTrustedG4CodeSigningRSA4096SHA3842021CA1.crl

Generate the RSA keys:

Generate an RSA key pair by running the following command:
```
$ openssl genrsa -aes256 -passout pass:<password> -out /tmp/encrypt_key-psw.pem 4096 1
```
1
Specify the RSA key password.
Create a temporary directory for the RSA keys by running the following command:
```
$ mkdir /tmp/ibmse/rsa
```

Create an encrypt_key.pub key by running the following command:

$ openssl rsa -in /tmp/encrypt_key-psw.pem -passin pass:<password> -pubout -out /tmp/ibmse/rsa/encrypt_key.pub

Create an encrypt_key.pem key by running the following command:

$ openssl rsa -in /tmp/encrypt_key-psw.pem -passin pass:<password> -out /tmp/ibmse/rsa/encrypt_key.pem

Verify the structure of the /tmp/ibmse directory by running the following command:

$ tree /tmp/ibmse

Example output

/tmp/ibmse
├── certs
│   ├── ibm-z-host-key-signing-gen2.crt
|   └── DigiCertCA.crt
├── crls
│   └── ibm-z-host-key-gen2.crl
│   └── DigiCertTrustedRootG4.crl
│   └── DigiCertTrustedG4CodeSigningRSA4096SHA3842021CA1.crl
├── hdr
│   └── hdr.bin
├── hkds
│   └── <hkd_cert.crt>
└── rsa
    ├── encrypt_key.pem
    └── encrypt_key.pub

Copy these files to the OpenShift Container Platform worker nodes by performing the following steps:
1. Create a compressed file from the /tmp/ibmse directory by running the following command:
```
$ tar -czf ibmse.tar.gz -C /tmp/ ibmse
```
2. Copy the .tar.gz file to the bastion node in your cluster by running the following command:
```
$ scp /tmp/ibmse.tar.gz root@<ocp_bastion_ip>:/tmp 1
```
  1
  Specify the IP address of the bastion node.
3. Connect to the bastion node over SSH by running the following command:
```
$ ssh root@<ocp_bastion_ip>
```
4. Copy the .tar.gz file to each worker node by running the following command:
```
$ scp /tmp/ibmse.tar.gz core@<worker_node_ip>:/tmp 1
```
  1
  Specify the IP address of the worker node.
5. Extract the .tar.gz on each worker node by running the following command:
```
$ ssh core@<worker_node_ip> 'sudo mkdir -p /opt/confidential-containers/ && sudo tar -xzf /tmp/ibmse.tar.gz -C /opt/confidential-containers/'
```
6. Update the ibmse folder permissions by running the following command:
```
$ ssh core@<worker_node_ip> 'sudo chmod -R 755 /opt/confidential-containers/ibmse/'
```

7.11. Configuring Trustee values, policies, and secrets

You can configure the following values, policies, and secrets for Trustee:

Optional: Reference values for the Reference Value Provider Service.
Attestation policy for IBM Secure Execution.
Optional: Secret for custom keys for Trustee clients.
Optional: Secret for container image signature verification.
Container image signature verification policy. This policy is mandatory. If you do not use container image signature verification, you must create a policy that does not verify signatures.
Resource access policy.

7.11.1. Configuring reference values

You can configure reference values for the Reference Value Provider Service (RVPS) by specifying the trusted digests of your hardware platform.

The client collects measurements from the running software, the Trusted Execution Environment (TEE) hardware and firmware and it submits a quote with the claims to the Attestation Server. These measurements must match the trusted digests registered to the Trustee. This process ensures that the confidential VM (CVM) is running the expected software stack and has not been tampered with.

Procedure

Create an rvps-configmap.yaml manifest file:

apiVersion: v1
kind: ConfigMap
metadata:
  name: rvps-reference-values
  namespace: trustee-operator-system
data:
  reference-values.json: |
    [ 1
    ]

1: Leave this value empty.

Create the RVPS config map by running the following command:
```
$ oc apply -f rvps-configmap.yaml
```

7.11.2. Creating the attestation policy for IBM Secure Execution

You must create the attestation policy for IBM Secure Execution.

Procedure

Create an attestation-policy.yaml manifest file:

apiVersion: v1
kind: ConfigMap
metadata:
  name: attestation-policy
  namespace: trustee-operator-system
data:
  default.rego: | 1
    package policy
    import rego.v1
    default allow = false
    converted_version := sprintf("%v", [input["se.version"]])
    allow if {
        input["se.attestation_phkh"] == "<se.attestation_phkh>" 2
        input["se.image_phkh"] == "<se.image_phkh>"
        input["se.tag"] == "<se.tag>"
        converted_version == "256"
    }

1: Do not modify the policy name.
2: Specify the attestation policy fields you obtained by running the se_parse_hdr.py script.

Create the attestation policy config map by running the following command:
```
$ oc apply -f attestation-policy.yaml
```

7.11.3. Creating a secret with custom keys for clients

You can create a secret that contains one or more custom keys for Trustee clients.

In this example, the kbsres1 secret has two entries (key1, key2), which the clients retrieve. You can add additional secrets according to your requirements by using the same format.

Prerequisites

You have created one or more custom keys.

Procedure

Create a secret for the custom keys according to the following example:
```
$ oc apply secret generic kbsres1 \
  --from-literal key1=<custom_key1> \ 1
  --from-literal key2=<custom_key2> \
  -n trustee-operator-system
```
1
Specify a custom key.
The kbsres1 secret is specified in the spec.kbsSecretResources key of the KbsConfig custom resource.

7.11.4. Creating a secret for container image signature verification

If you use container image signature verification, you must create a secret that contains the public container image signing key.

The Confidential compute attestation Operator uses the secret to verify the signature, ensuring that only trusted and authenticated container images are deployed in your environment.

You can use Red Hat Trusted Artifact Signer or other tools to sign container images.

Procedure

Create a secret for container image signature verification by running the following command:
```
$ oc apply secret generic <type> \ 1
  --from-file=<tag>=./<public_key_file> \ 2
  -n trustee-operator-system
```
1
Specify the KBS secret type, for example, img-sig.
2
Specify the secret tag, for example, pub-key, and the public container image signing key.
Record the <type> value. You must add this value to the spec.kbsSecretResources key when you create the KbsConfig custom resource.

7.11.5. Creating the container image signature verification policy

You create the container image signature verification policy because signature verification is always enabled. If this policy is missing, the pods will not start.

If you are not using container image signature verification, you create the policy without signature verification.

For more information, see containers-policy.json 5.

Procedure

Create a security-policy-config.json file according to the following examples:

Without signature verification:

{
  "default": [
  {
    "type": "insecureAcceptAnything"
  }],
  "transports": {}
}

With signature verification:

{
  "default": [
      {
      "type": "insecureAcceptAnything"
      }
  ],
  "transports": {
      "<transport>": { 1
          "<registry>/<image>": 2
          [
              {
                  "type": "sigstoreSigned",
                  "keyPath": "kbs:///default/<type>/<tag>" 3
              }
          ]
      }
  }
}

1: Specify the image repository for transport, for example, "docker":. For more information, see containers-transports 5.
2: Specify the container registry and image, for example, "quay.io/my-image".
3: Specify the type and tag of the container image signature verification secret that you created, for example, img-sig/pub-key.

Create the security policy by running the following command:
```
$ oc apply secret generic security-policy \
  --from-file=osc=./<security-policy-config.json> \
  -n trustee-operator-system
```
Do not alter the secret type, security-policy, or the key, osc.
The security-policy secret is specified in the spec.kbsSecretResources key of the KbsConfig custom resource.

7.11.6. Creating the resource access policy

You configure the resource access policy for the Trustee policy engine. This policy determines which resources Trustee can access.

Note

The Trustee policy engine is different from the Attestation Service policy engine, which determines the validity of TEE evidence.

Procedure

Create a resourcepolicy-configmap.yaml manifest file:
```
apiVersion: v1
kind: ConfigMap
metadata:
  name: resource-policy
  namespace: trustee-operator-system
data:
  policy.rego: | 1
    package policy 2
    path := split(data["resource-path"], "/")
    default allow = false
    allow {
      count(path) == 3
      input["tee"] == "se"
    }
```
1
The name of the resource policy, policy.rego, must match the resource policy defined in the Trustee config map.
2
The resource policy follows the Open Policy Agent specification. This example allows the retrieval of all resources when the TEE is not the sample attester.
Create the resource policy config map by running the following command:
```
$ oc apply -f resourcepolicy-configmap.yaml
```

7.12. Creating the KbsConfig custom resource

You create the KbsConfig custom resource (CR) to launch Trustee.

Then, you check the Trustee pods and pod logs to verify the configuration.

Procedure

Create a kbsconfig-cr.yaml manifest file:

apiVersion: confidentialcontainers.org/v1alpha1
kind: KbsConfig
metadata:
  labels:
    app.kubernetes.io/name: kbsconfig
    app.kubernetes.io/instance: kbsconfig
    app.kubernetes.io/part-of: trustee-operator
    app.kubernetes.io/managed-by: kustomize
    app.kubernetes.io/created-by: trustee-operator
  name: kbsconfig
  namespace: trustee-operator-system
spec:
  kbsConfigMapName: kbs-config-cm
  kbsAuthSecretName: kbs-auth-public-key
  kbsDeploymentType: AllInOneDeployment
  kbsRvpsRefValuesConfigMapName: rvps-reference-values
  kbsSecretResources: ["kbsres1", "security-policy", "<type>"] 1
  kbsResourcePolicyConfigMapName: resource-policy
  kbsAttestationPolicyConfigMapName: attestation-policy
  kbsServiceType: NodePort
  ibmSEConfigSpec:
    certStorePvc: ibmse-pvc

1: Optional: Specify the type value of the container image signature verification secret if you created the secret, for example, img-sig. If you did not create the secret, set the kbsSecretResources value to ["kbsres1", "security-policy"].

Create the KbsConfig CR by running the following command:
```
$ oc apply -f kbsconfig-cr.yaml
```

7.13. Verifying the Trustee configuration

You verify the Trustee configuration by checking the Trustee pods and logs.

Procedure

Set the default project by running the following command:
```
$ oc project trustee-operator-system
```

Check the Trustee pods by running the following command:

$ oc get pods -n trustee-operator-system

Example output

NAME                                                   READY   STATUS    RESTARTS   AGE
trustee-deployment-8585f98449-9bbgl                    1/1     Running   0          22m
trustee-operator-controller-manager-5fbd44cd97-55dlh   2/2     Running   0          59m

Set the POD_NAME environmental variable by running the following command:

$ POD_NAME=$(oc get pods -l app=kbs -o jsonpath='{.items[0].metadata.name}' -n trustee-operator-system)

Check the pod logs by running the following command:

$ oc logs -n trustee-operator-system $POD_NAME

Example output

[2024-05-30T13:44:24Z INFO  kbs] Using config file /etc/kbs-config/kbs-config.json
[2024-05-30T13:44:24Z WARN  attestation_service::rvps] No RVPS address provided and will launch a built-in rvps
[2024-05-30T13:44:24Z INFO  attestation_service::token::simple] No Token Signer key in config file, create an ephemeral key and without CA pubkey cert
[2024-05-30T13:44:24Z INFO  api_server] Starting HTTPS server at [0.0.0.0:8080]
[2024-05-30T13:44:24Z INFO  actix_server::builder] starting 12 workers
[2024-05-30T13:44:24Z INFO  actix_server::server] Tokio runtime found; starting in existing Tokio runtime

Expose the ibmse-pvc persistent volume claim to the Trustee pods by running the following command:

$ oc patch deployment trustee-deployment \
  --namespace=trustee-operator-system --type=json \
  -p='[{"op": "remove", "path": "/spec/template/spec/volumes/5/persistentVolumeClaim/readOnly"}]'

Verify that the kbs-service is exposed on a node port by running the following command:

$ oc get svc kbs-service -n trustee-operator-system

Example output

NAME          TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
kbs-service   NodePort   198.51.100.54   <none>        8080:31862/TCP   23h

The kbs-service URL is https://<worker_node_ip>:<node_port>, for example, https://172.16.0.56:31862.

7.14. Verifying the attestation process

You can verify the attestation process by creating a BusyBox pod. The pod image deploys the confidential workload where you can retrieve the key.

Important

This procedure is an example to verify that attestation is working. Do not write sensitive data to standard I/O because the data can be captured by using a memory dump. Only data written to memory is encrypted.

Procedure

Create a busybox.yaml manifest file:

apiVersion: v1
kind: Pod
metadata:
  name: busybox
  namespace: default
spec:
  runtimeClassName: kata-remote
  containers:
  - name: busybox
    image: quay.io/prometheus/busybox:latest
    imagePullPolicy: Always
    command:
      - "sleep"
      - "3600"

Create the pod by running the following command:
```
$ oc create -f busybox.yaml
```
Log in to the pod by running the following command:
```
$ oc exec -it busybox -n default -- /bin/sh
```

Get the secret key by running the following command:

$ wget http://127.0.0.1:8006/cdh/resource/default/kbsres1/key1

Example output

Connecting to 127.0.0.1:8006 (127.0.0.1:8006)
saving to 'key1'
key1                 100% |*******************************************|     8  0:00:00 ETA
'key1' saved

Display the key1 value by running the following command:
```
$ cat key1
```
Example output
```
res1val1/ #
```

Chapter 7. Deploying Confidential Containers on IBM Z and IBM LinuxONE

7.1. Installing the Confidential compute attestation Operator

7.2. Enabling the Confidential Containers feature gate

7.3. Creating the route for Trustee

7.4. Updating the peer pods config map

7.5. Deleting the KataConfig custom resource

7.6. Updating the peer pods secret

7.7. Re-creating the KataConfig custom resource

7.8. Creating the Trustee authentication secret

7.9. Creating the Trustee config map

7.10. Configuring the IBM Secure Execution certificates and keys

7.11. Configuring Trustee values, policies, and secrets

7.11.1. Configuring reference values

7.11.2. Creating the attestation policy for IBM Secure Execution

7.11.3. Creating a secret with custom keys for clients

7.11.4. Creating a secret for container image signature verification

7.11.5. Creating the container image signature verification policy

7.11.6. Creating the resource access policy

7.12. Creating the KbsConfig custom resource

7.13. Verifying the Trustee configuration

7.14. Verifying the attestation process

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

Making open source more inclusive

About Red Hat

Red Hat legal and privacy links

Red Hat legal and privacy links