Skip to content
Helm Chart CI (Core)

Prepare v2.16 #983

Sign in to view logs

Prepare v2.16

Prepare v2.16 #983

Triggered via pull request November 7, 2024 10:50
@JorTurFerJorTurFer
synchronize #704
SpiritZhou:prepare2160
Status Cancelled
Total duration 2m 36s
Artifacts –

ci-core.yml

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

Annotations

76 errors and 39 warnings
Deploy to Kubernetes v1.29 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.29 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.23 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.29 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.29 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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.23 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.23 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
The operation was canceled.
Deploy to Kubernetes v1.23 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Deploy to Kubernetes v1.29 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.29 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
The operation was canceled.
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 (With Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Deploy to Kubernetes v1.23 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
The operation was canceled.
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.30 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.30 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
The operation was canceled.
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 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.30 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
The operation was canceled.
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 (With Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.30 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
The operation was canceled.
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.31 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
The operation was canceled.
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.30 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Deploy to Kubernetes v1.23 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Deploy to Kubernetes v1.30 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.30 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
The operation was canceled.
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.31 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.31 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
The operation was canceled.
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.30 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.30 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
The operation was canceled.
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.23 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.23 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
The operation was canceled.
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.29 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Deploy to Kubernetes v1.31 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Deploy to Kubernetes v1.29 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Deploy to Kubernetes v1.30 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Deploy to Kubernetes v1.31 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
Deploy to Kubernetes v1.31 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
The operation was canceled.
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.30 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Canceling since a higher priority waiting request for 'Helm Chart CI (Core)-prepare2160' exists
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)
The operation was canceled.
Lint Helm Chart
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Lint Helm Chart
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, Azure/setup-helm@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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.31 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy to Kubernetes v1.31 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, Azure/setup-helm@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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.23 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy to Kubernetes v1.23 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, Azure/setup-helm@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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 '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.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.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.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 | 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 | 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 | 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 | 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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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