/
Secure Mode K3s
Secure Mode K3s
If the cluster has been deployed before January 2023, most probably it will come across this issue at some point.
If cluster runs a pod that uses a public image that hasn’t yet been copied to our public repo, error ErrImagePull
with the message Failed to pull image
will arise.
To address this issue this configuration file needs to be added, /etc/rancher/k3s/registries.yaml
with the following contents:
mirrors:
"*":
endpoint:
- "https://images.master.k3s.getvisibility.com"
rewrite:
"(.*)": "gv-public/$1"
"images.master.k3s.getvisibility.com":
endpoint:
- "https://images.master.k3s.getvisibility.com"
This file instructs K3s to rewrite all images (except images.master.k3s.getvisibility.com
) and redirect them to Getvisibility’s public repository.
, multiple selections available,
Related content
K3s Installation
K3s Installation
Read with this
Prerequisites for k3s on RHEL/CentOS/Oracle Linux
Prerequisites for k3s on RHEL/CentOS/Oracle Linux
Read with this
SIEM Integration with Webhooks
SIEM Integration with Webhooks
Read with this
Release Notes
Release Notes
Read with this
Configuring Rancher and Fleet agent to run behind a HTTP proxy if cluster was previously registered
Configuring Rancher and Fleet agent to run behind a HTTP proxy if cluster was previously registered
More like this
Re-register cluster in rancher
Re-register cluster in rancher
More like this
Classified as Getvisibility - Partner/Customer Confidential