From dbde54258ab777fc73760a43489cbacea185fdf3 Mon Sep 17 00:00:00 2001 From: Karol Szwaj Date: Mon, 2 Feb 2026 16:21:47 +0100 Subject: [PATCH] add kube-bind label in the kro RGD Signed-off-by: Karol Szwaj On-behalf-of: @SAP karol.szwaj@sap.com --- docs/content/usage/integrations/kro.md | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/docs/content/usage/integrations/kro.md b/docs/content/usage/integrations/kro.md index eb7e56a81..0977acaba 100644 --- a/docs/content/usage/integrations/kro.md +++ b/docs/content/usage/integrations/kro.md @@ -143,6 +143,9 @@ spec: apiVersion: v1alpha1 kind: LoadBalancer group: networking.kro.run + metadata: + labels: + kube-bind.io/exported: "true" spec: domain: string configMapRef: string @@ -214,14 +217,6 @@ spec: EOF ``` -### Add kube-bind Export Label - -Add the export label to the `LoadBalancer` CRD. - -```bash -kubectl label crd loadbalancers.networking.kro.run kube-bind.io/exported=true --overwrite -``` - ### Export the LoadBalancer API Create an `APIServiceExportTemplate`. Crucially, we add **PermissionClaims** to allow the provider