Skip to content

docs(console): cluster quota warnings, deployment history, and billing details #198

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.

Sign up for GitHub

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

Closed
jul-dan wants to merge 1 commit into from
Closed

docs(console): cluster quota warnings, deployment history, and billing details #198

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/configuration/clusters.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,6 +157,21 @@ Qovery tracks cluster health using two status categories:
| **Last Deployment Failed** | The most recent deployment encountered errors |
| **Last Deployment Succeeded** | The most recent deployment completed successfully |

#### AWS Quota Warnings

On AWS clusters, when an AWS service quota is reached and Karpenter can no longer create new nodes, Qovery surfaces a quota warning:

- The **cluster overview** displays a warning callout with the quota name, the impacted resource, the reported message, and the suggested action to run in your AWS account.
- While the warning is active, the cluster-status indicator of services running on the cluster reads **Quota issue** in its tooltip instead of the generic **Warning**.

Follow the suggested action (for example, requesting a quota increase in AWS) so Karpenter can resume creating nodes.

### Deployment History

@cubic-dev-ai cubic-dev-ai Bot Sep 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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>


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.

@cubic-dev-ai cubic-dev-ai Bot Sep 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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>


### Performing Actions on Clusters

Available cluster operations and their cloud provider compatibility:
Expand Down
4 changes: 4 additions & 0 deletions docs/configuration/organization.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,10 @@ Manage your organization's billing and subscription:
- **Subscription**: Upgrade or downgrade your plan
- **Usage**: Monitor resource usage and costs

<Info>
When you add a payment card — during organization onboarding or later from **Billing** — you must enter a complete billing address. A **VAT number** is required for billing countries in the EU and optional elsewhere. Postal codes are validated against the supported EU and US formats.
</Info>

For pricing details, visit the [pricing page](https://www.qovery.com/pricing).

## Organization Admin Settings
Expand Down
Loading