# set the kubeconfig to proper cluster
$ export KUBECONFIG=/home/.kube/config
# run the ./hack/test-pj.sh script, following the script runs the k8s-ppc64le-cluster-health-check
# on the cluster configured by KUBECONFIG(default: ${HOME}/.kube/config) and creates
# a file pod_table.txt in the present working directory with details about the
# job. The -j flag is used to specify the job to be run and is mandatory. The -p (purpose) flag
# is used to specify the purpose for which the job is being run and is optional.
# The job name and the purpose among other details will be populated in pod_table.txt
# if the purpose flag is set.
$ CONFIG_PATH=$(pwd)/config/prow/config.yaml JOB_CONFIG_PATH=$(pwd)/config/jobs/ppc64le-cloud/test-infra/test-infra-periodics.yaml ./hack/test-pj.sh -j k8s-ppc64le-cluster-health-check -p "Cluster health after new jobs"- https://prow.ppc64le-cloud.cis.ibm.net/ - Dashboard for internal prow jobs that run on ppc64le build cluster and a few on IKS(x86) cluster.
- https://search.ppc64le-cloud.cis.ibm.net/ - ci-search tool by openshift, configured to our internal prow jobs that have logs uploaded to GCS storage.
- https://jenkins.ppc64le-cloud.cis.ibm.net/ - Jenkins dashboard for OCP jobs run on Jenkins infra.
- https://grafana.ppc64le-cloud.cis.ibm.net - Grafana dashboard for analysing OCP jobs from Jenkins.
03 May 2022 - Usage of pod-utility images from locally built and pushed quay.io/powercloud private repo is deprecated.
The upstream pod-utility images from gcr.io/k8s-prow will be used - Change
Files from here will not be used.