Skip to content

chore: upgrade api7 and gateway to v3.9.10#280

Merged
nic-6443 merged 1 commit intomainfrom
chore/upgrade-3.9.10
Apr 22, 2026
Merged

chore: upgrade api7 and gateway to v3.9.10#280
nic-6443 merged 1 commit intomainfrom
chore/upgrade-3.9.10

Conversation

@jarvis9443
Copy link
Copy Markdown
Contributor

@jarvis9443 jarvis9443 commented Apr 22, 2026

Changes

Version bumps

  • api7 chart: 0.17.51 → 0.17.52, appVersion 3.9.9 → 3.9.10
  • gateway chart: 0.2.60 → 0.2.61, appVersion 3.9.9 → 3.9.10
  • dashboard/dp_manager/developer_portal/file_server image tags: v3.9.9 → v3.9.10
  • gateway image tag: 3.9.9 → 3.9.10

Structural changes

  • Added telemetry section to dashboard_configuration in api7 values.yaml (from CP helm PR — enables CP-managed telemetry config pushed to DP via heartbeat)

Summary by CodeRabbit

  • Chores

    • Updated Helm charts to use application version 3.9.10 (API7 chart v0.17.52, Gateway chart v0.2.61)
    • Updated all container image tags to v3.9.10
  • New Features

    • Added dashboard telemetry configuration options with customizable settings for interval, compression level, and metrics size

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 22, 2026

📝 Walkthrough

Walkthrough

Bumped Helm chart versions and application image tags from 3.9.9 to 3.9.10 across api7 and gateway charts. Added new telemetry configuration section to api7 dashboard settings with default parameters for metrics collection.

Changes

Cohort / File(s) Summary
Chart Metadata Updates
charts/api7/Chart.yaml, charts/gateway/Chart.yaml
Incremented chart versions (api7: 0.17.51 → 0.17.52, gateway: 0.2.60 → 0.2.61) and appVersion fields (both 3.9.9 → 3.9.10).
API7 Chart Configuration
charts/api7/values.yaml, charts/api7/README.md
Updated Docker image tags from v3.9.9 to v3.9.10 for dashboard, developer_portal, dp_manager, and file_server components. Added new dashboard_configuration.telemetry section with enable, interval, max_metrics_size, metrics_batch_size, and compression_level settings.
Gateway Chart Configuration
charts/gateway/values.yaml, charts/gateway/README.md
Updated API7 Gateway image tag from 3.9.9 to 3.9.10 in both configuration and documentation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

Suggested reviewers

  • nic-6443
🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
E2e Test Quality Review ❓ Inconclusive PR contains only Helm chart configuration changes with no test files or functional implementation code to review against the custom check criteria. Confirm whether this check should apply to infrastructure-only PRs or if separate integration/deployment tests exist for this version upgrade.
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically summarizes the main changes: upgrading both api7 and gateway components to v3.9.10, which directly aligns with all version bumps and configuration updates across the changeset.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Security Check ✅ Passed PR contains only version bumps and telemetry config with non-sensitive parameters; no credentials, API keys, or tokens exposed.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/upgrade-3.9.10

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
charts/api7/README.md (1)

100-104: Add descriptions for new telemetry values in the table.

Line 100–104 currently introduce new keys with empty descriptions, which makes safe tuning harder during upgrades.

📘 Suggested README table improvement
-| dashboard_configuration.telemetry.compression_level | int | `-1` |  |
-| dashboard_configuration.telemetry.enable | bool | `true` |  |
-| dashboard_configuration.telemetry.interval | int | `15` |  |
-| dashboard_configuration.telemetry.max_metrics_size | int | `33554432` |  |
-| dashboard_configuration.telemetry.metrics_batch_size | int | `4194304` |  |
+| dashboard_configuration.telemetry.compression_level | int | `-1` | gzip compression level (`-1` default, `0-9` valid levels) |
+| dashboard_configuration.telemetry.enable | bool | `true` | Enable telemetry reporting to control plane |
+| dashboard_configuration.telemetry.interval | int | `15` | Report interval in seconds |
+| dashboard_configuration.telemetry.max_metrics_size | int | `33554432` | Max telemetry payload size in bytes before truncation |
+| dashboard_configuration.telemetry.metrics_batch_size | int | `4194304` | Batch size in bytes before compression |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@charts/api7/README.md` around lines 100 - 104, The telemetry table rows for
dashboard_configuration.telemetry (keys: compression_level, enable, interval,
max_metrics_size, metrics_batch_size) lack descriptions; update the README table
by adding concise descriptions for each key explaining purpose, accepted
values/ranges, defaults and guidance for safe tuning during upgrades (e.g.,
compression_level: -1=no compression or 0-9 levels; enable: toggle telemetry
collection; interval: seconds between reports; max_metrics_size: max payload
bytes; metrics_batch_size: max bytes per send), and include any
upgrade/compatibility notes or recommended safe defaults.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@charts/api7/README.md`:
- Around line 100-104: The telemetry table rows for
dashboard_configuration.telemetry (keys: compression_level, enable, interval,
max_metrics_size, metrics_batch_size) lack descriptions; update the README table
by adding concise descriptions for each key explaining purpose, accepted
values/ranges, defaults and guidance for safe tuning during upgrades (e.g.,
compression_level: -1=no compression or 0-9 levels; enable: toggle telemetry
collection; interval: seconds between reports; max_metrics_size: max payload
bytes; metrics_batch_size: max bytes per send), and include any
upgrade/compatibility notes or recommended safe defaults.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 432a60af-5d73-464c-b965-78b2c0b7d5e0

📥 Commits

Reviewing files that changed from the base of the PR and between 5d8341d and 946729a.

📒 Files selected for processing (6)
  • charts/api7/Chart.yaml
  • charts/api7/README.md
  • charts/api7/values.yaml
  • charts/gateway/Chart.yaml
  • charts/gateway/README.md
  • charts/gateway/values.yaml

@nic-6443 nic-6443 merged commit 99145a6 into main Apr 22, 2026
3 of 4 checks passed
@nic-6443 nic-6443 deleted the chore/upgrade-3.9.10 branch April 22, 2026 04:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants