-
Notifications
You must be signed in to change notification settings - Fork 68
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
rfc2136 provider: expect base64 encoded TSIG key #347
Conversation
@Avarei Thank you for your contribution. |
Thank you @Avarei for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below. |
@MartinWeindel fyi |
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
Thank you for the improvement.
What this PR does / why we need it:
Usually both tsig key tools generate, and dns servers are configured using the base64 encoded version of the TSIG Key.
This PR reduces complexity by removing base64 encoding during runtime, which removes the need to decode it for the Kubernetes Secret.
This also makes integration with external secret providers easier, as the binary data from the tsig key could be difficult to copy.
Which issue(s) this PR fixes:
Fixes #346
Special notes for your reviewer:
the diff in go.mod is due to running
go mod tidy
Release note: