Commit 9aa4d1af authored by hr1sh1kesh's avatar hr1sh1kesh

Review comments: a) Note for VPC Native clusters. b) Note for namespace...

Review comments: a) Note for VPC Native clusters. b) Note for namespace specification during provider creation
parent 9b463453
......@@ -391,7 +391,7 @@ file.
[Crossplane](https://crossplane.io/docs) is a multicloud control plane useful in management of applications and infrastructure across multiple clouds by extending the Kubernetes API using custom resources and controllers watching those custom resources. Crossplane allows provisioning and lifecycle management of infrastructure components across cloud providers in a uniform manner abstracting away cloud provider specific configurations.
The Crossplane GitLab managed application installs Crossplane with a provider of choice on a kubernetes cluster attached to the project repository. Crossplane can then be used to provision infrastructure or managed applications such as postgresql (e.g.: CloudSQL from GCP or RDS from AWS) and other [services](https://crossplane.io/docs/v0.4/services-guide.html) required by the application via the Auto DevOps pipeline.
The Crossplane GitLab managed application installs Crossplane with a provider of choice on a kubernetes cluster attached to the project repository. Crossplane can then be used to provision infrastructure or managed applications such as postgresql (e.g.: CloudSQL from GCP or RDS from AWS) and other services required by the application via the Auto DevOps pipeline.
For configuring Crossplane on the cluster navigate to [Crossplane configuration with GitLab](./crossplane.md)
......
......@@ -9,6 +9,9 @@ For this guide the pre-requisites are as follows:
- Crossplane was previously installed as a [GitLab Managed App](./applications.md#crossplane) on the connected kubernetes cluster with a choice of the stack.
We will use the GCP stack as an example in this guide. The instructions for AWS and Azure will be similar to this.
> Note: Crossplane requires the kubernetes cluster to be VPC Native with Alias IPs enabled so that the IP address of the Pods are routable within the GCP network.
First, we need to declare some environment variables with configuration that will be used throughout this guide:
```
......@@ -51,6 +54,8 @@ EOF
### Configure Crossplane with the cloud provider
Follow the steps to configure the installed cloud provider stack with a user account.
> **Note: The Secret and the Provider resource referencing the Secret needs to be applied to the `gitlab-managed-apps` namespace in the guide. Make sure you change that while following the guide**
[Configure Providers](https://crossplane.io/docs/v0.4/cloud-providers.html)
### Configure Managed Service Access
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment