Running with gitlab-runner 13.11.0 (7f7a4bb0)  on gitlab-runners-bigbang-gitlab-runner-gitlab-runner-797d46cxptjg WntjV97x  feature flags: FF_GITLAB_REGISTRY_HELPER_IMAGE:true section_start:1623430521:resolve_secrets Resolving secrets section_end:1623430521:resolve_secrets section_start:1623430521:prepare_executor Preparing the "kubernetes" executor Using Kubernetes namespace: gitlab-runners Using Kubernetes executor with image registry.dso.mil/platform-one/big-bang/pipeline-templates/pipeline-templates/k3d-builder:0.0.5 ... section_end:1623430521:prepare_executor section_start:1623430521:prepare_script Preparing environment Waiting for pod gitlab-runners/runner-wntjv97x-project-3874-concurrent-06sqxw to be running, status is Pending Running on runner-wntjv97x-project-3874-concurrent-06sqxw via gitlab-runners-bigbang-gitlab-runner-gitlab-runner-797d46cxptjg... section_end:1623430524:prepare_script section_start:1623430524:get_sources Getting source from Git repository Fetching changes with git depth set to 50... Initialized empty Git repository in /builds/platform-one/big-bang/apps/developer-tools/haproxy/.git/ Created fresh repository. Checking out f7fedcc8 as refs/merge-requests/2/head... Skipping Git submodules setup section_end:1623430525:get_sources section_start:1623430525:step_script Executing "step_script" stage of the job script $ if [ -z ${PIPELINE_REPO_BRANCH} ]; then # collapsed multi-line command $ git clone -b ${PIPELINE_REPO_BRANCH} ${PIPELINE_REPO} ${PIPELINE_REPO_DESTINATION} Cloning into '../pipeline-repo'... $ echo "Directory structure of repository:" Directory structure of repository: $ tree . . |-- CODEOWNERS |-- README.md |-- chart | |-- Chart.yaml | |-- Kptfile | |-- README.md | |-- ci | | |-- daemonset-basic-values.yaml | | |-- daemonset-hostnet-values.yaml | | |-- deployment-basic-values.yaml | | |-- deployment-config-values.yaml | | |-- deployment-hpa-values.yaml | | `-- deployment-securitycontext-values.yaml | |-- templates | | |-- NOTES.txt | | |-- _helpers.tpl | | |-- bigbang | | | `-- virtualservices.yaml | | |-- configmap.yaml | | |-- daemonset.yaml | | |-- deployment.yaml | | |-- hpa.yaml | | |-- podsecuritypolicy.yaml | | |-- pullsecret.yaml | | |-- service.yaml | | `-- serviceaccount.yaml | `-- values.yaml `-- tests |-- main-test-gateway.yaml `-- test-values.yml 5 directories, 25 files $ echo "Generic configuration validation tests:" Generic configuration validation tests: $ if [ $(ls -1 tests/test-values.y*ml 2>/dev/null | wc -l) -gt 0 ]; then # collapsed multi-line command Checking test values... WARN - haproxy in the Deployment RELEASE-NAME-haproxy has ability to run as root WARN - Deployment RELEASE-NAME-haproxy using defaulting to image UID WARN - haproxy in the Deployment RELEASE-NAME-haproxy is missing livenessProbe WARN - haproxy in the Deployment RELEASE-NAME-haproxy is missing readinessProbe WARN - Deployment RELEASE-NAME-haproxy must include Kubernetes recommended labels: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/#labels WARN - haproxy in the Deployment RELEASE-NAME-haproxy does not have a memory requests set WARN - haproxy in the Deployment RELEASE-NAME-haproxy does not have a CPU requests set WARN - haproxy in the Deployment RELEASE-NAME-haproxy does not have a memory limit set WARN - haproxy in the Deployment RELEASE-NAME-haproxy does not have a CPU limit set WARN - haproxy in the Deployment RELEASE-NAME-haproxy does not have QoS class of Guaranteed 24 tests, 14 passed, 10 warnings, 0 failures Checking chart values... WARN - haproxy in the Deployment RELEASE-NAME-haproxy does not have a memory requests set WARN - haproxy in the Deployment RELEASE-NAME-haproxy does not have a CPU requests set WARN - haproxy in the Deployment RELEASE-NAME-haproxy does not have a memory limit set WARN - haproxy in the Deployment RELEASE-NAME-haproxy does not have a CPU limit set WARN - haproxy in the Deployment RELEASE-NAME-haproxy does not have QoS class of Guaranteed WARN - haproxy in the Deployment RELEASE-NAME-haproxy has ability to run as root WARN - Deployment RELEASE-NAME-haproxy using defaulting to image UID WARN - Deployment RELEASE-NAME-haproxy must include Kubernetes recommended labels: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/#labels WARN - haproxy in the Deployment RELEASE-NAME-haproxy is missing livenessProbe WARN - haproxy in the Deployment RELEASE-NAME-haproxy is missing readinessProbe 24 tests, 14 passed, 10 warnings, 0 failures $ if [ -d "tests/policy" ]; then # collapsed multi-line command section_end:1623430526:step_script section_start:1623430526:cleanup_file_variables Cleaning up file based variables section_end:1623430526:cleanup_file_variables Job succeeded