Merge pull request #1705 from my-git9/working-with-gatekeeper2

fix wehbhook error
This commit is contained in:
karmada-bot 2022-05-02 10:04:21 +08:00 committed by GitHub
commit c1c001c126
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions

View File

@ -44,7 +44,7 @@ In this case, you will use Gatekeeper v3.7.2. Related deployment files are from
- v1
- v1beta1
clientConfig:
#Change the clientconfig from service type to url type cause wehbhook config and service are not in the same cluster.
#Change the clientconfig from service type to url type cause webhook config and service are not in the same cluster.
url: https://gatekeeper-webhook-service.gatekeeper-system.svc:443/v1/mutate
failurePolicy: Ignore
matchPolicy: Exact
@ -77,7 +77,7 @@ In this case, you will use Gatekeeper v3.7.2. Related deployment files are from
- v1
- v1beta1
clientConfig:
#Change the clientconfig from service type to url type cause wehbhook config and service are not in the same cluster.
#Change the clientconfig from service type to url type cause webhook config and service are not in the same cluster.
url: https://gatekeeper-webhook-service.gatekeeper-system.svc:443/v1/admit
failurePolicy: Ignore
matchPolicy: Exact
@ -102,7 +102,7 @@ In this case, you will use Gatekeeper v3.7.2. Related deployment files are from
- v1
- v1beta1
clientConfig:
#Change the clientconfig from service type to url type cause wehbhook config and service are not in the same cluster.
#Change the clientconfig from service type to url type cause webhook config and service are not in the same cluster.
url: https://gatekeeper-webhook-service.gatekeeper-system.svc:443/v1/admitlabel
failurePolicy: Fail
matchPolicy: Exact