-
Notifications
You must be signed in to change notification settings - Fork 214
e2e: refactor TLS helpers #327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
stlaz
commented
Nov 26, 2024
- simplification of the current certgen code
- better separation of leaf and CA certs in kube CMs/Secrets
_, err = client.CoreV1().Secrets(ctx.Namespace).Create(context.TODO(), &corev1.Secret{ | ||
ObjectMeta: metav1.ObjectMeta{ | ||
Name: secretName, | ||
}, | ||
Data: map[string][]byte{ | ||
"tls.crt": pem.EncodeToMemory(&pem.Block{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
...thought maybe there was an issue since the tests failed, but ran them on my system and they were fine.
The test failed on KRP logging |
Looks like the same test failed again, that shouldn't happen. I'll have a look. |
Still not able to reproduce locally. Raising nginx loglevel to debug in CI. |
Unify cert template generation. SKID and AKID should be properly computed by Golang, no need to add them explicitly - unless we need explicit SKID but that's not the case in our tests.
The previous design was mixing CA and leaf certificates, making it easy to confuse them at place of use. Have all the leaf cryptomaterial in a secret, and the trust in the CM to avoid those issues.
afd6e94
to
daccc4d
Compare
2959053
to
48dfc38
Compare
Looks like the test was missing assumptions on when it's safe to be run. I'll give it a couple respins to check the timing issue is now gone. |