New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloud provider could not be initialized: could not init cloud provider "vsphere": 1:1: expected section header #357
Comments
Hi @abregar! We haven't cut a release yet of the CPI, so currently the tags for the CPI in GCR point to 1.1.0 and latest still only support the INI configuration. Please use the documentation for the INI based format here: It might be worth keeping the INI based configuration through and just noting that it's legacy. Will open up a PR to do that this morning. |
Hi @abregar Updated the documentation to include the /close |
@dvonthenen: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Thank you for the clarification. Since I do like the yaml format, is there any estimated date on new CPI version release supporting this feature (and all the fixes since 1.1.0)? |
I'm in the process of working on that release right now. Also, since this might trip other people up (myself included just now), the port value is no longer a string but an int. Correct:
Incorrect:
|
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
Following the docs/book kubernetes-on-vsphere-with-kubeadm seems after the change Initial implementation for YAML based config controllermanager.go crashed after announcing 1:1: expected section header
crashed_manager.log
What you expected to happen:
Cloud provider initialized successfully
How to reproduce it (as minimally and precisely as possible):
Use manifests prior named change (csi-vsphere.conf not in yaml format) and try to initialize cloud provider
Anything else we need to know?:
csi-vsphere.conf was converted from conf to yaml as written in docs
Environment:
uname -a
): 3.10.0-1127.13.1.el7.x86_64The text was updated successfully, but these errors were encountered: