CA check improvements for `system-agent` about rancher HOT 7 CLOSED

Blocked on design review currently.

from rancher.

Depends on #45628.

from rancher.

#45973

from rancher.

Tested this with results over in Qase test run /RM/1631. I noted the following failure:

VALIDATION STEPS

1. Setup Rancher v2.9-head with a valid cert.pem and/or key.pem file.
   • Ensured agentTLSMode=system-store in the helm install command.
2. Ran command kubectl get settings agent-tls-mode -o yaml and noted that the value is strict:

$ kubectl get settings agent-tls-mode -o yaml
apiVersion: management.cattle.io/v3
customized: false
default: strict
kind: Setting
metadata:
  creationTimestamp: "2024-07-02T20:30:00Z"
  generation: 1
  name: agent-tls-mode
  resourceVersion: "936"
  uid: ba85e161-b9b9-4450-9265-d01d04ca59f9
source: ""
value: ""

There are two other scenarios that have the same steps as above that have not been tested yet due to this failure. Marking as blocked until this is resolved.

from rancher.

@markusewalker Can you provide more details? The default on 2.9.0 will be strict, but the actual value should be as in the helm command, system-store - your output doesn't provide sufficient detail to determine if that is the case.

from rancher.

@MbolotSuse sure, updated my comment with the information we discussed offline.

from rancher.

Re-ran the test cases outlined in Qase test run /RM/1631. Using v2.9.0-alpha7, I was successfully able to validate this issue. Summary of the scenarios tested provided below:

from rancher.