-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Loading status checks…
Merge pull request #361 from Qovery/add_gcp_doc
Add gcp doc
- Loading branch information
Showing
16 changed files
with
245 additions
and
43 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
97 changes: 93 additions & 4 deletions
97
website/docs/using-qovery/configuration/cloud-service-provider/google-cloud-platform.md.erb
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,106 @@ | ||
--- | ||
last_modified_on: "2020-10-04" | ||
last_modified_on: "2023-12-26" | ||
title: "Google Cloud Platform (GCP)" | ||
description: "Learn how to configure and plug your Google Cloud Platform (GCP) account" | ||
--- | ||
|
||
import Steps from '@site/src/components/Steps'; | ||
import Alert from '@site/src/components/Alert'; | ||
import Assumptions from '@site/src/components/Assumptions'; | ||
|
||
<Alert type="info"> | ||
|
||
Please refer to [this page][docs.using-qovery.configuration.provider.kubernetes] if you want to install Qovery on your own Kubernetes cluster (BYOK). | ||
|
||
</Alert> | ||
|
||
## Managed Kubernetes by Qovery | ||
Qovery lets you quickly deploy applications to your [GCP (GCP)][urls.gcp] account. No knowledge needed, and it takes less than 10 minutes to install Qovery on your GCP account. | ||
|
||
## Getting started | ||
|
||
<Assumptions> | ||
|
||
* You have a Qovery account | ||
* You have created an [Organization][docs.using-qovery.configuration.organization] | ||
* You have a GCP account | ||
|
||
</Assumptions> | ||
|
||
### Connect your GCP account | ||
|
||
To link your GCP account to Qovery you need to provide a GCP JSON credentials key. | ||
|
||
<Alert type="info"> | ||
|
||
You can link more than one GCP account. Qovery also support multiple Cloud providers within the same Organization. Meaning, you can balance your workload on different Cloud providers. | ||
|
||
</Alert> | ||
|
||
#### Create your GCP credentials | ||
|
||
<Steps headingDepth={3}> | ||
<ol> | ||
|
||
<li> | ||
|
||
[Connect to your GCP console](https://console.cloud.google.com) | ||
|
||
</li> | ||
|
||
<li> | ||
|
||
Create a new `Project` or open an exiting one | ||
<img src="/img/gcp-credentials/gcp_project.png" /> | ||
|
||
</li> | ||
|
||
<li> | ||
|
||
Open the embedded Google shell | ||
<img src="/img/gcp-credentials/gcp_shell_1.png" /> | ||
|
||
</li> | ||
|
||
<li> | ||
|
||
Run the following command in the Google Shell to create the service account and generate the json key: | ||
|
||
```bash | ||
wget https://hub.qovery.com/files/create_credentials_gcp.sh && chmod +x create_credentials_gcp.sh && ./create_credentials_gcp.sh $GOOGLE_CLOUD_PROJECT qovery-service-account | ||
``` | ||
|
||
<Alert type="info"> | ||
|
||
You can modify the service account name by replacing `qovery-service-account` by the name of your choice. | ||
|
||
</Alert> | ||
|
||
</li> | ||
|
||
[We currently work on supporting Google Cloud Platform (GCP)](https://www.qovery.com/blog/early-access-for-google-cloud-platform/) as a managed Kubernetes provider. Stay tuned! | ||
<li> | ||
|
||
Once the script is done. A GCP JSON credentials key has been created and you can download it. | ||
<img src="/img/gcp-credentials/gcp_shell_5.png" /> | ||
<img src="/img/gcp-credentials/gcp_shell_6.png" /> | ||
|
||
</li> | ||
</ol> | ||
</Steps> | ||
|
||
Well done!! You now have your GCP `JSON credentials key`; It is time to connect Qovery to your GCP account. | ||
|
||
### Install a new cluster on Qovery | ||
|
||
You will be able to use the credentials you just generated when creating a cluster via the Qovery console. This cluster will be linked to your Qovery organization. | ||
Follow [this documentation][docs.using-qovery.configuration.clusters#creating-a-cluster] to create a new cluster on your organization. | ||
|
||
### Remove your GCP account | ||
|
||
<Alert type="warning"> | ||
|
||
Your applications and your data will be deleted. | ||
|
||
</Alert> | ||
|
||
<%= qovery_cloud_account_coming_soon('Google Cloud Platform', 'https://roadmap.qovery.com/roadmap/support-google-cloud-platform-gcp') %> | ||
To delete Qovery from your GCP account you must be the owner of the Organization and delete the cluster on Qovery side. Follow [this documentation][docs.using-qovery.configuration.clusters#deleting-a-cluster] | ||
Once your GCP account removed from Qovery, everything configured (VPC, Kubernetes, databases, ...) by Qovery will be deleted forever. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.