Cleanup unneeded PKS logic & fix for #56 #70
Merged
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.
What type of PR is this?
/kind feature
What this PR does / why we need it:
This cleans up pre-existing logic for handling PKS (Pivotal Kubernetes Service, aka. TKGi) where the K8s Root CA Cert was stored in a non-standard location.
Previously the Root CA Cert was read from either a PKS specific ConfigMap or from the in-cluster kubeconfig.
This change moves to reading the K8s Root CA cert from the now standardized
kube-root-ca.crt
ConfigMap that conformant k8s clusters will have in every namespace by default.This simplifies the code for the init container and moves to a unified logic.
Which issue(s) this PR fixes:
Fixes #56
Fixes #69
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., usage docs, etc.: