Description

Following the internal docs, osc/trustee was set up

The kbs-client pod was setup and could retrieve the secret

A kata-remote workload (hello-openshift) was created in the trustee namespace.

The pod failed to start because it could not authenticate which I think is expected

23m (x2 over 26m)   Warning   FailedCreatePodSandBox   Pod/hello-openshift-tagged                  Failed to create pod sandbox: rpc error: code = Unknown desc = CreateContainer failed: Failed to Check if grpc server is working: context deadline exceeded: unknown

In the Azure console, a VM named podvm-hello-openshift-tagged had been created.

I then deleted the pod.  The VM was left in a Failed status but was not deleted.

x,jsonfrom Azure

Client Version: 4.17.0-202410161505.p0.g897ef0b.assembly.stream.el9-897ef0b
Server Version: 4.17.3

OSC 1.8.0-3, trustee v0.1.0