> 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/openshift-how-to-supply-the-complete-certificate-chain.md).

# OpenShift- How to supply the complete certificate chain

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

Validator error when attempting to apply changes: `certificate signed by unknown authority`

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

OpenShift is not supplying the full certificate chain for verifying the certificate from the server.The issue occurs when a user's certificate originates from Kubernetes in the `kubeconfig` file (base64 encoded PEM format certs).The **OpenShift cluster** includes the **leaf cert**, which is used by the API server. A number of supporting certs in the `kubeconfig` file are also provided, but not the certificates needed to verify the **leaf cert**.