Skip to content
Helm Chart CI (Core)

Add insecureMetricsServiceSkipTLSVerify to helm config #780

Sign in to view logs

Add insecureMetricsServiceSkipTLSVerify to helm config

Add insecureMetricsServiceSkipTLSVerify to helm config #780

Triggered via pull request January 18, 2024 20:56
@aliaqel-stripealiaqel-stripe
opened #592
aliaqel-stripe:aliaqel/add-tls-skip-verify-for-grpcc
Status Failure
Total duration 7m 46s
Artifacts –

ci-core.yml

on: pull_request
Lint Helm Chart
3s
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.26 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 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 (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.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.23 in 'not-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 'not-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.27 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.27 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 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 | 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.26 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 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.28 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 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 '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.26 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.26 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.28 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
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
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.26 in 'keda' namespace (Without 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.26 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.26 in 'not-keda' namespace (Without 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.26 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.28 in 'keda' namespace (Without 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.28 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.27 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.27 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.28 in 'keda' namespace (With Azure Workload Identity | With 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.28 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.27 in 'not-keda' namespace (Without 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.27 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.27 in 'keda' namespace (Without Azure Workload Identity | With 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.27 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.27 in 'not-keda' namespace (Without Azure Workload Identity | With 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.27 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.27 in 'keda' namespace (With Azure Workload Identity | With 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.27 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.26 in 'not-keda' namespace (Without Azure Workload Identity | With 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.26 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.27 in 'keda' namespace (Without 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.27 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.27 in 'not-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.27 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 'not-keda' namespace (Without 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 '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 'keda' namespace (Without 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 (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)
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 '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 'keda' namespace (Without Azure Workload Identity | With 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 (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.27 in 'not-keda' namespace (With Azure Workload Identity | With 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.27 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.26 in 'keda' namespace (Without Azure Workload Identity | With 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.26 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.26 in 'not-keda' namespace (With Azure Workload Identity | With 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.26 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.28 in 'not-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.28 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.28 in 'keda' namespace (Without Azure Workload Identity | With 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.28 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.28 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.28 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 | With 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 | 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.26 in 'not-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.26 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.28 in 'not-keda' namespace (Without 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.28 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)
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 '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.28 in 'not-keda' namespace (With Azure Workload Identity | With 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.26 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.26 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.28 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 (With Azure Workload Identity | With 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 '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)
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)
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.26 in 'keda' namespace (With Azure Workload Identity | With 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.26 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.28 in 'not-keda' namespace (Without Azure Workload Identity | With 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.28 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