Skip to content

Chore: remove sso documentation and deprecated advanced settings #535

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Chore: remove sso documentation and deprecated advanced settings #535

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0815d90
chore: removed admin group reference
acarranoqovery Mar 13, 2025
3c75f10
chore: removed SSO doc and deprecated advanced settings
acarranoqovery Mar 13, 2025
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
7 changes: 3 additions & 4 deletions website/docs/using-qovery/configuration/cluster-advanced-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
last_modified_on: "2025-02-17"
last_modified_on: "2025-03-13"
title: "Cluster Advanced Settings"
description: "Learn how to set advanced settings on your infrastructure with Qovery"
---
Expand Down Expand Up @@ -364,13 +364,13 @@ Once enabled, you can update the advanced setting [resources.override.limit.ram_

| Type | Description | Default Value |
|---------|-----------------------------------------------------------------------------|---------------|
| boolean | Enable SSO sync allowing IAM users to connect to cluster using SSO. [Setup SSO support for your cluster][guides.tutorial.how-to-activate-sso-to-connect-to-your-eks-cluster]. <br />⚠️ [`aws.iam.sso_role_arn`](#awsiamsso_role_arn) should be set. | `false` |
| boolean | Deprecated - Enable SSO sync allowing IAM users to connect to cluster using SSO. <br />⚠️ [`aws.iam.sso_role_arn`](#awsiamsso_role_arn) should be set. | `false` |

#### aws.iam.sso_role_arn ![](/img/advanced_settings/aws.svg)

| Type | Description | Default Value |
|---------|-----------------------------------------------------------------------------|---------------|
| string | Allows you to specify the SSO role ARN to be used to connect to your cluster. [Setup SSO support for your cluster][guides.tutorial.how-to-activate-sso-to-connect-to-your-eks-cluster] | `""` |
| string | Deprecated - Allows you to specify the SSO role ARN to be used to connect to your cluster. | `""` |


## Object storage
Expand Down Expand Up @@ -452,4 +452,3 @@ Why? Dockerhub has a [rate limit system by IP](https://docs.docker.com/docker-hu
[docs.using-qovery.configuration.advanced-settings#resources]: /docs/using-qovery/configuration/advanced-settings/#resources
[docs.using-qovery.configuration.organization.container-registry]: /docs/using-qovery/configuration/organization/container-registry/
[docs.using-qovery.deployment.image-mirroring]: /docs/using-qovery/deployment/image-mirroring/
[guides.tutorial.how-to-activate-sso-to-connect-to-your-eks-cluster]: /guides/tutorial/how-to-activate-sso-to-connect-to-your-eks-cluster/
4 changes: 2 additions & 2 deletions website/docs/using-qovery/configuration/cluster-advanced-settings.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -355,13 +355,13 @@ Once enabled, you can update the advanced setting [resources.override.limit.ram_

| Type | Description | Default Value |
|---------|-----------------------------------------------------------------------------|---------------|
| boolean | Enable SSO sync allowing IAM users to connect to cluster using SSO. [Setup SSO support for your cluster][guides.tutorial.how-to-activate-sso-to-connect-to-your-eks-cluster]. <br />⚠️ `aws.iam.sso_role_arn` should be set. | `false` |
| boolean | Deprecated - Enable SSO sync allowing IAM users to connect to cluster using SSO. <br />⚠️ `aws.iam.sso_role_arn` should be set. | `false` |

#### aws.iam.sso_role_arn ![](/img/advanced_settings/aws.svg)

| Type | Description | Default Value |
|---------|-----------------------------------------------------------------------------|---------------|
| string | Allows you to specify the SSO role ARN to be used to connect to your cluster. [Setup SSO support for your cluster][guides.tutorial.how-to-activate-sso-to-connect-to-your-eks-cluster] | `""` |
| string | Deprecated - Allows you to specify the SSO role ARN to be used to connect to your cluster. | `""` |


## Object storage
Expand Down
2 changes: 1 addition & 1 deletion website/docs/using-qovery/interface.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
last_modified_on: "2023-12-27"
last_modified_on: "2025-03-10"
title: Interface
description: "Everything you need to know to use Qovery"
sidebar_label: hidden
Expand Down
6 changes: 3 additions & 3 deletions website/guides/advanced/sub-account-sso.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
last_modified_on: "2024-12-18"
last_modified_on: "2025-03-13"
$schema: "/.meta/.schemas/guides.json"
title: Configure Single Sign-On (SSO) for an AWS sub-account
description: Learn how to configure Single Sign-On (SSO) on AWS for a sub-account in Qovery.
Expand Down Expand Up @@ -46,9 +46,9 @@ In the ends, you should see your users in the AWS IAM Identity Center console:
<img src="/img/aws-subaccount-sso/iic-users-list.png" alt="iic user list" />
</p>

# Ass SSO (with Qovery) on your EKS cluster to support SSO (optional)
# Add SSO (with Qovery) on your EKS cluster to support SSO (optional)

Qovery allows you to connect to your EKS cluster using SSO. It's optional, but if you want to do this anyway, please [refer to this guide](/guides/tutorial/how-to-activate-sso-to-connect-to-your-eks-cluster).
Please follow this [AWS guide](https://aws.amazon.com/fr/blogs/containers/a-quick-path-to-amazon-eks-single-sign-on-using-aws-sso/)

# SSO sync for Google workspace (optional)

Expand Down
4 changes: 2 additions & 2 deletions website/guides/advanced/sub-account-sso.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,9 +45,9 @@ In the ends, you should see your users in the AWS IAM Identity Center console:
<img src="/img/aws-subaccount-sso/iic-users-list.png" alt="iic user list" />
</p>

# Ass SSO (with Qovery) on your EKS cluster to support SSO (optional)
# Add SSO (with Qovery) on your EKS cluster to support SSO (optional)

Qovery allows you to connect to your EKS cluster using SSO. It's optional, but if you want to do this anyway, please [refer to this guide](/guides/tutorial/how-to-activate-sso-to-connect-to-your-eks-cluster).
Please follow this [AWS guide](https://aws.amazon.com/fr/blogs/containers/a-quick-path-to-amazon-eks-single-sign-on-using-aws-sso/)

# SSO sync for Google workspace (optional)

Expand Down
268 changes: 0 additions & 268 deletions website/guides/tutorial/how-to-activate-sso-to-connect-to-your-eks-cluster.md
View file
Open in desktop

This file was deleted.

Loading