Conversation
…tails
Document user-facing Console changes:
- clusters: AWS quota warning surfaced on the cluster overview and in the
service status tooltip ("Quota issue") when Karpenter cannot create nodes.
console#3000
- clusters: cluster Deployment History view (now generally available) and the
"Dry run" badge on dry-run deployments. console#2986 + console#2991
- organization/billing: a complete billing address is now required when adding
a card, with a VAT number required for EU countries and postal-code
validation. console#2994
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
qovery-doc-mintlify-proxy | f6c3657 | Sep 24 2026, 01:13 PM |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
2 issues found across 2 files
Confidence score: 4/5
- In
docs/configuration/clusters.mdx, the “Dry run” badge is documented without explaining what triggers or constitutes a dry run, which could leave users unsure how to interpret the status—confirm the trigger and define it in the sentence. - The new Deployments section in
docs/configuration/clusters.mdxoverlaps withdocs/configuration/deployment/history.mdx, risking duplicated or inconsistent guidance about tabs, logs, statuses, and cancellation—link to the existing page or consolidate the shared details.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="docs/configuration/clusters.mdx">
<violation number="1" location="docs/configuration/clusters.mdx:169">
P3: This new section overlaps with the existing Deployment History page (docs/configuration/deployment/history.mdx), which documents the same **Deployments** tab concept, log viewing, statuses, and cancel action. Link the new section to that page so readers can find the detailed coverage instead of the cluster section being the only reference.</violation>
<violation number="2" location="docs/configuration/clusters.mdx:173">
P2: This sentence documents a "Dry run" badge without defining what a dry run is. The PR description itself flags this: console PR #2991 "does not define what constitutes a dry run" and requests confirming the trigger before documenting. Per AGENTS.md ("Do not invent features... If not verifiable from these sources, do not write it"), either confirm the dry-run trigger (e.g., cluster create/update validation) from the console implementation, or state what triggers a dry run.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
|
|
||
| The cluster's **Deployments** view lists its past deployments, most recent first, each with its status and timestamp. Open a deployment to read its deployment logs. | ||
|
|
||
| Deployments that ran as a dry run are marked with a **Dry run** badge in the list. |
There was a problem hiding this comment.
P2: This sentence documents a "Dry run" badge without defining what a dry run is. The PR description itself flags this: console PR #2991 "does not define what constitutes a dry run" and requests confirming the trigger before documenting. Per AGENTS.md ("Do not invent features... If not verifiable from these sources, do not write it"), either confirm the dry-run trigger (e.g., cluster create/update validation) from the console implementation, or state what triggers a dry run.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/configuration/clusters.mdx, line 173:
<comment>This sentence documents a "Dry run" badge without defining what a dry run is. The PR description itself flags this: console PR #2991 "does not define what constitutes a dry run" and requests confirming the trigger before documenting. Per AGENTS.md ("Do not invent features... If not verifiable from these sources, do not write it"), either confirm the dry-run trigger (e.g., cluster create/update validation) from the console implementation, or state what triggers a dry run.</comment>
<file context>
@@ -157,6 +157,21 @@ Qovery tracks cluster health using two status categories:
+
+The cluster's **Deployments** view lists its past deployments, most recent first, each with its status and timestamp. Open a deployment to read its deployment logs.
+
+Deployments that ran as a dry run are marked with a **Dry run** badge in the list.
+
### Performing Actions on Clusters
</file context>
|
|
||
| Follow the suggested action (for example, requesting a quota increase in AWS) so Karpenter can resume creating nodes. | ||
|
|
||
| ### Deployment History |
There was a problem hiding this comment.
P3: This new section overlaps with the existing Deployment History page (docs/configuration/deployment/history.mdx), which documents the same Deployments tab concept, log viewing, statuses, and cancel action. Link the new section to that page so readers can find the detailed coverage instead of the cluster section being the only reference.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/configuration/clusters.mdx, line 169:
<comment>This new section overlaps with the existing Deployment History page (docs/configuration/deployment/history.mdx), which documents the same **Deployments** tab concept, log viewing, statuses, and cancel action. Link the new section to that page so readers can find the detailed coverage instead of the cluster section being the only reference.</comment>
<file context>
@@ -157,6 +157,21 @@ Qovery tracks cluster health using two status categories:
+
+Follow the suggested action (for example, requesting a quota increase in AWS) so Karpenter can resume creating nodes.
+
+### Deployment History
+
+The cluster's **Deployments** view lists its past deployments, most recent first, each with its status and timestamp. Open a deployment to read its deployment logs.
</file context>
|
Superseded by #199, which reworks this branch with a signed commit and addresses the review feedback here: the cluster Dry-run is now defined (verified from the console update dialog) and the Deployments section links to the existing Deployment History page. #199 also adds the new Blueprint configuration settings page (console#2965). |
This branch was successfully deployed
1 participant
Summary
Documents user-facing changes merged into
qovery/consolemainduring the analysis window (last 14 days, since2026-09-10). Changes already covered by recent PRs — AI provider tokens / AWS Bedrock (documented in #194) and certificate renewal failure alerts (#195) — are intentionally not duplicated.Documented changes
1. AWS quota warnings on clusters
When an AWS service quota is reached and Karpenter can no longer create new nodes, the Console now surfaces a quota warning: a callout on the cluster overview (quota name, impacted resource, message, suggested AWS action), and a Quota issue tooltip on the status indicator of services running on that cluster.
configuration/clusters.mdx(new "AWS Quota Warnings" subsection under Statuses)2. Cluster deployment history and dry-run badge
The cluster Deployments history view is now generally available (its feature flag was removed), listing past cluster deployments with status/timestamp and per-deployment logs. Deployments that ran as a dry run now show a Dry run badge.
configuration/clusters.mdx(new "Deployment History" section)3. Billing details validation
Adding a payment card — during organization onboarding or from Billing — now requires a complete billing address, a VAT number for EU billing countries (optional elsewhere), and validates supported EU/US postal-code formats.
configuration/organization.mdx(Billing section)Needs review
configuration/agent-tasks/, so I did not change those pages. Worth a review to see if the reorganized settings layout deserves a doc refresh.configuration/blueprints.mdxalready documents overrides, the preview/apply update flow, and outputs, so no change was made. Confirm whether the new per-service settings UI needs its own section.DOCS_AGENT_LAST_RUN_ATcould not be read or updated. I fell back to a 14-day analysis window and left the variable untouched, so the next run will re-analyze this window.🤖 Generated with Claude Code
Summary by cubic
Documents user-facing Console changes in the cluster and organization docs.
Written for commit f6c3657. Summary will update on new commits.