Skip to content
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

failed to read config #304

Open
attiliodrei opened this issue Jan 11, 2025 · 2 comments
Open

failed to read config #304

attiliodrei opened this issue Jan 11, 2025 · 2 comments

Comments

@attiliodrei
Copy link

Bug Report

Description

kubectl logs proxmox-csi-plugin-controller-fc58b4bb4-pvvwh
E0111 14:45:13.979739 1 main.go:132] "Failed to create controller service" err="failed to read config: error reading /etc/proxmox/config.yaml: open /etc/proxmox/config.yaml: no such file or directory"
i am using talos 1.9.1 + kubernetes 1.32.0

@sergelogvinov
Copy link
Owner

Hello, I’m truly sorry to hear about the challenges you faced with Kubernetes. The plugin requires a configuration file that contains the Proxmox API endpoint and account credentials.

If you use the helm upgrade/install method read this document https://github.com/sergelogvinov/proxmox-csi-plugin/blob/main/charts/proxmox-csi-plugin/README.md

if you use kubectl apply method check this documentation https://github.com/sergelogvinov/proxmox-csi-plugin/blob/main/docs/install.md#install-the-plugin-by-using-kubectl

@attiliodrei
Copy link
Author

attiliodrei commented Jan 12, 2025

ok, thank you, with helm installation works.
not clear zone server in a cluster environment.
what happen if node vm is migrated on another proxmox server and in case a zone proxmox go down , if need to change node zone label.

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

No branches or pull requests

2 participants