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

Documentation missing details for region(s) generated kubconfig folder #107

Closed
OJDUDE opened this issue Nov 18, 2016 · 4 comments · Fixed by #1345
Closed

Documentation missing details for region(s) generated kubconfig folder #107

OJDUDE opened this issue Nov 18, 2016 · 4 comments · Fixed by #1345

Comments

@OJDUDE
Copy link

OJDUDE commented Nov 18, 2016

I managed to deploy a Kubernetes cluster successfully from the first time. It was actually great. I just noticed that the acs-engine created a kubconfig folder with server configuration for each supported region. I did not see the files anywhere referenced in your docs on how to use. Can you please point to the docs that provide more details what to use these files for?

@anhowe
Copy link
Contributor

anhowe commented Jan 23, 2017

Each region will get a separate DNS URL. ACS-Engine is not aware of which region you will deploy to and generates a kubeconfig for each region. Once you have deployed to the region, you just use the appropriate kubeconfig for the region deployed to.

@anhowe
Copy link
Contributor

anhowe commented May 1, 2017

@squillace can you help with documentation around this?

@ppanyukov
Copy link

@anhowe :

you just use the appropriate kubeconfig for the region deployed to

not sure this clarified anything for me, use how? :)

@jackfrancis
Copy link
Member

@ppanyukov @OJDUDE we have lots of color aroung kubeconfig regions in this doc:

https://github.com/Azure/acs-engine/blob/master/docs/kubernetes/deploy.md

That is now linked to from the general purpose acsengine doc, so hopefully folks in the future will more easily find this info.

jim-minter added a commit to jim-minter/acs-engine that referenced this issue Apr 13, 2018
autoprovision managed disks for azure PVs, otherwise it doesn't work
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants