-
Notifications
You must be signed in to change notification settings - Fork 53
v0.3.7 patch release #369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.3.7 patch release #369
Changes from all commits
b543ba0
2899305
1622822
5458627
9ad5316
ed497f7
31bdbd1
091d979
4469547
24d5d5d
6abed8e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -91,6 +91,22 @@ const accessReviews = useAccessReviews(resourceAttributes); | |||||
| const canRead = accessReviews[0]; | ||||||
| ``` | ||||||
|
|
||||||
| ### 5. Configuration | ||||||
|
|
||||||
| The plugin supports configurable Topology andPrometheus metrics for gateway traffic monitoring. This allows the console to work with different Gateway API implementations (OpenShift 4.19+, OSSM, etc.). | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Minor typo: missing space. There's a missing space between "and" and "Prometheus". 📝 Suggested fix-The plugin supports configurable Topology andPrometheus metrics for gateway traffic monitoring. This allows the console to work with different Gateway API implementations (OpenShift 4.19+, OSSM, etc.).
+The plugin supports configurable Topology and Prometheus metrics for gateway traffic monitoring. This allows the console to work with different Gateway API implementations (OpenShift 4.19+, OSSM, etc.).📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||
|
|
||||||
| **Configuration is managed through:** | ||||||
| - `src/utils/configLoader.ts` - Configuration schema and defaults | ||||||
| - `src/utils/metricsQueries.ts` - Query utilities | ||||||
| - Environment variables in deployment manifests | ||||||
|
|
||||||
| **Example ENV Configuration:** | ||||||
| ```yaml | ||||||
| TOPOLOGY_CONFIGMAP_NAME: "topology" | ||||||
| TOPOLOGY_CONFIGMAP_NAMESPACE: "kuadrant-system" | ||||||
| METRICS_WORKLOAD_SUFFIX: "-openshift-default" | ||||||
| ``` | ||||||
|
|
||||||
| ## Key Components | ||||||
|
|
||||||
| - **KuadrantOverviewPage**: Main dashboard with gateway health status | ||||||
|
|
||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: Kuadrant/kuadrant-console-plugin
Length of output: 110
🏁 Script executed:
cat -n .github/workflows/dev-build.yaml | head -60Repository: Kuadrant/kuadrant-console-plugin
Length of output: 2260
🌐 Web query:
docker/login-action@v2 GitHub Actions compatibility current runners 2024 2025💡 Result:
docker/login-action@v2 is compatible with current GitHub Actions hosted runners as of April 2026, but it is outdated and runs on Node.js 16, which has been deprecated since 2023-2024. Current runners (v2.33x+) support Node 20 (default until June 2026) and Node 24. Node 16 actions like v2 will continue to run with opt-out env vars (ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true), but may fail post-September 2026 when Node 20 is fully removed. Official docs and examples use v4.1.0 (Node 24, requires runner v2.327.1+). Upgrade to v3+ (Node 20, runner v2.308+) or v4+ for full compatibility without warnings or future breakage. In 2024-early 2025, v2 worked fine; by 2025-2026, Dependabot recommends upgrades in projects like actions/runner.
Citations:
🌐 Web query:
actionlint docker/login-action version compatibility warnings💡 Result:
No specific version compatibility warnings or issues were found between actionlint and docker/login-action. Actionlint performs comprehensive static analysis on GitHub Actions workflows, including checks for popular actions like docker/login-action such as input validation at 'with:', outdated versions at 'uses:', and general syntax/type checks. Docker/login-action is actively maintained with recent releases up to v4.1.0 (as of 2026-04-02), and major version bumps (e.g., v2 to v3, v3 to v4) are handled via Dependabot without actionlint-related complaints in searched issues/PRs. Use the latest versions: actionlint v1.7.12+ and docker/login-action@v4 for optimal compatibility. To verify workflows, run actionlint locally or in CI.
Citations:
Guard this login step and bump
docker/login-actionto v3 or later.This login step (line 28) runs unconditionally whilst the build/push step (line 46) is guarded by
if: github.repository_owner == 'kuadrant'. For non-Kuadrant forks triggered viaworkflow_dispatch, the login step will attempt to execute before being skipped, causing failure due to missing registry credentials. Additionally,docker/login-action@v2runs on Node.js 16, which is deprecated. Upgrade to v3 (Node 20, supported through June 2026) or v4 for forward compatibility.Suggested patch
🧰 Tools
🪛 actionlint (1.7.12)
[error] 28-28: the runner of "docker/login-action@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue
(action)
🤖 Prompt for AI Agents