SeleniumHQ / docker-selenium

Provides a simple way to run Selenium Grid with Chrome, Firefox, and Edge using Docker, making it easier to perform browser automation
http://www.selenium.dev/docker-selenium/
Other
7.99k stars 2.51k forks source link

chore(deps): update helm release kube-prometheus-stack to v66 #2461

Open renovate[bot] opened 2 weeks ago

renovate[bot] commented 2 weeks ago

This PR contains the following updates:

Package Update Change
kube-prometheus-stack (source) major 65.8.1 -> 66.2.1

Release Notes

prometheus-community/helm-charts (kube-prometheus-stack) ### [`v66.2.1`](https://redirect.github.com/prometheus-community/helm-charts/releases/tag/kube-prometheus-stack-66.2.1) [Compare Source](https://redirect.github.com/prometheus-community/helm-charts/compare/kube-prometheus-stack-66.2.0...kube-prometheus-stack-66.2.1) kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator. ##### What's Changed - \[kube-prometheus-stack] Fix README.md by [@​muffl0n](https://redirect.github.com/muffl0n) in [https://github.com/prometheus-community/helm-charts/pull/4998](https://redirect.github.com/prometheus-community/helm-charts/pull/4998) **Full Changelog**: https://github.com/prometheus-community/helm-charts/compare/kube-prometheus-stack-66.2.0...kube-prometheus-stack-66.2.1 ### [`v66.2.0`](https://redirect.github.com/prometheus-community/helm-charts/releases/tag/kube-prometheus-stack-66.2.0) [Compare Source](https://redirect.github.com/prometheus-community/helm-charts/compare/kube-prometheus-stack-66.1.1...kube-prometheus-stack-66.2.0) kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator. #### What's Changed - \[kube-prometheus-stack] regenerate dashboards and alerts by [@​DrFaust92](https://redirect.github.com/DrFaust92) in [https://github.com/prometheus-community/helm-charts/pull/4997](https://redirect.github.com/prometheus-community/helm-charts/pull/4997) **Full Changelog**: https://github.com/prometheus-community/helm-charts/compare/kube-prometheus-stack-66.1.1...kube-prometheus-stack-66.2.0 ### [`v66.1.1`](https://redirect.github.com/prometheus-community/helm-charts/releases/tag/kube-prometheus-stack-66.1.1) [Compare Source](https://redirect.github.com/prometheus-community/helm-charts/compare/kube-prometheus-stack-66.1.0...kube-prometheus-stack-66.1.1) kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator. #### What's Changed - \[kube-prometheus-stack] Fix Helm template error by using hasKey to ch… by [@​traberph](https://redirect.github.com/traberph) in [https://github.com/prometheus-community/helm-charts/pull/4976](https://redirect.github.com/prometheus-community/helm-charts/pull/4976) #### New Contributors - [@​traberph](https://redirect.github.com/traberph) made their first contribution in [https://github.com/prometheus-community/helm-charts/pull/4976](https://redirect.github.com/prometheus-community/helm-charts/pull/4976) **Full Changelog**: https://github.com/prometheus-community/helm-charts/compare/prometheus-25.30.0...kube-prometheus-stack-66.1.1 ### [`v66.1.0`](https://redirect.github.com/prometheus-community/helm-charts/releases/tag/kube-prometheus-stack-66.1.0) [Compare Source](https://redirect.github.com/prometheus-community/helm-charts/compare/kube-prometheus-stack-66.0.0...kube-prometheus-stack-66.1.0) kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator. #### What's Changed - \[kube-prometheus-stack] bump deps by [@​DrFaust92](https://redirect.github.com/DrFaust92) in [https://github.com/prometheus-community/helm-charts/pull/4989](https://redirect.github.com/prometheus-community/helm-charts/pull/4989) **Full Changelog**: https://github.com/prometheus-community/helm-charts/compare/kube-state-metrics-5.27.0...kube-prometheus-stack-66.1.0 ### [`v66.0.0`](https://redirect.github.com/prometheus-community/helm-charts/compare/kube-prometheus-stack-65.8.1...kube-prometheus-stack-66.0.0) [Compare Source](https://redirect.github.com/prometheus-community/helm-charts/compare/kube-prometheus-stack-65.8.1...kube-prometheus-stack-66.0.0)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR was generated by Mend Renovate. View the repository job log.

codiumai-pr-agent-pro[bot] commented 2 weeks ago

CI Failure Feedback 🧐

(Checks updated until commit https://github.com/SeleniumHQ/docker-selenium/commit/689878aea3c5ad238a5191b6c29d9068bf10a138)

**Action:** Test Selenium Grid on Kubernetes / Test K8s (v1.27.16, job, minikube, v3.12.3, 24.0.9, true, true)
**Failed stage:** [Verify chart configuration up-to-date](https://github.com/SeleniumHQ/docker-selenium/actions/runs/11864056974/job/33068011538) [❌]
**Failed test name:** lint_readme_charts
**Failure summary:** The action failed due to the following reasons:
  • The make lint_readme_charts command failed because there were new changes in the chart that were not
    reflected in the README files. The error message suggests running make generate_readme_charts to
    update the documentation.
  • The process completed with exit code 2, indicating a failure in the make command execution.
  • Relevant error logs: ```yaml 1: ##[group]Operating System 2: Ubuntu ... 167: fi 168:  169: # Option: Remove large packages 170: # REF: https://github.com/apache/flink/blob/master/tools/azure-pipelines/free_disk_space.sh 171:  172: if [[ false == 'true' ]]; then 173:  BEFORE=$(getAvailableSpace) 174:   175:  sudo apt-get remove -y '^aspnetcore-.*' || echo "::warning::The command [sudo apt-get remove -y '^aspnetcore-.*'] failed to complete successfully. Proceeding..." 176:  sudo apt-get remove -y '^dotnet-.*' --fix-missing || echo "::warning::The command [sudo apt-get remove -y '^dotnet-.*' --fix-missing] failed to complete successfully. Proceeding..." 177:  sudo apt-get remove -y '^llvm-.*' --fix-missing || echo "::warning::The command [sudo apt-get remove -y '^llvm-.*' --fix-missing] failed to complete successfully. Proceeding..." 178:  sudo apt-get remove -y 'php.*' --fix-missing || echo "::warning::The command [sudo apt-get remove -y 'php.*' --fix-missing] failed to complete successfully. Proceeding..." 179:  sudo apt-get remove -y '^mongodb-.*' --fix-missing || echo "::warning::The command [sudo apt-get remove -y '^mongodb-.*' --fix-missing] failed to complete successfully. Proceeding..." 180:  sudo apt-get remove -y '^mysql-.*' --fix-missing || echo "::warning::The command [sudo apt-get remove -y '^mysql-.*' --fix-missing] failed to complete successfully. Proceeding..." 181:  sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing || echo "::warning::The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding..." 182:  sudo apt-get remove -y google-cloud-sdk --fix-missing || echo "::debug::The command [sudo apt-get remove -y google-cloud-sdk --fix-missing] failed to complete successfully. Proceeding..." 183:  sudo apt-get remove -y google-cloud-cli --fix-missing || echo "::debug::The command [sudo apt-get remove -y google-cloud-cli --fix-missing] failed to complete successfully. Proceeding..." 184:  sudo apt-get autoremove -y || echo "::warning::The command [sudo apt-get autoremove -y] failed to complete successfully. Proceeding..." 185:  sudo apt-get clean || echo "::warning::The command [sudo apt-get clean] failed to complete successfully. Proceeding..." ... 543: with: 544: timeout_minutes: 10 545: max_attempts: 3 546: command: make setup_dev_env 547: 548: retry_wait_seconds: 10 549: polling_interval_seconds: 1 550: warning_on_retry: true 551: continue_on_error: false ... 1067: go: downloading github.com/shopspring/decimal v1.3.1 1068: go: downloading golang.org/x/crypto v0.21.0 1069: go: downloading golang.org/x/text v0.14.0 1070: go: downloading github.com/subosito/gotenv v1.4.2 1071: go: downloading github.com/hashicorp/hcl v1.0.0 1072: go: downloading gopkg.in/ini.v1 v1.67.0 1073: go: downloading github.com/magiconair/properties v1.8.7 1074: go: downloading github.com/pelletier/go-toml/v2 v2.0.8 1075: go: downloading github.com/pkg/errors v0.9.1 ... 1079: helm-docs [flags] 1080: Flags: 1081: -b, --badge-style string badge style to use for charts (default "flat-square") 1082: -c, --chart-search-root string directory to search recursively within for charts (default ".") 1083: -g, --chart-to-generate strings List of charts that will have documentation generated. Comma separated, no space. Empty list - generate for all charts in chart-search-root 1084: -u, --document-dependency-values For charts with dependencies, include the dependency values in the chart values documentation 1085: -y, --documentation-strict-ignore-absent strings A comma separate values which are allowed not to be documented in strict mode (default [service.type,image.repository,image.tag]) 1086: -z, --documentation-strict-ignore-absent-regex strings A comma separate values which are allowed not to be documented in strict mode (default [.*service\.type,.*image\.repository,.*image\.tag]) 1087: -x, --documentation-strict-mode Fail the generation of docs if there are undocumented values 1088: -d, --dry-run don't actually render any markdown files just print to stdout passed 1089: -h, --help help for helm-docs 1090: -i, --ignore-file string The filename to use as an ignore file to exclude chart directories (default ".helmdocsignore") 1091: --ignore-non-descriptions ignore values without a comment, this values will not be included in the README 1092: -l, --log-level string Level of logs that should printed, one of (panic, fatal, error, warning, info, debug, trace) (default "info") ... 1280: if [ $EXIT_CODE -ne 0 ]; then \ 1281: echo "New changes in chart. Please run 'make generate_readme_charts' to update them." ; \ 1282: exit $EXIT_CODE ; \ 1283: fi ; \ 1284: exit $EXIT_CODE 1285: charts/selenium-grid/CONFIGURATION.md | 2 +- 1286: 1 file changed, 1 insertion(+), 1 deletion(-) 1287: New changes in chart. Please run 'make generate_readme_charts' to update them. 1288: make: *** [Makefile:88: lint_readme_charts] Error 1 1289: ##[error]Process completed with exit code 2. ... 1304: SERVICE_MESH: true 1305: pythonLocation: /opt/hostedtoolcache/Python/3.11.10/x64 1306: PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.11.10/x64/lib/pkgconfig 1307: Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.10/x64 1308: Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.10/x64 1309: Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.10/x64 1310: LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.11.10/x64/lib 1311: ##[endgroup] 1312: ##[error]Input required and not supplied: path ... 1410: [command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :" 1411: flag provided but not defined: -variables 1412: Usage: envsubst [options...] 1413: Options: 1414: -i Specify file input, otherwise use last argument as input file. 1415: If no input file is specified, read from stdin. 1416: -o Specify file output. If none is specified, write to stdout. 1417: -no-digit Do not replace variables starting with a digit. e.g. $1 and ${1} 1418: -no-unset Fail if a variable is not set. 1419: -no-empty Fail if a variable is set but empty. 1420: -fail-fast Fail on first error otherwise display all failures if restrictions are set. ... 1424: [command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :" 1425: flag provided but not defined: -variables 1426: Usage: envsubst [options...] 1427: Options: 1428: -i Specify file input, otherwise use last argument as input file. 1429: If no input file is specified, read from stdin. 1430: -o Specify file output. If none is specified, write to stdout. 1431: -no-digit Do not replace variables starting with a digit. e.g. $1 and ${1} 1432: -no-unset Fail if a variable is not set. 1433: -no-empty Fail if a variable is set but empty. 1434: -fail-fast Fail on first error otherwise display all failures if restrictions are set. ```

    ✨ CI feedback usage guide:
    The CI feedback tool (`/checks)` automatically triggers when a PR has a failed check. The tool analyzes the failed checks and provides several feedbacks: - Failed stage - Failed test name - Failure summary - Relevant error logs In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR: ``` /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}" ``` where `{repo_name}` is the name of the repository, `{run_number}` is the run number of the failed check, and `{job_number}` is the job number of the failed check. #### Configuration options - `enable_auto_checks_feedback` - if set to true, the tool will automatically provide feedback when a check is failed. Default is true. - `excluded_checks_list` - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list. - `enable_help_text` - if set to true, the tool will provide a help message with the feedback. Default is true. - `persistent_comment` - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true. - `final_update_message` - if `persistent_comment` is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true. See more information about the `checks` tool in the [docs](https://pr-agent-docs.codium.ai/tools/ci_feedback/).