Ubuntu 22.04 support

[nijel]

Are there any plans for supporting Ubuntu 22.04? Presently, this fails to start kube-apiserver.

Failed run

Updating Docker configuration to support OC insecure registry
Loading input variables
Downloading OpenShift Cluster v3.11.0
OpenShift Cluster version found at: https://github.com/openshift/origin/releases/download/v3.11.0/openshift-origin-client-tools-v3.11.0-0cbc58b-linux-64bit.tar.gz
Installing OpenShift Cluster
Current working directory: /home/runner/work/openshift/openshift
/usr/bin/tar xz --warning=no-unknown-keyword --overwrite -C /home/runner/work/_temp/ed91ea0d-6fde-40a8-bb98-5c06e950dbaf -f /home/runner/work/_temp/6a5752fe-8bc3-43c8-bf7c-8d81451c243d
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Pulling image openshift/origin-control-plane:v3.11
Pulled 1/5 layers, 27% complete
Pulled 2/5 layers, 45% complete
Pulled 3/5 layers, 71% complete
Pulled 4/5 layers, 82% complete
Pulled 5/5 layers, 100% complete
Extracting
Image pull complete
Pulling image openshift/origin-cli:v3.11
Image pull complete
Pulling image openshift/origin-node:v3.11
Pulled 6/6 layers, 100% complete
Extracting
Image pull complete
Creating shared mount directory on the remote host ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
I0809 17:54:59.428786    1991 config.go:40] Running "create-master-config"
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I0809 17:55:01.974783    1991 config.go:46] Running "create-node-config"
I0809 17:55:02.692975    1991 flags.go:30] Running "create-kubelet-flags"
I0809 17:55:03.090000    1991 run_kubelet.go:49] Running "start-kubelet"
I0809 17:55:03.172988    1991 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0809 18:00:03.174469    1991 run_self_hosted.go:571] API server error: Get https://127.0.0.1:8443/healthz?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused ()
Error: timed out waiting for the condition
Error: Command failed: oc cluster up --routing-suffix="127.0.0.1.${OC_DOMAIN:-nip.io}" 
    at checkExecSyncError (node:child_process:828:11)
    at Object.execSync (node:child_process:899:15)
    at logExecSync (/home/runner/work/_actions/manusa/actions-setup-openshift/v1.1.5/src/exec.js:8:17)
    at clusterUp (/home/runner/work/_actions/manusa/actions-setup-openshift/v1.1.5/src/install.js:16:3)
    at startCluster (/home/runner/work/_actions/manusa/actions-setup-openshift/v1.1.5/src/install.js:18:39)
    at install (/home/runner/work/_actions/manusa/actions-setup-openshift/v1.1.5/src/install.js:46:3)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async run (/home/runner/work/_actions/manusa/actions-setup-openshift/v1.1.5/src/index.js:16:3) {
  status: 1,
  signal: null,
Error: Command failed: oc cluster up --routing-suffix="127.0.0.1.${OC_DOMAIN:-nip.io}" 
Error: Command failed: oc cluster up --routing-suffix="127.0.0.1.${OC_DOMAIN:-nip.io}" 
  output: [ null, null, null ],
  pid: 1990,
  stdout: null,
  stderr: null
}

This seems to be a known issue, as 20.04 was pinned in 86d19ff.