Ensure Kubespawner internal SSL secret is correctly encoded as base64 #828
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.
test_spawn_internal_ssl
is failing on the main branch.This additional (currently failing) test suggests the certificates in the Kubernetes secret is not correctly encoded as base64:
This seems to be caused by the base64 encoded
notebooks-ca_trust.crt
containing a==
in the middle, followed by more encoded data.==
should only appear as padding at the end.