Add test for the attestation key lifecycle #193
Conversation
The test ensures that the attestation keys is approved and deleted together with the machine. Signed-off-by: Alice Frosi <afrosi@redhat.com>
|
@alicefr: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: alicefr, Jakob-Naucke The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
github.com (to fetch a resource, not the GHA) timed out for the lint, re-running |
Jakob-Naucke
merged commit 11f0322
into
trusted-execution-clusters:main
2 participants
This try to reproduce the issue described in #168 which is solved by #187. But it is better to have a simple tests which validate the attestation keys lifecycle.
The attestation key, also, in this particular case, is created before the machine. After, when the machine is created, the attestation key is approved and the its owner is set to the machine. Once, the machine is removed, also the attestation key and the corresponding secret are also deleted.