-
Notifications
You must be signed in to change notification settings - Fork 216
USHIFT-2455 USHIFT-2456 USHIFT-2457 USHIFT-2458: Introduce adding Custom CA certs for API endpoint #3130
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
USHIFT-2455 USHIFT-2456 USHIFT-2457 USHIFT-2458: Introduce adding Custom CA certs for API endpoint #3130
Conversation
@eslutsky: This pull request references USHIFT-2458 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set. In response to this: 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 openshift-eng/jira-lifecycle-plugin repository. |
Skipping CI for Draft Pull Request. |
f93b3fe
to
0871763
Compare
@eslutsky: This pull request references USHIFT-2101 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.16.0" version, but no target version was set. In response to this: 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 openshift-eng/jira-lifecycle-plugin repository. |
0871763
to
4efac90
Compare
/test all |
1dc3727
to
d3208bc
Compare
/test all |
d3208bc
to
fb4ee76
Compare
/test all |
fb4ee76
to
0aa849a
Compare
/test all |
0aa849a
to
c09851e
Compare
320ece3
to
d20d640
Compare
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.
Just couple, rather minor, comments, but maybe someone more knowledgeable about certs could take a look
}, | ||
} | ||
// prepend the named certs to the beginning of the slice (so it will take precedence for same SNI) | ||
namedCerts = append(cert, namedCerts...) |
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.
Okay, so that works functionally.
Just FYI: This is very inefficient. Go will check capacity of cert
and since it's 1, it will allocate new slice. This will happen for all iterations of the loop. We don't expect huge amounts of data in the slice so it's "alright"
d20d640
to
b511e24
Compare
b511e24
to
a1fc792
Compare
Signed-off-by: Evgeny Slutsky <[email protected]>
Signed-off-by: Evgeny Slutsky <[email protected]>
Signed-off-by: Evgeny Slutsky <[email protected]>
a1fc792
to
fe5539b
Compare
fe5539b
to
a40e8fb
Compare
@eslutsky: This pull request references USHIFT-2458 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set. In response to this: 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 openshift-eng/jira-lifecycle-plugin repository. |
@@ -408,6 +408,60 @@ func initKubeconfigs( | |||
klog.Warningf("Unable to remove stale kubeconfigs: %v", err) |
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.
Just realized, do we cleanup stale kubeconfigs for NamedCertificates no longer present in the config?
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.
yes its taken cared before generating the kubeconfig by running cleanupStaleKubeconfigs, https://github.com/openshift/microshift/blob/main/pkg/cmd/init.go#L407
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.
Two minor things, otherwise it looks pretty good
Signed-off-by: Evgeny Slutsky <[email protected]>
a40e8fb
to
3acbfc1
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: eslutsky, pmtk The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@eslutsky: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
No description provided.