Skip to content
Helm Chart CI (Core)

feat: Support for enabling metrics in OpenTelemetry Collector #655

Sign in to view logs

feat: Support for enabling metrics in OpenTelemetry Collector

feat: Support for enabling metrics in OpenTelemetry Collector #655

Triggered via pull request September 28, 2023 19:40
@tomkerkhovetomkerkhove
synchronize #534
otel-chart
Status Cancelled
Total duration 17m 24s
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

58 errors and 44 warnings
Deploy to Kubernetes v1.25 in 'not-keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.25 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.26 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 (With Azure Workload Identity | Without cert-manager)
The run was canceled by @JorTurFer.
Deploy to Kubernetes v1.26 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
The run was canceled by @JorTurFer.
Deploy to Kubernetes v1.27 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
The run was canceled by @JorTurFer.
Deploy to Kubernetes v1.28 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
The run was canceled by @JorTurFer.
Deploy to Kubernetes v1.27 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
The run was canceled by @JorTurFer.
Deploy to Kubernetes v1.28 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
The run was canceled by @JorTurFer.
Deploy to Kubernetes v1.26 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
The run was canceled by @JorTurFer.
Deploy to Kubernetes v1.26 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
The run was canceled by @JorTurFer.
Deploy to Kubernetes v1.27 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
The run was canceled by @JorTurFer.
Deploy to Kubernetes v1.28 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
The run was canceled by @JorTurFer.
Deploy to Kubernetes v1.28 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
The run was canceled by @JorTurFer.
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)
The operation was canceled.
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.25 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.25 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.25 in 'not-keda' namespace (With Azure Workload Identity | With cert-manager)
The operation was canceled.
Deploy to Kubernetes v1.25 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.25 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.25 in 'not-keda' namespace (With Azure Workload Identity | Without cert-manager)
The operation was canceled.
Deploy to Kubernetes v1.25 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.25 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
The operation was canceled.
Deploy to Kubernetes v1.25 in 'keda' namespace (With Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.25 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.25 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.25 in 'keda' namespace (With Azure Workload Identity | With cert-manager)
The operation was canceled.
Deploy to Kubernetes v1.28 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
The operation was canceled.
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 'keda' namespace (Without Azure Workload Identity | With cert-manager)
The operation was canceled.
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.27 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
The operation was canceled.
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.26 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
The operation was canceled.
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 | With cert-manager)
The operation was canceled.
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.28 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
The operation was canceled.
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 '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)
The operation was canceled.
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)
The operation was canceled.
Deploy to Kubernetes v1.25 in 'keda' namespace (Without Azure Workload Identity | With cert-manager)
The operation was canceled.
Deploy to Kubernetes v1.25 in '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 | 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)
The operation was canceled.
Deploy to Kubernetes v1.25 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
The operation was canceled.
Deploy to Kubernetes v1.25 in 'keda' namespace (Without Azure Workload Identity | Without cert-manager)
Process completed with exit code 1.
Deploy to Kubernetes v1.25 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
The operation was canceled.
Deploy to Kubernetes v1.25 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.26 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
The operation was canceled.
Deploy to Kubernetes v1.27 in 'not-keda' namespace (Without Azure Workload Identity | With cert-manager)
The operation was canceled.
Deploy to Kubernetes v1.27 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.25 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.25 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.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.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.25 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.25 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.25 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.25 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.25 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.25 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.25 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.25 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
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.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.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 '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.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 '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 | 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.25 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.25 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 '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.25 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.25 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.25 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.25 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.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 '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