Skip to content
Helm Chart CI (Core)

add: helm values for --enable-webhook-patching flag #995

Sign in to view logs

add: helm values for --enable-webhook-patching flag

add: helm values for --enable-webhook-patching flag #995

Triggered via pull request December 9, 2024 13:17
@KrishnaSindhurKrishnaSindhur
opened #715
KrishnaSindhur:webhook-flag
Status Failure
Total duration 7m 7s
Artifacts –

ci-core.yml

on: pull_request
Lint Helm Chart
4s
Lint Helm Chart
Matrix: deploy-helm-3-x
Fit to window
Zoom out
Zoom in

Annotations

64 errors and 66 warnings
Deploy to Kubernetes v1.29 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.29 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.31 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.30 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Lint Helm Chart
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Lint Helm Chart
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.29 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.29 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.29 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.29 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.29 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.29 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.29 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.29 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.31 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.31 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.23 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.23 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.23 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.23 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.29 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.29 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.29 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.29 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.30 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.30 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.23 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.23 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.29 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.29 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.29 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.29 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.31 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.31 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.23 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.23 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.30 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.30 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.30 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.30 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.23 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.23 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.31 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.31 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.30 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.30 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.30 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.30 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.31 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.31 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.23 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.23 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.30 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.30 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.30 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.30 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0
Deploy to Kubernetes v1.30 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy to Kubernetes v1.30 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0