entitlement: using the same content for the entitlement.pem and entitlement-key.pem isn't safe about ci-artifacts

[kpouget]

So in mc_pem.yml, we should distinguish BASE64_ENCODED_PEM_FILE and BASE64_ENCODED_PEM_KEY_FILE:

sed -n '/BEGIN RSA PRIVATE KEY/q;p' {ID}.pem > entitlement.pem
sed -n '/BEGIN RSA PRIVATE KEY/,$p' {ID}.pem > entitlement-key.pem

[kpouget]

In addition, in the playbooks, we can validate the structure of the files:

# cat entitlement.pem | grep -- ---
-----BEGIN CERTIFICATE-----
-----END CERTIFICATE-----
-----BEGIN ENTITLEMENT DATA-----
-----END ENTITLEMENT DATA-----
-----BEGIN RSA SIGNATURE-----
-----END RSA SIGNATURE-----

# cat entitlement-key.pem | grep -- ---
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----

[kpouget]

/close

GPU Operator >= v1.9 doesn't require entitlement, making this less relevant

[openshift-ci]

@kpouget: Closing this issue.

In response to this:

/close

GPU Operator >= v1.9 doesn't require entitlement, making this less relevant

Instructions 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/test-infra repository.