diff --git a/docs/content/usage/integrations/.pages b/docs/content/usage/integrations/.pages index c695c2b86..b0579ff79 100644 --- a/docs/content/usage/integrations/.pages +++ b/docs/content/usage/integrations/.pages @@ -1,2 +1,3 @@ nav: - - cert-manager.md \ No newline at end of file + - cert-manager.md + - crossplane.md diff --git a/docs/content/usage/integrations/cert-manager.md b/docs/content/usage/integrations/cert-manager.md index 0f59e84a0..831927df1 100644 --- a/docs/content/usage/integrations/cert-manager.md +++ b/docs/content/usage/integrations/cert-manager.md @@ -9,8 +9,26 @@ weight: 10 1. **Install cert-manager** in your Kubernetes cluster, where kube-bind backend is running, if you haven't already. You can follow the official installation guide [here](https://cert-manager.io/docs/installation/kubernetes/). +2. **Add kube-bind export label** to certificate CRD. -2. **Create a `kube-bind` template for `Certificate` resources** to allow service consumers to request TLS certificates. Below is an example template: +```bash +kubectl label crd certificates.cert-manager.io kube-bind.io/exported=true --overwrite +``` + +3. **Create SelfSigned issuer** in the provider cluster. + +```yaml +kubectl apply -f - <