From 06ab130ae8312aeaae3a6e51fc3d83b7f22e9546 Mon Sep 17 00:00:00 2001 From: changzhen Date: Wed, 12 Feb 2025 17:29:34 +0800 Subject: [PATCH] update some describetion with the resourceinterpreterwebhook readme file Signed-off-by: changzhen --- examples/customresourceinterpreter/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/examples/customresourceinterpreter/README.md b/examples/customresourceinterpreter/README.md index 49514dbf0..cfd378f83 100644 --- a/examples/customresourceinterpreter/README.md +++ b/examples/customresourceinterpreter/README.md @@ -144,7 +144,7 @@ clientConfig: caBundle: {{caBundle}} ``` -Alternatively, you can also define service in clientConfig, which requires you to deploy a Service of type ExternalName in `Karmada-apiserver`: +Alternatively, you can also declare service in clientConfig: ```yaml clientConfig: @@ -156,7 +156,7 @@ clientConfig: path: /interpreter-workload ``` -Deploy the Service in `karmada-apiserver`. +You can deploy a `ExternalName` type Service in `karmada-apiserver`: ```yaml apiVersion: v1 @@ -169,6 +169,8 @@ spec: externalName: karmada-interpreter-webhook-example.karmada-system.svc.cluster.local ``` +Or you do not need to deploy any Service in `karmada-apiserver`, it will fall back to standard Kubernetes service DNS name format: `https://karmada-interpreter-webhook-example.karmada-system.svc:443/interpreter-workload`. + In the example of this article, you can directly run the following script to deploy ResourceInterpreterWebhookConfiguration: