Skip to content

Commit

Permalink
fix links (#507)
Browse files Browse the repository at this point in the history
* fix links

* add helm network clone specifity
  • Loading branch information
jul-dan authored Jan 15, 2025
1 parent 0cf1b44 commit 42af275
Show file tree
Hide file tree
Showing 2 changed files with 25 additions and 7 deletions.
17 changes: 13 additions & 4 deletions website/docs/using-qovery/configuration/helm.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
last_modified_on: "2024-09-25"
last_modified_on: "2025-01-15"
title: "Helm"
description: "Learn how to configure your Helm on Qovery"
---
Expand Down Expand Up @@ -267,9 +267,18 @@ You can edit the existing service/port or declare new ones by specifying:
- Port Name: it is the name assigned to the port. When multiple ports are exposed publicly, its value is used to route the traffic to the right port based on the called subdomain (which will contain the port name value). Since each port is exposed on the port 443, having a different subdomain is the only way to have multiple ports exposed over the internet. If not set, the default value is `p<portNumber>` (see [Qovery Provided Domain section](#qovery-provided-domains) for more information)

<Alert type="info">

This setup is not copied when the helm chart is cloned (via a [manual clone][docs.using-qovery.configuration.environment#clone-environment] or the [preview environment feature][docs.using-qovery.configuration.environment#preview-environment])


When cloning a Helm chart (via a [manual clone][docs.using-qovery.configuration.environment#clone-environment] or the [preview environment feature][docs.using-qovery.configuration.environment#preview-environment]), the network setup copying behavior depends on the service name format:

* The network setup will be copied if the service name is generic (without any service identifier)
* The network setup will not be copied if the service name contains a specific service ID

| Service Name | Format | Clone Behavior |
|--------------|--------|------------------|
| `grafana-front` | Generic name | ✅ Network setup is copied |
| `helm-z1243144-grafana-front` | Contains service ID | ❌ Network setup is not copied |

**Note**: Service IDs are unique identifiers (like `z1243144`) that are embedded within the service name.
</Alert>

#### Important Informations
Expand Down
15 changes: 12 additions & 3 deletions website/docs/using-qovery/configuration/helm.md.erb
Original file line number Diff line number Diff line change
Expand Up @@ -255,9 +255,18 @@ You can edit the existing service/port or declare new ones by specifying:
- Port Name: it is the name assigned to the port. When multiple ports are exposed publicly, its value is used to route the traffic to the right port based on the called subdomain (which will contain the port name value). Since each port is exposed on the port 443, having a different subdomain is the only way to have multiple ports exposed over the internet. If not set, the default value is `p<portNumber>` (see [Qovery Provided Domain section](#qovery-provided-domains) for more information)

<Alert type="info">

This setup is not copied when the helm chart is cloned (via a [manual clone][docs.using-qovery.configuration.environment#clone-environment] or the [preview environment feature][docs.using-qovery.configuration.environment#preview-environment])


When cloning a Helm chart (via a [manual clone][docs.using-qovery.configuration.environment#clone-environment] or the [preview environment feature][docs.using-qovery.configuration.environment#preview-environment]), the network setup copying behavior depends on the service name format:

* The network setup will be copied if the service name is generic (without any service identifier)
* The network setup will not be copied if the service name contains a specific service ID

| Service Name | Format | Clone Behavior |
|--------------|--------|------------------|
| `grafana-front` | Generic name | ✅ Network setup is copied |
| `helm-z1243144-grafana-front` | Contains service ID | ❌ Network setup is not copied |

**Note**: Service IDs are unique identifiers (like `z1243144`) that are embedded within the service name.
</Alert>

#### Important Informations
Expand Down

0 comments on commit 42af275

Please sign in to comment.