feat: support custom ca request header authentication #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The aggregated apiserver can support custom authentication by pointing to the CA file to trust and headers to use for authentication with a core apiserver that's proxying requests. This can be used in custom deployments of the aggregated apiserver where it may not be running in a real kubernetes control plane.
I also made some changes to make log level configurable and fixed logging being configured through CLI flags.
Relates to https://github.com/datum-cloud/engineering/issues/90