Error from server (InternalError): error when creating "s2ibuilder.yaml": Internal error occurred: failed calling webhook "s2ibuilder.kb.io": Post "https://webhook-server-service.kubesphere-devops-system.svc:443/mutate-devops-kubesphere-io-v1alpha1-s2ibuilder?timeout=30s": x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0

version: s2ioperator-3.2.1
使用测试案例部署s2ibuilder和s2irun时报错：
Error from server (InternalError): error when creating "s2ibuilder.yaml": Internal error occurred: failed calling webhook "s2ibuilder.kb.io": Post "https://webhook-server-service.kubesphere-devops-system.svc:443/mutate-devops-kubesphere-io-v1alpha1-s2ibuilder?timeout=30s": x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0
和
Error from server (InternalError): error when creating "s2irun.yaml": Internal error occurred: failed calling webhook "vs2irun.kb.io": Post "https://webhook-server-service.kubesphere-devops-system.svc:443/validate-devops-kubesphere-io-v1alpha1-s2irun?timeout=30s": x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0

s2ibuild.yaml
apiVersion: devops.kubesphere.io/v1alpha1
kind: S2iBuilder
metadata:
name: s2ibuilder-sample
spec:
config:
export: true
displayName: "For Test"
sourceUrl: "https://github.com/kubesphere/devops-java-sample"
builderImage: kubesphere/java-8-centos7:v2.1.0
imageName: hello-world # please replace your registry username
tag: v0.0.1
builderPullPolicy: if-not-present
pushAuthentication:
secretRef:
name: s2i-secret-sample # This secret is created by step 1.

s2irun.yaml
apiVersion: devops.kubesphere.io/v1alpha1
kind: S2iRun
metadata:
name: s2irun-sample
spec:
builderName: s2ibuilder-sample

Start by reproducing the failure with the provided s2ibuilder.yaml and s2irun.yaml test cases, focusing on the s2ibuilder.kb.io and vs2irun.kb.io webhook errors. Done means both resources can be created without the x509 legacy Common Name certificate error.