manusa / actions-setup-openshift

Set up your GitHub Actions workflow with a specific version of OKD (OpenShift/Origin)

Setup OpenShift GitHub Action

Set up your GitHub Actions workflow with a specific version of OKD (OpenShift/Origin).

Currently only Linux/Ubuntu CI environment is supported.

Usage

Basic

name: Example workflow

on: [push]

jobs:
  example:
    name: Example OpenShift Cluster interaction
    runs-on: ubuntu-20.04
    steps:
      - name: Checkout
        uses: actions/checkout@v1
      - name: Setup OpenShift
        uses: manusa/[email protected]
        with:
          oc version: 'v3.11.0'
          github token: ${{ secrets.GITHUB_TOKEN }}
      - name: Interact with the cluster
        run: oc cluster status

Required input parameters

Parameter	Description
oc version	OpenShift version to deploy

Optional input parameters

Parameter	Description
dns ip	External DNS server IP to use in node-config.yaml
enable	A list of components to enable (comma separated)
github token	GITHUB_TOKEN secret value to access GitHub REST API with an unlimited number of requests

License

The scripts and documentation in this project are released under the Apache 2.0.

actions-setup-openshift's Issues

Use shell scripts instead of Node, easier access to environment

Description

Switch from a node project to a Shell script-based project

Initialize project structure

Requirements

• GitHub action descriptor yaml (https://help.github.com/en/articles/metadata-syntax-for-github-actions)
• Node project
• CI Automation file (A.K.A. GitHub action for building action and running tests) Inception
  • Should checkout action code
  • Should setup node
  • Should install node package dependencies npm install
  • Should run and check all tests pass
  • Should try to build the Dockerfile representing the action image

DNS resolution fails within the Pods

Description

Trying to access an Internet domain from within a Pod is not possible due to domain name resolution failure (Access to Internet/external addresses is possible).

The file /etc/resolv.conf provided by OpenShift has the following content:

nameserver 172.30.0.2
search myproject.svc.cluster.local svc.cluster.local cluster.local
options ndots:5

Related issues

• openshift/origin#23495
• openshift/origin#19877
• openshift/origin#18358

Remove devDependencies from node_modules

Description

Minimize repository files by removing devDependencies using git hooks.

Draft release

Description

Necessary tasks to prepare an official release:

• Clean up code
• Add coverage
• ...

Yet again, switch back to Node project NOT running in Docker

Description

• Action to be implemented using Javascript/Node
• Full deployment (node_modules) must be available in git repo -> Action will have dependencies at runtime when checked out in other repository workflows.

Fix typos in readme and update tests

Description

Update typo in the basic usage instructions section in README.md.

Update tests to match methodology followed in https://github.com/manusa/action-setup-minikube

Ubuntu 22.04 support

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.

Repurpose project to use OpenShift Cluster

Description

Minishift won't be able to start in GitHub actions CI environment, as no virtualization support is provided (Both --vm-driver virtualbox and kvm fail)

On the other hand, OpenShift cluster does start.

https://docs.okd.io/latest/getting_started/administrators.html