karmada-io
/
karmada
mirror of https://github.com/karmada-io/karmada.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #6113 from XiShanYongYe-Chang/update-resourceinterprewebhook-readme 

[Cleanup] update some describetion with the resourceinterpreterwebhook readme file
This commit is contained in:
karmada-bot 2025-02-13 16:24:10 +08:00 committed by GitHub
parent c5d640c1d3 06ab130ae8
commit 69abca81ca
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
examples/customresourceinterpreter/README.md
View File

@ -144,7 +144,7 @@ clientConfig:
caBundle: {{caBundle}} 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 ```yaml
clientConfig: clientConfig:
@ -156,7 +156,7 @@ clientConfig:
path: /interpreter-workload path: /interpreter-workload
``` ```
Deploy the Service in `karmada-apiserver`. You can deploy a `ExternalName` type Service in `karmada-apiserver`:
```yaml ```yaml
apiVersion: v1 apiVersion: v1
@ -169,6 +169,8 @@ spec:
externalName: karmada-interpreter-webhook-example.karmada-system.svc.cluster.local 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: In the example of this article, you can directly run the following script to deploy ResourceInterpreterWebhookConfiguration:
<details> <details>