Skip to content

Add a new stage to push preprocess and JBS Containerfile changes to git #244

Add a new stage to push preprocess and JBS Containerfile changes to git

Add a new stage to push preprocess and JBS Containerfile changes to git #244

Workflow file for this run

name: Validate Kubernetes YAMLs
on:
pull_request:
branches: [ main ]
paths:
- 'deploy/crds/base/**.ya?ml'
- 'deploy/operator/base/**.ya?ml'
- 'deploy/operator/config/**.ya?ml'
jobs:
kube-linter:
name: Kube linter
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b # v4
- name: Create ../kube-linter/ for deployment yaml files
shell: bash
run: mkdir -p ../kube-linter/
- name: Generate JVM Build Service operator deployment configuration
shell: bash
run: |
kustomize build deploy/crds/base/ > ../kube-linter/jvm-build-service-crd.yaml && \
kustomize build deploy/operator/base/ > ../kube-linter/jvm-build-service-operator-base.yaml && \
kustomize build deploy/operator/config/ > ../kube-linter/jvm-build-service-operator-config.yaml
- name: Scan yaml files with kube-linter
uses: stackrox/kube-linter-action@5792edc6a03735d592b13c08201711327a935735 # v1
id: kube-linter-action-scan
with:
# Where to do scanning
directory: ../kube-linter/
# Where to search for kube-linter config. Removing the setting make using the default config.
config: ./.github/.kube-linter-config.yaml
# The following two settings make kube-linter produce scan analysis in SARIF format
# which would then be made available in GitHub UI via upload-sarif action below.
format: sarif
output-file: ../kube-linter/kube-linter.sarif
# The following line prevents aborting the workflow immediately in case your files fail kube-linter checks.
# This allows the following upload-sarif action to still upload the results to your GitHub repo.
continue-on-error: true
- name: Upload SARIF report files to GitHub
uses: github/codeql-action/upload-sarif@d39d31e687223d841ef683f52467bd88e9b21c14 # v3
with:
sarif_file: ../kube-linter/kube-linter.sarif
# Ensure the workflow eventually fails if files did not pass kube-linter checks.
- name: Verify kube-linter-action succeeded
shell: bash
run: |
echo "If this step fails, kube-linter found issues. Check the output of the scan step above."
[[ "${{ steps.kube-linter-action-scan.outcome }}" == "success" ]]