| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Docker: Support Google Chrome images for linux/arm64 (#3187) * Docker: Support Google Chrome images for linux/arm64 Google Chrome (google-chrome-stable) is now published for Linux/ARM64 in the APT stable channel starting from v150. Build and publish the Chrome Node/Standalone images as multi-arch instead of AMD64 only. - NodeChrome: drop the hardcoded --platform=linux/amd64 in FROM - Makefile: build/tag/test Chrome and Standalone Chrome for $(PLATFORMS) - Add CHROME_PLATFORMS key to the browser matrix so older Chrome versions keep building for linux/amd64 only - Build dev/beta Chrome images for linux/amd64,linux/arm64 - Bump Chrome/Edge/CfT/Firefox versions in the build matrices - README: update the browser/arch support tables and notes Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Makefile: Align exporter builder stage Go version in update_go The update_go target bumped the Go toolchain for both in-repo modules but only realigned the .keda-external-scaler Dockerfile base image. Hub and Router build the .monitoring/exporter module in their exporter-builder stage, so they drifted from the module Go version. - Add GO_DOCKERFILES listing the Dockerfiles with a golang: builder stage and loop the base image alignment over it - Match golang:latest as well as pinned versions so an unpinned base gets pinned on the first run - Pin Hub/Router exporter-builder to golang:1.26, matching go 1.26.5 in the modules and the external scaler base - Dependency bumps from running the target: grpc v1.83.0, genproto rpc, otel v1.44.0 in .keda-external-scaler Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Docker: Install Chromium driver for Chrome images on linux/arm64 Google does not publish a ChromeDriver build for Linux/ARM64, Chrome for Testing only ships linux64 in every channel and the arm64 Chrome deb does not contain a driver, so the linux-aarch64 CfT URL always returned 404. On non-amd64, install the Debian chromium-driver package of the same major version instead, built from the same Chromium source and archived per version at https://github.com/NDViet/chromium-stable: - Resolve CHROMIUM_PACKAGE_VERSION for the Chrome major from the archive browser-matrix.yml, and fail with a clear message when the major is not released yet instead of installing a mismatched driver - Extract /usr/bin/chromedriver from the package, the amd64 CfT flow and the resulting chromedriver-<version> layout are unchanged - Install libdouble-conversion3 and libminizip1t64, the driver links against them and Google Chrome does not pull them in - Upgrade libc6 from Debian only when the driver refuses to start, the package requires libc6 >= 2.42 while the base image ships 2.39 - README: note where the ARM64 driver comes from Verified on linux/arm64 with node-chrome and standalone-chrome images: Chrome 151.0.7922.71 driven by ChromeDriver 151.0.7922.47, session created through the Grid and page title read back. The amd64 image still installs the CfT driver 151.0.7922.71 on the unchanged Ubuntu glibc. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * [ci] Report Chrome and ChromeDriver arm64 versions in release notes The Chrome row was hardcoded to "x" for arm64 and the arm64 ChromeDriver cell reported the driver from the node-chromium image, which no longer matches what node-chrome ships on arm64. - Query node-chrome with --platform linux/arm64 for both versions, the same way the Firefox arm64 version is collected - Drop CHROMIUMDRIVER_VERSION, the arm64 ChromeDriver cell was its only reference - Chrome for Testing and Edge stay "x", they remain AMD64 only Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> | 1 个月前 | |
Docker: Grid endpoint /metrics for exporter or K8s ServiceMonitor (#3135) Signed-off-by: Viet Nguyen Duc <nguyenducviet4496@gmail.com> | 3 个月前 | |
Docker: Update dependencies before building exporter Signed-off-by: Viet Nguyen Duc <nguyenducviet4496@gmail.com> | 3 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 个月前 | ||
| 3 个月前 | ||
| 3 个月前 |