Log: /mnt/jenkins/workspace/cloud-pxc-operator_PR-1131/e2e-tests/logs/smart-update2-8-0.log No resources found + kubectl patch pxc -n sh --type=merge -p '{"metadata":{"finalizers":[]}}' error: resource(s) were provided, but no name was specified No resources found No resources found No resources found ----------------------------------------------------------------------------------- cleaned up all old namespaces ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- cleaned up old namespaces pxc-operator ----------------------------------------------------------------------------------- Error from server (Forbidden): namespaces "default" is forbidden: this namespace may not be deleted namespace "pxc-operator" deleted namespace/pxc-operator - Error from server (NotFound): namespaces "pxc-operator" not found ----------------------------------------------------------------------------------- create namespace pxc-operator ----------------------------------------------------------------------------------- namespace/pxc-operator created Context "gke_cloud-dev-112233_us-central1-a_jen-pxc-1131-d64e70d4-2-cluster4" modified. ----------------------------------------------------------------------------------- start PXC operator ----------------------------------------------------------------------------------- customresourcedefinition.apiextensions.k8s.io/perconaxtradbclusterbackups.pxc.percona.com serverside-applied customresourcedefinition.apiextensions.k8s.io/perconaxtradbclusterrestores.pxc.percona.com serverside-applied customresourcedefinition.apiextensions.k8s.io/perconaxtradbclusters.pxc.percona.com serverside-applied clusterrole.rbac.authorization.k8s.io/percona-xtradb-cluster-operator unchanged serviceaccount/percona-xtradb-cluster-operator created clusterrolebinding.rbac.authorization.k8s.io/service-account-percona-xtradb-cluster-operator unchanged deployment.apps/percona-xtradb-cluster-operator created service/percona-xtradb-cluster-operator created percona-xtradb-cluster-operator-58bddf54b8-n9grx.Ok ----------------------------------------------------------------------------------- cleaned up all old namespaces ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- cleaned up old namespaces smart-update2-24138 ----------------------------------------------------------------------------------- Error from server (NotFound): namespaces "smart-update2-24138" not found namespace/smart-update2-24138 - Error from server (Forbidden): namespaces "default" is forbidden: this namespace may not be deleted Error from server (NotFound): namespaces "smart-update2-24138" not found ----------------------------------------------------------------------------------- create namespace smart-update2-24138 ----------------------------------------------------------------------------------- namespace/smart-update2-24138 created Context "gke_cloud-dev-112233_us-central1-a_jen-pxc-1131-d64e70d4-2-cluster4" modified. ----------------------------------------------------------------------------------- create secrets for cloud storages ----------------------------------------------------------------------------------- secret/minio-secret created secret/aws-s3-secret created secret/gcp-cs-secret created secret/azure-secret created ----------------------------------------------------------------------------------- install version service ----------------------------------------------------------------------------------- configmap/versions created deployment.apps/version-service created service/version-service created ----------------------------------------------------------------------------------- deploy cert manager ----------------------------------------------------------------------------------- namespace/cert-manager created namespace/cert-manager labeled namespace/cert-manager configured customresourcedefinition.apiextensions.k8s.io/certificaterequests.cert-manager.io created customresourcedefinition.apiextensions.k8s.io/certificates.cert-manager.io created customresourcedefinition.apiextensions.k8s.io/challenges.acme.cert-manager.io created customresourcedefinition.apiextensions.k8s.io/clusterissuers.cert-manager.io created customresourcedefinition.apiextensions.k8s.io/issuers.cert-manager.io created customresourcedefinition.apiextensions.k8s.io/orders.acme.cert-manager.io created serviceaccount/cert-manager-cainjector created serviceaccount/cert-manager created serviceaccount/cert-manager-webhook created configmap/cert-manager-webhook created clusterrole.rbac.authorization.k8s.io/cert-manager-cainjector created clusterrole.rbac.authorization.k8s.io/cert-manager-controller-issuers created clusterrole.rbac.authorization.k8s.io/cert-manager-controller-clusterissuers created clusterrole.rbac.authorization.k8s.io/cert-manager-controller-certificates created clusterrole.rbac.authorization.k8s.io/cert-manager-controller-orders created clusterrole.rbac.authorization.k8s.io/cert-manager-controller-challenges created clusterrole.rbac.authorization.k8s.io/cert-manager-controller-ingress-shim created clusterrole.rbac.authorization.k8s.io/cert-manager-view created clusterrole.rbac.authorization.k8s.io/cert-manager-edit created clusterrole.rbac.authorization.k8s.io/cert-manager-controller-approve:cert-manager-io created clusterrole.rbac.authorization.k8s.io/cert-manager-controller-certificatesigningrequests created clusterrole.rbac.authorization.k8s.io/cert-manager-webhook:subjectaccessreviews created clusterrolebinding.rbac.authorization.k8s.io/cert-manager-cainjector created clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-issuers created clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-clusterissuers created clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-certificates created clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-orders created clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-challenges created clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-ingress-shim created clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-approve:cert-manager-io created clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-certificatesigningrequests created clusterrolebinding.rbac.authorization.k8s.io/cert-manager-webhook:subjectaccessreviews created role.rbac.authorization.k8s.io/cert-manager-cainjector:leaderelection created role.rbac.authorization.k8s.io/cert-manager:leaderelection created role.rbac.authorization.k8s.io/cert-manager-webhook:dynamic-serving created rolebinding.rbac.authorization.k8s.io/cert-manager-cainjector:leaderelection created rolebinding.rbac.authorization.k8s.io/cert-manager:leaderelection created rolebinding.rbac.authorization.k8s.io/cert-manager-webhook:dynamic-serving created service/cert-manager created service/cert-manager-webhook created deployment.apps/cert-manager-cainjector created deployment.apps/cert-manager created deployment.apps/cert-manager-webhook created mutatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook created validatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook created Warning: resource namespaces/cert-manager is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically. Unable to use a TTY - input is not a terminal or the right kind of file customresourcedefinition.apiextensions.k8s.io/perconaxtradbclusters.pxc.percona.com patched deployment.apps/percona-xtradb-cluster-operator env updated ----------------------------------------------------------------------------------- Starting telemetry testing ----------------------------------------------------------------------------------- deployment.apps/version-service-cr created service/version-service-cr created pod "version-service-fbb464655-ldn6j" deleted ----------------------------------------------------------------------------------- Enable telemetry on operator level ----------------------------------------------------------------------------------- deployment.apps/percona-xtradb-cluster-operator configured percona-xtradb-cluster-operator-765f7df9cf-q8m5f.Ok ----------------------------------------------------------------------------------- create PXC minimal cluster ----------------------------------------------------------------------------------- deployment.apps/pxc-client created secret/minimal-cluster created secret/some-name-ssl created secret/some-name-ssl-internal created perconaxtradbcluster.pxc.percona.com/minimal-cluster created ----------------------------------------------------------------------------------- check if Pod is started ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- minimal-cluster-pxc-0...............................Ok ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- minimal-cluster-haproxy-0error: a container name must be specified for pod minimal-cluster-haproxy-0, choose one of: [haproxy pxc-monit] .Ok ----------------------------------------------------------------------------------- write data ----------------------------------------------------------------------------------- pxc-client-757f677487-krp4s.Ok [ERROR] mysql: option '-P' requires an argument command terminated with exit code 5 pxc-client-757f677487-krp4s.Ok [ERROR] mysql: option '-P' requires an argument command terminated with exit code 5 ----------------------------------------------------------------------------------- telemetry was disabled in CR but in operator not ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- operator fallback VS should have telemetry ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- CR VS should not have telemetry ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- telemetry was disabled in operator but not in CR ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- telemetry was disabled in CR as well as in operator ----------------------------------------------------------------------------------- perconaxtradbcluster.pxc.percona.com/minimal-cluster patched pod "percona-xtradb-cluster-operator-765f7df9cf-q8m5f" deleted perconaxtradbcluster.pxc.percona.com "minimal-cluster" deleted deployment.apps "pxc-client" deleted ----------------------------------------------------------------------------------- Disabling telemetry on the operator level ----------------------------------------------------------------------------------- pod "version-service-cr-7bb4cd67bf-4cp2w" deleted pod "version-service-fbb464655-fkbds" deleted deployment.apps/percona-xtradb-cluster-operator configured percona-xtradb-cluster-operator-f4b76b476-bjlzz.Ok ----------------------------------------------------------------------------------- create PXC minimal cluster ----------------------------------------------------------------------------------- deployment.apps/pxc-client created secret/minimal-cluster unchanged secret/some-name-ssl unchanged secret/some-name-ssl-internal unchanged perconaxtradbcluster.pxc.percona.com/minimal-cluster created ----------------------------------------------------------------------------------- check if Pod is started ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- minimal-cluster-pxc-0.....................Ok ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- minimal-cluster-haproxy-0error: a container name must be specified for pod minimal-cluster-haproxy-0, choose one of: [haproxy pxc-monit] .Ok ----------------------------------------------------------------------------------- write data ----------------------------------------------------------------------------------- pxc-client-757f677487-rkppz.Ok [ERROR] mysql: option '-P' requires an argument command terminated with exit code 5 pxc-client-757f677487-rkppz.Ok [ERROR] mysql: option '-P' requires an argument command terminated with exit code 5 ----------------------------------------------------------------------------------- telemetry was disabled in CR but in operator not ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- telemetry was disabled in operator but not in CR ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- cr VS should have telemetry ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- operator VS should not have telemetry ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- telemetry was disabled in CR as well as in operator ----------------------------------------------------------------------------------- perconaxtradbcluster.pxc.percona.com/minimal-cluster patched pod "percona-xtradb-cluster-operator-f4b76b476-bjlzz" deleted perconaxtradbcluster.pxc.percona.com "minimal-cluster" deleted deployment.apps "pxc-client" deleted pod "version-service-cr-7bb4cd67bf-8g7z8" deleted pod "version-service-fbb464655-7d77k" deleted ----------------------------------------------------------------------------------- create PXC minimal cluster ----------------------------------------------------------------------------------- deployment.apps/pxc-client created secret/minimal-cluster unchanged secret/some-name-ssl unchanged secret/some-name-ssl-internal unchanged perconaxtradbcluster.pxc.percona.com/minimal-cluster created ----------------------------------------------------------------------------------- check if Pod is started ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- minimal-cluster-pxc-0................................Ok ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- minimal-cluster-haproxy-0error: a container name must be specified for pod minimal-cluster-haproxy-0, choose one of: [haproxy pxc-monit] .Ok ----------------------------------------------------------------------------------- write data ----------------------------------------------------------------------------------- pxc-client-757f677487-vm2zh.Ok [ERROR] mysql: option '-P' requires an argument command terminated with exit code 5 pxc-client-757f677487-vm2zh.Ok [ERROR] mysql: option '-P' requires an argument command terminated with exit code 5 ----------------------------------------------------------------------------------- telemetry was disabled in CR but in operator not ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- telemetry was disabled in operator but not in CR ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- telemetry was disabled in CR as well as in operator ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- CR VS should not have telemetry ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- operator VS should not have telemetry ----------------------------------------------------------------------------------- perconaxtradbcluster.pxc.percona.com/minimal-cluster patched pod "percona-xtradb-cluster-operator-f4b76b476-vhbht" deleted perconaxtradbcluster.pxc.percona.com "minimal-cluster" deleted deployment.apps "pxc-client" deleted deployment.apps "version-service-cr" deleted ----------------------------------------------------------------------------------- Telemetry testing finished ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- PXC cluster with version service offline ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- create first PXC cluster ----------------------------------------------------------------------------------- secret/my-cluster-secrets created secret/some-name-ssl unchanged secret/some-name-ssl-internal unchanged deployment.apps/pxc-client created perconaxtradbcluster.pxc.percona.com/smart-update created ----------------------------------------------------------------------------------- check if all 3 Pods started ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- smart-update-haproxy-0....................error: a container name must be specified for pod smart-update-haproxy-0, choose one of: [haproxy pxc-monit] .Ok ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- smart-update-pxc-0.Ok smart-update-pxc-1................Ok smart-update-pxc-2.................Ok ----------------------------------------------------------------------------------- write data ----------------------------------------------------------------------------------- pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok Unable to use a TTY - input is not a terminal or the right kind of file ----------------------------------------------------------------------------------- wait cluster consistency ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- PXC cluster update with recommended image by version service ----------------------------------------------------------------------------------- pxc-client-5d749ff8b6-lwrpd.Ok perconaxtradbcluster.pxc.percona.com/smart-update patched Waiting for the last pod to update+ wait_cluster_consistency smart-update 3 2 + local cluster_name=smart-update + local cluster_size=3 + local proxy_size=2 + '[' -z 2 ']' + desc 'wait cluster consistency' + set +o xtrace ----------------------------------------------------------------------------------- wait cluster consistency ----------------------------------------------------------------------------------- pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok perconaxtradbcluster.pxc.percona.com "smart-update" deleted persistentvolumeclaim "datadir-smart-update-pxc-0" deleted persistentvolumeclaim "datadir-smart-update-pxc-1" deleted persistentvolumeclaim "datadir-smart-update-pxc-2" deleted ----------------------------------------------------------------------------------- PXC cluster update with the latest image by version service ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- create first PXC cluster ----------------------------------------------------------------------------------- secret/my-cluster-secrets unchanged secret/some-name-ssl unchanged secret/some-name-ssl-internal unchanged deployment.apps/pxc-client unchanged perconaxtradbcluster.pxc.percona.com/smart-update created ----------------------------------------------------------------------------------- check if all 3 Pods started ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- smart-update-haproxy-0...................error: a container name must be specified for pod smart-update-haproxy-0, choose one of: [haproxy pxc-monit] .Ok ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- smart-update-pxc-0.Ok smart-update-pxc-1.............Ok smart-update-pxc-2.....................Ok ----------------------------------------------------------------------------------- write data ----------------------------------------------------------------------------------- pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok Unable to use a TTY - input is not a terminal or the right kind of file pxc-client-5d749ff8b6-lwrpd.Ok perconaxtradbcluster.pxc.percona.com/smart-update patched Waiting for the last pod to update+ wait_cluster_consistency smart-update 3 2 + local cluster_name=smart-update + local cluster_size=3 + local proxy_size=2 + '[' -z 2 ']' + desc 'wait cluster consistency' + set +o xtrace ----------------------------------------------------------------------------------- wait cluster consistency ----------------------------------------------------------------------------------- pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok perconaxtradbcluster.pxc.percona.com "smart-update" deleted persistentvolumeclaim "datadir-smart-update-pxc-0" deleted persistentvolumeclaim "datadir-smart-update-pxc-1" deleted persistentvolumeclaim "datadir-smart-update-pxc-2" deleted ----------------------------------------------------------------------------------- PXC cluster update with explicitly specified image inside version service ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- create first PXC cluster ----------------------------------------------------------------------------------- secret/my-cluster-secrets unchanged secret/some-name-ssl unchanged secret/some-name-ssl-internal unchanged deployment.apps/pxc-client unchanged perconaxtradbcluster.pxc.percona.com/smart-update created ----------------------------------------------------------------------------------- check if all 3 Pods started ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- smart-update-haproxy-0....................error: a container name must be specified for pod smart-update-haproxy-0, choose one of: [haproxy pxc-monit] .Ok ----------------------------------------------------------------------------------- wait for running cluster ----------------------------------------------------------------------------------- smart-update-pxc-0.Ok smart-update-pxc-1...................Ok smart-update-pxc-2...................Ok ----------------------------------------------------------------------------------- write data ----------------------------------------------------------------------------------- pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok Unable to use a TTY - input is not a terminal or the right kind of file Unable to use a TTY - input is not a terminal or the right kind of file pxc-client-5d749ff8b6-lwrpd.Ok perconaxtradbcluster.pxc.percona.com/smart-update patched Waiting for the last pod to update+ wait_cluster_consistency smart-update 3 2 + local cluster_name=smart-update + local cluster_size=3 + local proxy_size=2 + '[' -z 2 ']' + desc 'wait cluster consistency' + set +o xtrace ----------------------------------------------------------------------------------- wait cluster consistency ----------------------------------------------------------------------------------- pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok pxc-client-5d749ff8b6-lwrpd.Ok perconaxtradbcluster.pxc.percona.com "smart-update" deleted persistentvolumeclaim "datadir-smart-update-pxc-0" deleted persistentvolumeclaim "datadir-smart-update-pxc-1" deleted persistentvolumeclaim "datadir-smart-update-pxc-2" deleted ----------------------------------------------------------------------------------- cleanup ----------------------------------------------------------------------------------- deployment.apps "version-service" deleted service "version-service" deleted ----------------------------------------------------------------------------------- destroy cluster/operator and all other resources ----------------------------------------------------------------------------------- No resources found + kubectl patch pxc -n sh --type=merge -p '{"metadata":{"finalizers":[]}}' error: resource(s) were provided, but no name was specified No resources found No resources found No resources found validatingwebhookconfiguration.admissionregistration.k8s.io "percona-xtradbcluster-webhook" deleted namespace "cert-manager" deleted customresourcedefinition.apiextensions.k8s.io "certificaterequests.cert-manager.io" deleted customresourcedefinition.apiextensions.k8s.io "certificates.cert-manager.io" deleted customresourcedefinition.apiextensions.k8s.io "challenges.acme.cert-manager.io" deleted customresourcedefinition.apiextensions.k8s.io "clusterissuers.cert-manager.io" deleted customresourcedefinition.apiextensions.k8s.io "issuers.cert-manager.io" deleted customresourcedefinition.apiextensions.k8s.io "orders.acme.cert-manager.io" deleted serviceaccount "cert-manager-cainjector" deleted serviceaccount "cert-manager" deleted serviceaccount "cert-manager-webhook" deleted configmap "cert-manager-webhook" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-cainjector" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-controller-issuers" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-controller-clusterissuers" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-controller-certificates" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-controller-orders" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-controller-challenges" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-controller-ingress-shim" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-view" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-edit" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-controller-approve:cert-manager-io" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-controller-certificatesigningrequests" deleted clusterrole.rbac.authorization.k8s.io "cert-manager-webhook:subjectaccessreviews" deleted clusterrolebinding.rbac.authorization.k8s.io "cert-manager-cainjector" deleted clusterrolebinding.rbac.authorization.k8s.io "cert-manager-controller-issuers" deleted clusterrolebinding.rbac.authorization.k8s.io "cert-manager-controller-clusterissuers" deleted clusterrolebinding.rbac.authorization.k8s.io "cert-manager-controller-certificates" deleted clusterrolebinding.rbac.authorization.k8s.io "cert-manager-controller-orders" deleted clusterrolebinding.rbac.authorization.k8s.io "cert-manager-controller-challenges" deleted clusterrolebinding.rbac.authorization.k8s.io "cert-manager-controller-ingress-shim" deleted clusterrolebinding.rbac.authorization.k8s.io "cert-manager-controller-approve:cert-manager-io" deleted clusterrolebinding.rbac.authorization.k8s.io "cert-manager-controller-certificatesigningrequests" deleted clusterrolebinding.rbac.authorization.k8s.io "cert-manager-webhook:subjectaccessreviews" deleted role.rbac.authorization.k8s.io "cert-manager-cainjector:leaderelection" deleted role.rbac.authorization.k8s.io "cert-manager:leaderelection" deleted rolebinding.rbac.authorization.k8s.io "cert-manager-cainjector:leaderelection" deleted rolebinding.rbac.authorization.k8s.io "cert-manager:leaderelection" deleted rolebinding.rbac.authorization.k8s.io "cert-manager-webhook:dynamic-serving" deleted mutatingwebhookconfiguration.admissionregistration.k8s.io "cert-manager-webhook" deleted validatingwebhookconfiguration.admissionregistration.k8s.io "cert-manager-webhook" deleted ----------------------------------------------------------------------------------- test passed -----------------------------------------------------------------------------------