-
Notifications
You must be signed in to change notification settings - Fork 95
Updated Document about Worker node labeling for CSI #477
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
Conversation
Thank you for your pull request and welcome to our community! To contribute, please sign the Oracle Contributor Agreement (OCA).
The following contributors of this PR have not signed the OCA:
- PR author: maurerezi.p@gmail.com (@Oreo-Tech)
To sign the OCA, please create an Oracle account and sign the OCA in Oracle's Contributor Agreement Application.
When signing the OCA, please provide your GitHub username. After signing the OCA and getting an OCA approval from Oracle, this PR will be automatically updated.
If you are an Oracle employee, please make sure that you are a member of the main Oracle GitHub organization, and your membership in this organization is public.
These labels get set automatically if the CCM container is running correctly. Can you check the logs of the CCM container to figure out whats failing
during the step of setting the CSI node driver the pods were failing with error
response": "{\"name\":\"fss.csi.oraclecloud.com\",\"vendor_version\":\"0.1.0\"}"}
2024年05月21日T11:06:56.122Z ERROR FSS csi-util/utils.go:119 Did not find the label for the fault domain. {"nodeId": "pvtrihesk8w2dr", "label": "failure-domain.beta.kubernetes.io/zone"}
2024年05月21日T11:06:56.122Z ERROR FSS driver/fss_node.go:420 Failed to get availability domain of node from kube api server. {"error": "Did not find the label for the fault domain.", "nodeId": "pvtrihesk8w2dr", "availabilityDomain": ""}
While setting CSI on a custom Kubernetes cluster setup, we came across these two labels that were required for to complete CSI setup on the cluster