-
Notifications
You must be signed in to change notification settings - Fork 76
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
Add bootstrap Authenticator and CSR registration #510
Add bootstrap Authenticator and CSR registration #510
Conversation
Codecov Report
@@ Coverage Diff @@
## main #510 +/- ##
==========================================
- Coverage 67.32% 63.97% -3.36%
==========================================
Files 22 25 +3
Lines 1732 1904 +172
==========================================
+ Hits 1166 1218 +52
- Misses 494 608 +114
- Partials 72 78 +6
|
Also, this part of the code is untested? |
CSR registration wnd BootstrapAuthenticator will be handled behind SecureAccess feature flag. CSR resource will be created in the management cluster on the start of the HostAgent. BootstrapAuthenticator controller will watch the CSR resources. Currently placeholders are created for different flows and the implementation will be raised in differemt PRs
There is already a test case added should create BYOHost CSR in the management cluster, and the code block is only initializing struct type and calling some methods. |
💭 We should try to keep the coverage as is and not reduce it from achieved higher value 💭 |
The CSR naming is changed to byoh-csr-<hostname> so that the same can be picked in ByoAdmisisonController. As CSR is clusterscoped resource, usage of namespace is removed. EnvTest k8s version is updated to 1.23.3 as ExpirationSeconds is supported after v1.22.x
@pshail, I agree. Currently, the code coverage is less
|
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.
minor nits. LGTM otherwise.
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
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.
Overall LGTM just need clarity on main error handling related to CSR creation failure(s)
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
What this PR does / why we need it:
This PR implements CSR registration and
BootstrapAuthenticator
controller as per the design for feature #484.Both CSR registration/BootstrapAuthenticator Controller logic is disabled by default and will be kept behind the
SecureAccess
feature flag, which can be enabled explicitly while starting theHostAgent
.Which issue(s) this PR fixes :
Fixes #508 #509(partially)