Skip to content

Feat/new navigation #104

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

Merged
rmnbrd merged 7 commits into from
May 11, 2026
Merged

Feat/new navigation #104

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
3722d83
Add screenshots WIP
jul-dan Apr 15, 2026
2cd5cb8
Update screenshots WIP
jul-dan Apr 17, 2026
7488508
WIP update screenshots
jul-dan Apr 22, 2026
5aeea65
WIP update screenshots
jul-dan Apr 23, 2026
0cec92a
Update screenshots
jul-dan Apr 24, 2026
6415279
Update documentation content following the new navigation
jul-dan Apr 24, 2026
cdbf705
Update screenshots
jul-dan Apr 27, 2026
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
19 changes: 10 additions & 9 deletions docs/configuration/clusters.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ description: "Manage your Kubernetes clusters with Qovery"
To create a new cluster:

1. Open the [Qovery Console](https://console.qovery.com)
2. Navigate to the **Cluster** page in the left menu
2. Navigate to the **Clusters** tab
3. Click **Add Cluster**
4. Follow the provider-specific guide for your cloud platform:

Expand Down Expand Up @@ -197,13 +197,11 @@ Resumes a stopped cluster and redeploys all services.
Permanently removes your cluster. You have three deletion options:

1. **Default (Recommended)**: Complete cleanup

- Deletes all Qovery-managed resources
- Removes cloud provider infrastructure
- No residual costs

2. **Delete on cloud provider and Qovery configuration**: Manual database handling

- Deletes cluster from cloud provider
- Removes Qovery configuration
- Requires manual database cleanup
Expand Down Expand Up @@ -306,6 +304,7 @@ To use your own custom domain with wildcard TLS certificates, Qovery supports **
- Your Cloudflare account email

The Qovery team will configure the integration for you.

</Step>

<Step title="Verify DNS">
Expand Down Expand Up @@ -365,6 +364,7 @@ To use your own custom domain with wildcard TLS certificates, Qovery supports **
<Info>
The Hosted Zone ID is optional. If not provided, Qovery will auto-detect it.
</Info>

</Step>

<Step title="Contact Qovery Support">
Expand All @@ -377,6 +377,7 @@ To use your own custom domain with wildcard TLS certificates, Qovery supports **
- Your Hosted Zone ID (optional)

The Qovery team will configure the integration for you.

</Step>

<Step title="Verify DNS">
Expand All @@ -385,7 +386,8 @@ To use your own custom domain with wildcard TLS certificates, Qovery supports **
</Steps>

<Info>
This feature is currently in **Beta**. Both **Cloudflare** and **AWS Route53** are supported. Additional DNS providers will be added in future releases.
This feature is currently in **Beta**. Both **Cloudflare** and **AWS Route53**
are supported. Additional DNS providers will be added in future releases.
</Info>

## AWS Account Cleanup
Expand All @@ -399,11 +401,10 @@ If cluster deletion fails or leaves resources behind, you can manually clean up
Navigate to the [AWS Resource Groups & Tag Editor](https://console.aws.amazon.com/resource-groups/tag-editor)
</Step>

<Step title="Search for Qovery Resources">
1. Select **All supported resource types**
2. Add tag filter: `ClusterId` or `QoveryCluster`
3. Search for resources
</Step>
<Step title="Search for Qovery Resources">
1. Select **All supported resource types** 2. Add tag filter: `ClusterId` or
`QoveryCluster` 3. Search for resources
</Step>

<Step title="Review and Delete">
1. Review the list of tagged resources
Expand Down
Loading
Loading