diff --git a/.github/workflows/kube-linter.yaml b/.github/workflows/kube-linter.yaml
index d8cdbc3..5efbae4 100644
--- a/.github/workflows/kube-linter.yaml
+++ b/.github/workflows/kube-linter.yaml
@@ -9,11 +9,6 @@ jobs:
     steps:
       - uses: actions/checkout@v2
 
-      # This prepares directory where github/codeql-action/upload-sarif@v1 looks up report files by default.
-      - name: Create ../results directory for SARIF report files
-        shell: bash
-        run: mkdir -p ../results
-
       - name: Scan yaml files with kube-linter
         uses: stackrox/kube-linter-action@v1.0.4
         id: kube-linter-action-scan
@@ -22,21 +17,4 @@ jobs:
           directory: "."
           # Adjust this to the location of kube-linter config you're using, or remove the setting if you'd like to use
           # the default config.
-          config: .kube-linter.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: ../results/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@v2
-
-      # 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" ]]
\ No newline at end of file
+          config: .kube-linter.yaml
\ No newline at end of file