Draft: Create k8s API secret/token manually to support Kubernetes 1.24+. #60
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.
This PR creates Kubernetes API secret/token manually to support Kubernetes 1.24+. This functionality has been available since ~ Kubernetes 1.13, so it seems safe to replace the previous code.
Prior to Kubernetes 1.24, creating a Kubernetes Service Account would automatically create a non-expiring secret/token. As of 1.24, this needs secret must be created manually. Additionally, it needs to have a special annotation to associating it with the service account.