You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Providers](https://docs.crossplane.io/latest/concepts/providers/) allow us to setup external providers that helps provision infrastructure for external services. </br>
61
+
62
+
For example, our crossplane cluster may have providers for deploying Azure, AWS, GCP or any other external infrastructure </br>
63
+
64
+
Furthermore, there is marketplace that hosts many providers, configurations and extensions for Crossplane called [Upbound](https://marketplace.upbound.io/providers)
Once we have a provider setup, we can configure it using a `ProviderConfig` in Kubernetes </br>
83
+
An impotrant configuration is to tell the Crossplane Provider how to authenticate with its external service. </br>
84
+
85
+
For example, when using an Azure Provider, you need an Azure Service Principal, and for AWS you may need a service account with AWS account id and key. </br>
86
+
Each provider will have their own supported authentication methods. </br>
87
+
88
+
### Create Provider credentials
89
+
90
+
```
91
+
SUBSCRIPTION_ID=<subscription-id>
92
+
RESOURCE_GROUP=marcel-test
93
+
94
+
az account set -s $SUBSCRIPTION_ID
95
+
az group create -n $RESOURCE_GROUP -l australiaeast
error: resource mapping not found for name: "marcel-test-vnet" namespace: "" from "kubernetes/crossplane/resources/azure/resource-vnet.yaml": no matches for kind "VirtualNetwork" in version "network.azure.upbound.io/v1beta1"
123
+
ensure CRDs are installed first
124
+
125
+
```
126
+
We see there is no CRD for Azure VNETs, that is because every type of resource in Azure is modularized into a separate provider, so we will need the networking provider first </br>
0 commit comments