test/e2e: Update testcases for HTTPS KBS#2285
test/e2e: Update testcases for HTTPS KBS#2285mkulke merged 1 commit intoconfidential-containers:mainfrom
Conversation
e1f08ea to
7cbad6f
Compare
ec76f50 to
b45c04f
Compare
stevenhorsman
left a comment
There was a problem hiding this comment.
It generally is looking fine. I had a few questions/comments of some of the code choices and we also need to have a commit body explaining the changes in commit message.
|
|
||
| var trusteeRepoPath string | ||
| var certPath string | ||
| var workerNodeIP string |
There was a problem hiding this comment.
What is the reason for this being made a package level variable?
There was a problem hiding this comment.
Hello steve,
certificate path is being used while setting the resource policy and attestation policy.
And worker node Ip is being used by NewHTTPSKbsInstallOverlay to generate certificate and key.
There was a problem hiding this comment.
So can we just use workerNodeIP, _, _ = getFirstWorkerNodeIPAndName(cfg) (or refactor getFirstWorkerNodeIPAndName to have a verison that just returns the ip) when we need it rather than making it package level and then having to do if workerNodeIP != "" {?
5089cc4 to
c3eaf07
Compare
34c8377 to
13ec5b7
Compare
- Switch the KBS tests, using initdata to use https rather than http, as we want to ensure this flow works in order to avoid exposure of secrets - Update `checkout_kbs.sh` to configure certificates in the kbs deployment Signed-off-by: Adapa Chathurya <[email protected]>
a2fd332 to
228ea92
Compare
stevenhorsman
left a comment
There was a problem hiding this comment.
The code looks reasonable and the tests all pass. Thanks @chathuryaadapa!
Support certificates in KBS and aa/cdh
fixes: #2300