Elgato_dark/podman-desktop
1
0
Fork 0
mirror of https://github.com/podman-desktop/podman-desktop synced 2026-04-21 17:47:22 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 10

docs: added a troubleshooting section (#15718)

Browse source 
* docs: added a troubleshooting section

Signed-off-by: Shipra Singh <shipsing@redhat.com>

* docs: fixed suggestions by coderabbit

Signed-off-by: Shipra Singh <shipsing@redhat.com>

---------

Signed-off-by: Shipra Singh <shipsing@redhat.com>
This commit is contained in:
Shipra Singh 2026-01-16 10:38:19 +05:30 committed by GitHub
parent 4a36cee7fe
commit 640cb36a64
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 32 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
website/docs/troubleshooting/troubleshooting-podman.md
View file

@ -271,3 +271,35 @@ Kubernetes clusters from cloud providers require an executable installed on the
1. Move the binary located in your `.kube/config` file to a system bin directory, such as `/usr/local/bin/`.
1. Set the value of the `command` parameter to the full path of the executable in your Kubernetes configuration file. For example, `command: /usr/local/bin/<cloud-provider-binary>`, where `cloud-provider-binary` denotes the binary name, such as `aws` or `oci`.
## Kubernetes clusters with custom CA certificates are not reachable
#### Issue
Podman Desktop might not connect to Kubernetes or OpenShift clusters that use custom certificates. This happens because the connection requires a specific local Certificate Authority (CA). You may see the following errors in the logs:
- `Error: self signed certificate in certificate chain`
- `x509: certificate signed by unknown authority`
Podman Desktop might not automatically use certificates from your machine's trust store, even if the CA is already installed on your operating system.
#### Solution
To resolve this, explicitly define the CA for the specific cluster in your Kubernetes configuration file.
1. Open your Kubernetes configuration file. The default location is `~/.kube/config`.
1. Locate the `clusters` entry for the cluster that fails to connect.
1. Add the `certificate-authority` property with the absolute path to your CA certificate.
_Example: `~/.kube/config` snippet_:
```yaml
apiVersion: v1
clusters:
- cluster:
certificate-authority: /home/user/.kube/my-cluster-ca.crt
server: https://api.my-cluster.example.com:6443
name: my-cluster-alias
```
1. Restart Podman Desktop to ensure the new configuration is loaded.