> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/unable-to-add-kubernetes-cloud-provider-with-a-secret-engine.md).

# Unable to Add Kubernetes Cloud Provider with a Secret Engine

### Issue <a href="#issue" id="issue"></a>

When adding a Cloud Provider Account using a secret, the SpinnakerServices validator will throw an error stating that there isn't sufficient permissions to access the cluster: `The kubeconfig does not have explicit permissions to the target cluster's resources`. for: "STDIN": admission webhook "webhook-spinnakerservices-v1alpha2.spinnaker.armory.io" denied the request: SpinnakerService validation failed: Validator for account 'spinnaker' detected an error: error listing namespaces in account "spinnaker": Get https\://$CLUSTER\_URL\_HERE/api/v1/namespaces: exec: exit status 255

### Cause <a href="#cause" id="cause"></a>

The kubeconfig does not have explicit permissions to the target cluster's resources, and this will need to be defined.