Addons should be created and become available with their pods in a normal state.
Actual Behavior
When trying to add addons through Terraform or manually, the addons are added but remain in a "Not Available" state. Additionally, the pods associcated with these addons are in an "Abnormal" status.
If I check the cloud UI, I see the following details:
On the "Pods" tab for the addon:
Pod scheduling failed.: 0/2 nodes are available: 2 node(s) had untolerated taint {node.kubernetes.io/route-unreachable: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
In the "Nodes" tab of the cluster section, the "Node pool" is in the "Restricted schedulin" state with taint:
Hi, there,
I'm encountering an issue when adding addons to a CCE cluster while applying a Terraform configuration.
Terraform Version
Sbercloud Provider Version
Affected Resource(s)
Terraform Configuration Files
tf-config.zip
Debug Output
https://gist.github.com/xT10r/22909d1e1b5db02c4cce496ce8edb96a
Expected Behavior
Addons should be created and become available with their pods in a normal state.
Actual Behavior
When trying to add addons through Terraform or manually, the addons are added but remain in a "Not Available" state. Additionally, the pods associcated with these addons are in an "Abnormal" status.
If I check the cloud UI, I see the following details:
On the "Pods" tab for the addon:
In the "Nodes" tab of the cluster section, the "Node pool" is in the "Restricted schedulin" state with taint:
Steps to Reproduce
cce_node_pool
resourceterraform init
terraform plan
terraform apply