From a5bf5b93bdc51b990e7102cbda9d352b60ab0c03 Mon Sep 17 00:00:00 2001 From: jul-dan Date: Thu, 24 Sep 2026 14:01:14 +0000 Subject: [PATCH 1/2] docs(console): cluster deployments, AWS quota warnings, blueprint settings, billing details - clusters: document the cluster Deployments tab (history + per-deployment logs, "Dry run" badge) and AWS quota warnings on cluster status - blueprints: document the "Blueprint configuration" settings page for reconfiguring an existing blueprint service - organization: note the required billing details (address, VAT for EU) at organization creation / when adding a card Co-Authored-By: Claude Opus 4.8 --- docs/configuration/blueprints.mdx | 10 ++++++++++ docs/configuration/clusters.mdx | 23 ++++++++++++++++++++++- docs/configuration/organization.mdx | 4 ++++ 3 files changed, 36 insertions(+), 1 deletion(-) diff --git a/docs/configuration/blueprints.mdx b/docs/configuration/blueprints.mdx index e3cd9cdc..c8593e95 100644 --- a/docs/configuration/blueprints.mdx +++ b/docs/configuration/blueprints.mdx @@ -196,6 +196,16 @@ The engine block defines how the resource is provisioned. Which settings you can For Helm blueprints, engine version, credentials, and state backend do not apply — the chart and its version are defined by the blueprint, and the resources block is ignored because the chart declares its own. +## Editing a Blueprint Service + +After a blueprint service is created, you can change the inputs it was provisioned with from its **Blueprint configuration** settings page. Open the blueprint service, go to its **Settings**, and select **Blueprint configuration** to review and edit the variables and any overridable engine settings the blueprint exposes (see [Variables & Engine Reference](#variables--engine-reference)). Secret values are handled without exposing the stored secret, and the **Overrides** section is collapsed by default. + +Save your changes, then redeploy the service to apply them. + + +The **Blueprint configuration** page is only available for blueprint-backed services. For a blueprint service, source, build, and deployment-restriction settings are not shown, since they are managed by the blueprint. + + ## Updating a Blueprint When Qovery maintains a newer version of a blueprint's template, the linked service surfaces an available update. Qovery compares your current tag to the latest catalog tag and reports exactly what changed: diff --git a/docs/configuration/clusters.mdx b/docs/configuration/clusters.mdx index 1ca65761..92d8bbd6 100644 --- a/docs/configuration/clusters.mdx +++ b/docs/configuration/clusters.mdx @@ -144,7 +144,7 @@ Qovery tracks cluster health using two status categories: | Status | Description | | -------------------------------------------------------------------------------- | ----------------------------------------- | | **Running** | Cluster is healthy and operational | -| **Warning** | Minor issues detected, requires attention | +| **Warning** | Minor issues detected, requires attention — for example an [AWS quota warning](#aws-quota-warnings) | | **Error** | Critical issues, intervention required | | **Status unavailable** | Cluster unreachable or offline | @@ -157,6 +157,17 @@ 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 Karpenter cannot create new nodes because an AWS service quota has been reached, the cluster status becomes **Warning** and a yellow callout is shown on the cluster overview. The callout reports: + +- the **quota name** (or code) that was hit, +- the **impacted resource**, +- a **message** describing the issue, +- a **suggested action** — typically requesting an AWS quota increase, then retrying or waiting for the cluster to scale again. + +While the warning is active, the cluster-status indicator shown next to your services (on the service overview) reads **Quota issue** instead of the generic warning label. The warning clears automatically once new nodes can be scheduled again; it may remain visible for a short time after the last occurrence. + ### Performing Actions on Clusters Available cluster operations and their cloud provider compatibility: @@ -240,6 +251,16 @@ Permanently removes your cluster. You have three deletion options: securely and never commit to version control. +## Deployments + +Each cluster has its own **Deployments** tab that lists its past deployments, most recent first — each with its status, timestamp, duration, and who or what triggered it. Select a deployment to open its logs. This is the same [deployment history](/configuration/deployment/history) available on environments and services, applied to the cluster itself. + +A cluster deployment run with the **Dry-run** option enabled — a checkbox in the cluster update dialog that previews the changes without applying them — is tagged with a **Dry run** badge in the list. + + +Bookmarked links to the previous cluster logs URL are automatically redirected to the **Deployments** tab. + + ## Logs Access cluster logs for troubleshooting and monitoring: diff --git a/docs/configuration/organization.mdx b/docs/configuration/organization.mdx index fc069e59..809325b1 100644 --- a/docs/configuration/organization.mdx +++ b/docs/configuration/organization.mdx @@ -84,6 +84,10 @@ Manage your organization's billing and subscription: - **Subscription**: Upgrade or downgrade your plan - **Usage**: Monitor resource usage and costs + +When you create an organization or add a payment card, you must provide your billing details, including a billing address. A **VAT number** is required for billing addresses in EU countries and optional elsewhere. Postal codes are validated against the expected format for the selected country. + + For pricing details, visit the [pricing page](https://www.qovery.com/pricing). ## Organization Admin Settings From 5de29dab763a8db7404408572f48a1035618e824 Mon Sep 17 00:00:00 2001 From: jul-dan Date: Thu, 24 Sep 2026 14:59:49 +0000 Subject: [PATCH 2/2] docs(agent-tasks): document agent task model selection Agent tasks now let you pick the model the agent runs on. Once a provider token is selected, a Model dropdown lists the models available to that token (for AWS Bedrock, filtered by the token's AWS region); the first is selected by default, and the choice can be changed later from Settings > AI configuration. Source: qovery/console#3005 Co-Authored-By: Claude Opus 4.8 --- docs/configuration/agent-tasks/overview.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/configuration/agent-tasks/overview.mdx b/docs/configuration/agent-tasks/overview.mdx index 8f4aa023..10fb618a 100644 --- a/docs/configuration/agent-tasks/overview.mdx +++ b/docs/configuration/agent-tasks/overview.mdx @@ -24,8 +24,10 @@ Agent Tasks are one-time or scheduled jobs delegated to AI agents, running on yo Connect a Qovery service, a Git repository, or both, for the agent to load as context. A Qovery service's linked Git repository is included automatically, no need to add it separately, connect a repository on its own only when it isn't tied to a Qovery service. - + Pick **Claude** (Anthropic) or **AWS Bedrock**, then select an existing token or create a new one on the fly. A token created here is saved and can be reused by any other agent task in the organization, no need to re-enter credentials each time. Tokens can also be managed centrally from **Organization Settings > Agent > Token**. + + Once a token is selected, pick the **Model** the agent runs on from the list of models available to that token. The first available model is selected by default. For AWS Bedrock, the models offered depend on the token's AWS region. You can change the model later from the agent task's **Settings > AI configuration**. If you added a Qovery service as Context in the previous step, Qovery's own MCP server is created and selected automatically: organization-scoped, read-only, backed by a Viewer API token. No URL, header, or token to configure. This is also preconfigured for the Incident Analyzer (incident.io and Honeybadger) and Build & deployment optimizer templates.