Add Tekton OpenShift testing (#720)

Use Tekton to run tests inside OpenShift

Author: thegridman

.github/workflows/build.yaml

@@ -49,6 +49,8 @@ jobs:
         dpkg-query -Wf '${Installed-Size}\t${Package}\n' | sort -n | tail -n 100
         df -h
         echo "Removing large packages"
+        sudo docker image prune --all --force
+        sudo docker builder prune -a
         sudo apt-get remove -y '^dotnet-.*' || true
         sudo apt-get remove -y '^llvm-.*' || true
         sudo apt-get remove -y 'monodoc-http' || true
@@ -60,6 +62,8 @@ jobs:
         echo "Removing large directories"
         rm -rf /usr/share/dotnet/
         sudo rm -rf /usr/local/lib/android
+        sudo rm -rf /opt/ghc
+        sudo rm -rf /opt/hostedtoolcache/CodeQL
         df -h
 
     - name: Set up JDK
@@ -122,6 +126,9 @@ jobs:
       run: |
         make kind-load
         make remove-all-images
+        sudo docker image prune --all --force
+        sudo docker builder prune -a
+        df -h
 
     - name: Unit Tests
       shell: bash

.github/workflows/istio-tests.yaml

@@ -55,6 +55,8 @@ jobs:
         dpkg-query -Wf '${Installed-Size}\t${Package}\n' | sort -n | tail -n 100
         df -h
         echo "Removing large packages"
+        sudo docker image prune --all --force
+        sudo docker builder prune -a
         sudo apt-get remove -y '^dotnet-.*' || true
         sudo apt-get remove -y '^llvm-.*' || true
         sudo apt-get remove -y 'monodoc-http' || true
@@ -66,6 +68,8 @@ jobs:
         echo "Removing large directories"
         rm -rf /usr/share/dotnet/
         sudo rm -rf /usr/local/lib/android
+        sudo rm -rf /opt/ghc
+        sudo rm -rf /opt/hostedtoolcache/CodeQL
         df -h
 
     - name: Set up JDK
@@ -108,21 +112,20 @@ jobs:
         make kind
         kubectl version
         kubectl get nodes
-        docker pull gcr.io/distroless/java
-        docker pull gcr.io/distroless/java11-debian11
-        docker pull gcr.io/distroless/java17-debian11
-        docker pull gcr.io/distroless/java17-debian12
-        docker pull gcr.io/distroless/java21-debian12
 
     - name: Build
       shell: bash
-      run: make all
+      run: | 
+        make all
 
     - name: Load Images to KinD
 #     Load the images just built to the KinD cluster
       shell: bash
       run: |
         make kind-load
+        sudo docker image prune --all --force
+        sudo docker builder prune -a
+        df -h
 
     - name: Istio Tests
       shell: bash

.gitignore

@@ -58,6 +58,5 @@ test/**/test-report.xml
 api/**/zz_*.go
 bundle.Dockerfile
 /__debug_bin
-hack/istio*/
 /java/certs/
 .flattened-pom.xml

Makefile

@@ -21,12 +21,15 @@ metadata:
     features.operators.openshift.io/token-auth-aws: "false"
     features.operators.openshift.io/token-auth-azure: "false"
     features.operators.openshift.io/token-auth-gcp: "false"
+    operatorframework.io/arch.amd64: supported
+    operatorframework.io/arch.arm64: supported
+    operatorframework.io/os.linux: supported
     operators.openshift.io/infrastructure-features: '["disconnected"]'
     operators.operatorframework.io/builder: operator-sdk-v1.39.1
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v4
     repository: https://github.com/oracle/coherence-operator
     support: Oracle Corporation
-  name: coherence-operator.v3.4.2
+  name: coherence-operator.v3.5.0
 spec:
   apiservicedefinitions: {}
   customresourcedefinitions:

config/manifests/bases/coherence-operator.clusterserviceversion.yaml

@@ -76,7 +76,7 @@ documentation.
 At the time of writing, for whatever reason, Grafana does not provide a simple way to bulk import a set of dashboard files.
 There are many examples and scripts on available in the community that show how to do this.
 The Coherence Operator source contains a script that can be used for this purpose
-https://github.com/oracle/coherence-operator/raw/main/hack/grafana-import.sh[grafana-import.sh]
+https://github.com/oracle/coherence-operator/raw/main/hack/grafana/grafana-import.sh[grafana-import.sh]
 
 NOTE: The `grafana-import.sh` script requires the https://stedolan.github.io/jq/[JQ] utility to parse json.
 
@@ -88,7 +88,7 @@ We do not document the credentials here as the default values have been known to
 
 [source,bash]
 ----
-curl -Lo grafana-import.sh https://github.com/oracle/coherence-operator/raw/main/hack/grafana-import.sh
+curl -Lo grafana-import.sh https://github.com/oracle/coherence-operator/raw/main/hack/grafana/grafana-import.sh
 chmod +x grafana-import.sh
 ----
 [source,bash]

docs/metrics/030_importing.adoc

@@ -33,6 +33,7 @@ pages:
         - "docs/**/*.adoc"
         - "examples/**/*.adoc"
     - excludes:
+        - "build/**"
 backend:
     name: "vuetify"
     homePage: "docs/about/01_overview.adoc"

docs/sitegen.yaml

@@ -758,7 +758,7 @@ https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentati
 If installing Prometheus into RBAC enabled k8s clusters, you may need to create the required RBAC resources
 as described in the https://prometheus-operator.dev/docs/operator/rbac/[Prometheus RBAC] documentation.
 The Coherence Operator contains an example that works with the out-of-the-box Prometheus Operator install
-that we use for testing https://raw.githubusercontent.com/oracle/coherence-operator/main/hack/prometheus-rbac.yaml[prometheus-rbac.yaml]
+that we use for testing https://raw.githubusercontent.com/oracle/coherence-operator/main/hack/prometheus/prometheus-rbac.yaml[prometheus-rbac.yaml]
 This yaml creates a `ClusterRole` with the required permissions and a `ClusterRoleBinding` that binds the role to the
 `prometheus-k8s` service account (which is the name of the account created, and used by the Prometheus Operator).
 This yaml file can be installed into k8s before installing the Prometheus Operator.