Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

refactor xDS components to not require kubeconfig #95

Closed
michelleN opened this issue Jan 30, 2020 · 3 comments
Closed

refactor xDS components to not require kubeconfig #95

michelleN opened this issue Jan 30, 2020 · 3 comments
Assignees
Milestone

Comments

@michelleN
Copy link
Contributor

michelleN commented Jan 30, 2020

Currently, we're passing the kube config file to generate a kubernetes client within each xDS component that it can communicate with the Kubernetes api server. There are ways of generating a client without passing in a kube config file. We'll need to mount a service account to each xDS pod so that it can authenticate inside the cluster like shown here.

@asridharan
Copy link
Contributor

@michelleN could you add a description to the issue?

Would this get resolved automatically by #96 ?

@michelleN
Copy link
Contributor Author

@asridharan - added a description. I don't believe it will be automatically resolved via #96 bc we could technically continue on even with the aggregated discovery service using the kube config. However, this solution can be integrated during that refactor.

@michelleN
Copy link
Contributor Author

resolved via #270

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants