Add option to use anonymous authentication in k8s WorkloadAttestor #3273
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.
Pull Request check list
Affected functionality
k8s
WorkloadAttestor plugin integration with kubeletDescription of change
The
k8s
WorkloadAttestor plugin does not provide a way to obtain selectors from the kubelet over the secure port when the kubelet is configured to use anonymous authentication. Add a configuration fielduse_anonymous_authentication
that allows the plugin to send unauthenticated requests to the kubelet secure port.Which issue this PR fixes
#3193
Tested this with the
k8s-reconcile
test with these changes applied in my local branch: 0d59a37