Add helm charts for api-portal along with version bump for other portals - #3158
Open
DinithHerath wants to merge 8 commits into
Open
Add helm charts for api-portal along with version bump for other portals#3158DinithHerath wants to merge 8 commits into
DinithHerath wants to merge 8 commits into
Conversation
…along with version bumps
…he naming convention
DinithHerath
requested review from
AnuGayan,
Arshardh,
CrowleyRajapakse,
HeshanSudarshana,
HiranyaKavishani,
Krishanx92,
PasanT9,
RakhithaRR,
Tharsanan1,
Thushani-Jayasekera,
VirajSalaka,
ashera96,
chamilaadhi,
dushaniw,
hisanhunais,
malinthaprasan,
pubudu538,
renuka-fernando,
senthuran16,
tgtshanika,
tharikaGitHub,
tharindu1st and
thivindu
as code owners
August 5, 2026 18:31
DinithHerath
requested review from
Induwara04,
Piumal1999 and
lasanthaS
as code owners
August 5, 2026 18:31
Contributor
|
Warning Review limit reached
Next review available in: 6 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThe change migrates Helm releases and chart configuration from Developer Portal to API Portal. It updates chart versions, resource naming, secrets, validation, API Portal UI settings, Platform API contracts, upload limits, and deployment configuration guidance. ChangesAPI Portal release packaging
Estimated code review effort: 4 (Complex) | ~60 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@kubernetes/helm/ai-workspace-ui-helm-chart/templates/configmap.yaml`:
- Around line 59-66: Update the authorization validation around $authz in the
Helm template to add a render-time guard when the local Platform API is enabled,
requiring config.auth.authorization.mode to match
platform-api.config.auth.authorization.mode. Preserve the existing scope/role
validation, and document the required matching mode for deployments using an
external Platform API.
In `@kubernetes/helm/api-portal-helm-chart/Chart.yaml`:
- Line 2: Update the description in Chart.yaml to replace every occurrence of
“Developer Portal” with “API Portal” on the referenced description lines, while
preserving the rest of the Helm metadata unchanged.
In `@kubernetes/helm/api-portal-ui-helm-chart/templates/configmap.yaml`:
- Line 131: Update the fail message in the template validation to reference the
actual values path, using config.organization.handle is required instead of
apiPortal.config.organization.handle. Keep the validation behavior unchanged.
In `@kubernetes/helm/api-portal-ui-helm-chart/templates/pdb.yaml`:
- Around line 4-8: Update the PDB validation and emitted spec around the
minAvailable and maxUnavailable fields to test whether each key is present, not
whether its value is truthy, preserving explicit zero values. Ensure validation
still rejects both fields when set and rejects neither when absent, and render
the selected field even when its value is 0.
In `@kubernetes/helm/platform-api-helm-chart/values.yaml`:
- Around line 284-297: The chart needs an upgrade path for Secrets created with
the previous generic key names. Update the secrets key handling around the
values.keys mapping so existing old-key Secrets remain readable during rollout,
either by documenting a migration procedure or by supporting
dual-write/dual-read of both old and new names; ensure secretKeyRef lookups and
the Secret volume entries for encryption, database, webhook, JWT, and admin
credentials continue working with legacy Secrets.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 76cd9a2e-eaf4-4bbe-a28b-182f6baec3e9
📒 Files selected for processing (39)
.github/workflows/api-portal-helm-release.yml.github/workflows/api-portal-ui-helm-release.ymlkubernetes/helm/ai-workspace-helm-chart/Chart.yamlkubernetes/helm/ai-workspace-helm-chart/generate-secrets.shkubernetes/helm/ai-workspace-helm-chart/templates/NOTES.txtkubernetes/helm/ai-workspace-helm-chart/templates/validation.yamlkubernetes/helm/ai-workspace-ui-helm-chart/Chart.yamlkubernetes/helm/ai-workspace-ui-helm-chart/templates/_helpers.tplkubernetes/helm/ai-workspace-ui-helm-chart/templates/configmap.yamlkubernetes/helm/ai-workspace-ui-helm-chart/values.yamlkubernetes/helm/api-portal-helm-chart/.helmignorekubernetes/helm/api-portal-helm-chart/Chart.yamlkubernetes/helm/api-portal-helm-chart/generate-secrets.shkubernetes/helm/api-portal-helm-chart/templates/NOTES.txtkubernetes/helm/api-portal-helm-chart/templates/serviceaccount.yamlkubernetes/helm/api-portal-helm-chart/templates/validation.yamlkubernetes/helm/api-portal-helm-chart/values-local.yamlkubernetes/helm/api-portal-helm-chart/values.yamlkubernetes/helm/api-portal-ui-helm-chart/.helmignorekubernetes/helm/api-portal-ui-helm-chart/Chart.yamlkubernetes/helm/api-portal-ui-helm-chart/templates/_helpers.tplkubernetes/helm/api-portal-ui-helm-chart/templates/certificate.yamlkubernetes/helm/api-portal-ui-helm-chart/templates/configmap.yamlkubernetes/helm/api-portal-ui-helm-chart/templates/deployment.yamlkubernetes/helm/api-portal-ui-helm-chart/templates/hpa.yamlkubernetes/helm/api-portal-ui-helm-chart/templates/issuer.yamlkubernetes/helm/api-portal-ui-helm-chart/templates/pdb.yamlkubernetes/helm/api-portal-ui-helm-chart/templates/pvc.yamlkubernetes/helm/api-portal-ui-helm-chart/templates/service.yamlkubernetes/helm/api-portal-ui-helm-chart/values-local.yamlkubernetes/helm/api-portal-ui-helm-chart/values.yamlkubernetes/helm/developer-portal-ui-helm-chart/templates/pdb.yamlkubernetes/helm/gateway-helm-chart/values.yamlkubernetes/helm/platform-api-helm-chart/Chart.yamlkubernetes/helm/platform-api-helm-chart/templates/_helpers.tplkubernetes/helm/platform-api-helm-chart/templates/configmap.yamlkubernetes/helm/platform-api-helm-chart/values.yamlplatform-api/config/config.goportals/api-portal/configs/config-template.toml
💤 Files with no reviewable changes (1)
- kubernetes/helm/developer-portal-ui-helm-chart/templates/pdb.yaml
- Fail render when platform-api and ai-workspace-ui authorization modes mismatch, since the UI only mirrors what the Platform API enforces - Fix leftover "Developer Portal" text in api-portal Chart.yaml description - Fix values path in api-portal-ui's organization.handle validation error - Preserve explicit minAvailable/maxUnavailable: 0 in the PDB template, which truthiness checks were treating as unset - Document the upgrade path for platform-api's APIP_CP_* secret key rename
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the AI Workspace Helm charts and related GitHub Actions workflows to rename the "Developer Portal" to "API Portal" throughout the codebase. It also standardizes secret and environment variable naming, updates component versions to 1.0.0, and improves documentation and configuration consistency.
Portal Renaming and Workflow Updates:
Secret and Environment Variable Standardization:
generate-secrets.shto use a consistentAPIP_*prefix and clarified their usage in documentation. Deprecated and replaced old variable names. [1] [2]Helm Chart and Component Version Updates:
1.0.0and updated theplatform-apidependency to0.16.0for compatibility and stability. [1] [2] [3]Documentation and User Guidance Improvements:
Validation and Error Messaging:
These changes ensure consistent naming, improved maintainability, and a clearer installation and configuration experience for users.