-
Notifications
You must be signed in to change notification settings - Fork 137
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Stop serving and fetching the tls cert used for gRPC (#584)
## Description - Stops serving the gRPC cert via http and stops fetching it. - Cleans up a ton of code that was confusing to read in the clients due to dealing with the gRPC certificate. - Removes a few Config structs that are passed into funcs These were used to get around having lots of parameters and the long lines that caused, but now are just one or two values. ## Why is this needed The whole serving of the gRPC certificate via http as `/cert` should never have made it to tinkerbell. It's too easy to use incorrectly and fall into a sense of security that may not be there. Its also a pain to actually use in production when following modern best practices of short lived TLS certificates. Clients can't use gRPC's/Go's builtin certificate handling of when certs are rotated. This is not a lot of good, yet a bunch of bad only to make a corner case easier at the expense of normal route. `/cert` makes self-sigend certs "easy"ish (see cert rotation issue still) but it's just not worth it. If someone can handle the implications of self-signed certs in production (#567 can be used for dev envs) then they can figure out how to embed their CA into hook or roll their own tink-worker environment. ## How Has This Been Tested? Compiles and tests pass. ## How are existing users impacted? What migration steps/scripts do we need? This is a breaking change for out-of-tree clients, I think its worth it compared to the ops / security benefits. Fixes #324
- Loading branch information
Showing
24 changed files
with
298 additions
and
442 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.