Closed matteomasciari closed 3 months ago
Little update: By installing the original vcluster chart (it works fine) I found this difference in the init container:
initContainers:
- args:
- -c
- cp /bin/k3s /binaries/k3s
command:
- /bin/sh
image: rancher/k3s:v1.29.0-k3s1
initContainers:
- args:
- -c
- cp /vcluster /binaries/vcluster
command:
- /bin/sh
image: ghcr.io/loft-sh/vcluster:0.19.5
So the default Controlplane used by vcluster (k3s) works fine on Openshift, but the standard controlplan, used by Krateo installation doesn't work.
I hope this can help you in the analysis of the problem
The problem seems related to SELinux, indeed by switching from Enforcing to Permissive vcluster starts
Describe the bug On an Openshift Cluster like:
❯ oc version Client Version: 4.15.8 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: 4.13.25 Kubernetes Version: v1.26.9+aa37255
After installing the helm chart with these values:
The pod of the deployment "vcluster-k8s" give me this error:
I tried also with these values:
To Reproduce Steps to reproduce the behavior: On an Openshift environment, run the command:
with custom.values.yaml: