Created
December 27, 2021 18:47
-
-
Save jvanz/f262764ac1dc7e2d4b7f5d06bd8f9169 to your computer and use it in GitHub Desktop.
Kubecontroller issue 110
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| v1.19.16-k3s1 v1.20.12-k3s1 v1.20.13-k3s1 v1.20.14-k3s1 v1.21.6-k3s1 v1.21.7-k3s1 v1.21.8-k3s1 v1.22.3-k3s1 v1.22.4-k3s1 v1.22.5-k3s1 | |
| ################################################### | |
| ##### Testing v1.19.16-k3s1 #### | |
| ################################################### | |
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0002] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0002] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0002] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0002] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0002] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.19.16-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0001] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0001] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0001] HostIP: using network gateway... | |
| [36mINFO[0m[0001] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0001] Starting servers... | |
| [36mINFO[0m[0001] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0007] Starting agents... | |
| [36mINFO[0m[0007] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0015] Starting helpers... | |
| [36mINFO[0m[0015] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0022] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0022] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0027] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0027] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 11:47:30 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 11:48:03 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| NAME: kubewarden-controller | |
| LAST DEPLOYED: Mon Dec 27 11:48:10 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| kubewarden-controller installed. | |
| You can start defining cluster admission policies by using the | |
| `clusteradmissionpolicies.policies.kubewarden.io` resource. | |
| For more information checkout https://kubewarden.io/ | |
| > **Warning:** the `ClusterAdmissionPolicy` resources of version | |
| > `v1alpha1` are now removed. Refer to the `v0.2.0` release notes to | |
| > find out how to migrate them to `v1alpha2` if you still need to do | |
| > so. | |
| ################################################### | |
| ##### Testing v1.20.12-k3s1 #### | |
| ################################################### | |
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0002] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0002] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0002] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0002] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0002] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.20.12-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0003] Pulling image 'rancher/k3s:v1.20.12-k3s1' | |
| [36mINFO[0m[0010] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0010] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0010] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0010] HostIP: using network gateway... | |
| [36mINFO[0m[0010] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0010] Starting servers... | |
| [36mINFO[0m[0010] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0011] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0017] Starting agents... | |
| [36mINFO[0m[0017] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0026] Starting helpers... | |
| [36mINFO[0m[0026] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0033] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0033] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0038] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0038] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 11:50:07 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 11:51:12 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| NAME: kubewarden-controller | |
| LAST DEPLOYED: Mon Dec 27 11:51:38 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| kubewarden-controller installed. | |
| You can start defining cluster admission policies by using the | |
| `clusteradmissionpolicies.policies.kubewarden.io` resource. | |
| For more information checkout https://kubewarden.io/ | |
| > **Warning:** the `ClusterAdmissionPolicy` resources of version | |
| > `v1alpha1` are now removed. Refer to the `v0.2.0` release notes to | |
| > find out how to migrate them to `v1alpha2` if you still need to do | |
| > so. | |
| ################################################### | |
| ##### Testing v1.20.13-k3s1 #### | |
| ################################################### | |
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0002] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0002] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0002] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0002] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0002] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.20.13-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0003] Pulling image 'rancher/k3s:v1.20.13-k3s1' | |
| [36mINFO[0m[0010] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0010] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0011] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0011] HostIP: using network gateway... | |
| [36mINFO[0m[0011] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0011] Starting servers... | |
| [36mINFO[0m[0011] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0011] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0016] Starting agents... | |
| [36mINFO[0m[0016] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0029] Starting helpers... | |
| [36mINFO[0m[0029] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0036] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0036] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0041] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0041] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 11:53:04 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 11:53:41 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| NAME: kubewarden-controller | |
| LAST DEPLOYED: Mon Dec 27 11:53:52 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| kubewarden-controller installed. | |
| You can start defining cluster admission policies by using the | |
| `clusteradmissionpolicies.policies.kubewarden.io` resource. | |
| For more information checkout https://kubewarden.io/ | |
| > **Warning:** the `ClusterAdmissionPolicy` resources of version | |
| > `v1alpha1` are now removed. Refer to the `v0.2.0` release notes to | |
| > find out how to migrate them to `v1alpha2` if you still need to do | |
| > so. | |
| ################################################### | |
| ##### Testing v1.20.14-k3s1 #### | |
| ################################################### | |
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0002] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0003] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0003] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0003] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0003] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0003] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.20.14-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0003] Pulling image 'rancher/k3s:v1.20.14-k3s1' | |
| [36mINFO[0m[0007] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0007] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0007] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0007] HostIP: using network gateway... | |
| [36mINFO[0m[0007] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0007] Starting servers... | |
| [36mINFO[0m[0008] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0008] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0013] Starting agents... | |
| [36mINFO[0m[0013] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0022] Starting helpers... | |
| [36mINFO[0m[0022] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0028] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0028] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0033] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0033] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 11:55:01 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 11:55:33 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| NAME: kubewarden-controller | |
| LAST DEPLOYED: Mon Dec 27 11:55:44 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| kubewarden-controller installed. | |
| You can start defining cluster admission policies by using the | |
| `clusteradmissionpolicies.policies.kubewarden.io` resource. | |
| For more information checkout https://kubewarden.io/ | |
| > **Warning:** the `ClusterAdmissionPolicy` resources of version | |
| > `v1alpha1` are now removed. Refer to the `v0.2.0` release notes to | |
| > find out how to migrate them to `v1alpha2` if you still need to do | |
| > so. | |
| ################################################### | |
| ##### Testing v1.21.6-k3s1 #### | |
| ################################################### | |
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0002] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0002] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0002] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0002] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0002] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.21.6-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0003] Pulling image 'rancher/k3s:v1.21.6-k3s1' | |
| [36mINFO[0m[0010] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0010] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0010] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0010] HostIP: using network gateway... | |
| [36mINFO[0m[0010] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0010] Starting servers... | |
| [36mINFO[0m[0010] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0011] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0017] Starting agents... | |
| [36mINFO[0m[0017] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0030] Starting helpers... | |
| [36mINFO[0m[0030] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0037] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0037] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0042] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0042] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Unable to get an update from the "bitnami" chart repository (https://charts.bitnami.com/bitnami): | |
| stream error: stream ID 1; INTERNAL_ERROR | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 11:57:05 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 11:57:35 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| ################################################### | |
| ##### Testing v1.21.7-k3s1 #### | |
| ################################################### | |
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0002] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0002] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0002] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0002] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0002] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.21.7-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0003] Pulling image 'rancher/k3s:v1.21.7-k3s1' | |
| [36mINFO[0m[0007] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0008] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0008] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0008] HostIP: using network gateway... | |
| [36mINFO[0m[0008] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0008] Starting servers... | |
| [36mINFO[0m[0008] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0008] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0013] Starting agents... | |
| [36mINFO[0m[0013] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0026] Starting helpers... | |
| [36mINFO[0m[0026] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0033] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0033] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0038] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0038] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 11:59:03 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 11:59:35 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| NAME: kubewarden-controller | |
| LAST DEPLOYED: Mon Dec 27 11:59:43 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| kubewarden-controller installed. | |
| You can start defining cluster admission policies by using the | |
| `clusteradmissionpolicies.policies.kubewarden.io` resource. | |
| For more information checkout https://kubewarden.io/ | |
| > **Warning:** the `ClusterAdmissionPolicy` resources of version | |
| > `v1alpha1` are now removed. Refer to the `v0.2.0` release notes to | |
| > find out how to migrate them to `v1alpha2` if you still need to do | |
| > so. | |
| ################################################### | |
| ##### Testing v1.21.8-k3s1 #### | |
| ################################################### | |
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0002] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0002] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0002] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0002] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0002] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.21.8-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0001] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0001] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0001] HostIP: using network gateway... | |
| [36mINFO[0m[0001] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0001] Starting servers... | |
| [36mINFO[0m[0001] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0007] Starting agents... | |
| [36mINFO[0m[0007] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0015] Starting helpers... | |
| [36mINFO[0m[0015] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0022] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0022] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0027] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0027] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 12:00:44 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 12:01:21 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| NAME: kubewarden-controller | |
| LAST DEPLOYED: Mon Dec 27 12:01:32 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| kubewarden-controller installed. | |
| You can start defining cluster admission policies by using the | |
| `clusteradmissionpolicies.policies.kubewarden.io` resource. | |
| For more information checkout https://kubewarden.io/ | |
| > **Warning:** the `ClusterAdmissionPolicy` resources of version | |
| > `v1alpha1` are now removed. Refer to the `v0.2.0` release notes to | |
| > find out how to migrate them to `v1alpha2` if you still need to do | |
| > so. | |
| ################################################### | |
| ##### Testing v1.22.3-k3s1 #### | |
| ################################################### | |
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0003] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0003] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0003] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0003] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0003] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.22.3-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0003] Pulling image 'rancher/k3s:v1.22.3-k3s1' | |
| [36mINFO[0m[0011] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0011] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0011] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0011] HostIP: using network gateway... | |
| [36mINFO[0m[0011] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0011] Starting servers... | |
| [36mINFO[0m[0011] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0012] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0018] Starting agents... | |
| [36mINFO[0m[0018] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0027] Starting helpers... | |
| [36mINFO[0m[0027] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0034] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0034] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0038] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0038] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 12:02:37 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 12:03:06 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| NAME: kubewarden-controller | |
| LAST DEPLOYED: Mon Dec 27 12:03:13 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| kubewarden-controller installed. | |
| You can start defining cluster admission policies by using the | |
| `clusteradmissionpolicies.policies.kubewarden.io` resource. | |
| For more information checkout https://kubewarden.io/ | |
| > **Warning:** the `ClusterAdmissionPolicy` resources of version | |
| > `v1alpha1` are now removed. Refer to the `v0.2.0` release notes to | |
| > find out how to migrate them to `v1alpha2` if you still need to do | |
| > so. | |
| ################################################### | |
| ##### Testing v1.22.4-k3s1 #### | |
| ################################################### | |
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0002] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0002] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0002] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0002] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0002] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.22.4-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0001] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0001] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0001] HostIP: using network gateway... | |
| [36mINFO[0m[0001] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0001] Starting servers... | |
| [36mINFO[0m[0001] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0007] Starting agents... | |
| [36mINFO[0m[0007] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0016] Starting helpers... | |
| [36mINFO[0m[0016] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0023] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0023] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0028] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0028] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 12:04:13 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 12:04:48 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| NAME: kubewarden-controller | |
| LAST DEPLOYED: Mon Dec 27 12:04:54 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| kubewarden-controller installed. | |
| You can start defining cluster admission policies by using the | |
| `clusteradmissionpolicies.policies.kubewarden.io` resource. | |
| For more information checkout https://kubewarden.io/ | |
| > **Warning:** the `ClusterAdmissionPolicy` resources of version | |
| > `v1alpha1` are now removed. Refer to the `v0.2.0` release notes to | |
| > find out how to migrate them to `v1alpha2` if you still need to do | |
| > so. | |
| ################################################### | |
| ##### Testing v1.22.5-k3s1 #### | |
| ################################################### | |
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0002] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0002] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0002] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0002] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0002] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.22.5-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0003] Pulling image 'rancher/k3s:v1.22.5-k3s1' | |
| [36mINFO[0m[0009] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0010] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0010] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0010] HostIP: using network gateway... | |
| [36mINFO[0m[0010] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0010] Starting servers... | |
| [36mINFO[0m[0010] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0010] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0015] Starting agents... | |
| [36mINFO[0m[0015] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0025] Starting helpers... | |
| [36mINFO[0m[0025] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0031] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0031] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0035] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0035] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 12:05:57 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 12:06:24 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| NAME: kubewarden-controller | |
| LAST DEPLOYED: Mon Dec 27 12:06:31 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| kubewarden-controller installed. | |
| You can start defining cluster admission policies by using the | |
| `clusteradmissionpolicies.policies.kubewarden.io` resource. | |
| For more information checkout https://kubewarden.io/ | |
| > **Warning:** the `ClusterAdmissionPolicy` resources of version | |
| > `v1alpha1` are now removed. Refer to the `v0.2.0` release notes to | |
| > find out how to migrate them to `v1alpha2` if you still need to do | |
| > so. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| k3d cluster delete testing-cert-manager-helm-chart | |
| [36mINFO[0m[0000] Deleting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0000] Deleted k3d-testing-cert-manager-helm-chart-serverlb | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-agent-0 | |
| [36mINFO[0m[0002] Deleted k3d-testing-cert-manager-helm-chart-server-0 | |
| [36mINFO[0m[0002] Deleting image volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0002] Removing cluster details from default kubeconfig... | |
| [36mINFO[0m[0002] Removing standalone kubeconfig file (if there is one)... | |
| [36mINFO[0m[0002] Successfully deleted cluster testing-cert-manager-helm-chart! | |
| k3d cluster create testing-cert-manager-helm-chart --wait --timeout 5m --image rancher/k3s:v1.21.6-k3s1 --config /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml -v /dev/mapper:/dev/mapper | |
| [36mINFO[0m[0000] Using config file /home/jvanz/suse/kubewarden/kubewarden-end-to-end-tests/resources/k3d-default.yaml (k3d.io/v1alpha2#simple) | |
| [36mINFO[0m[0000] Prep: Network | |
| [36mINFO[0m[0000] Re-using existing network 'k3d-testing-cert-manager-helm-chart' (822dfddaa59dcbd51be5d9a6dd37c82492c5605a8f28f8c497544ea2fb9b1362) | |
| [36mINFO[0m[0000] Created volume 'k3d-testing-cert-manager-helm-chart-images' | |
| [36mINFO[0m[0000] Starting new tools node... | |
| [36mINFO[0m[0000] Starting Node 'k3d-testing-cert-manager-helm-chart-tools' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0001] Creating node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0001] Creating LoadBalancer 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0001] Using the k3d-tools node to gather environment information | |
| [36mINFO[0m[0001] HostIP: using network gateway... | |
| [36mINFO[0m[0001] Starting cluster 'testing-cert-manager-helm-chart' | |
| [36mINFO[0m[0001] Starting servers... | |
| [36mINFO[0m[0001] Starting Node 'k3d-testing-cert-manager-helm-chart-server-0' | |
| [36mINFO[0m[0001] Deleted k3d-testing-cert-manager-helm-chart-tools | |
| [36mINFO[0m[0008] Starting agents... | |
| [36mINFO[0m[0008] Starting Node 'k3d-testing-cert-manager-helm-chart-agent-0' | |
| [36mINFO[0m[0021] Starting helpers... | |
| [36mINFO[0m[0021] Starting Node 'k3d-testing-cert-manager-helm-chart-serverlb' | |
| [36mINFO[0m[0027] Injecting record for host.k3d.internal into CoreDNS configmap... | |
| [36mINFO[0m[0027] Injecting '192.168.32.1 host.k3d.internal' into /etc/hosts of all nodes... | |
| [36mINFO[0m[0032] Cluster 'testing-cert-manager-helm-chart' created successfully! | |
| [36mINFO[0m[0033] You can now use it like this: | |
| kubectl cluster-info | |
| kubectl --context k3d-testing-cert-manager-helm-chart wait --for=condition=Ready nodes --all | |
| node/k3d-testing-cert-manager-helm-chart-agent-0 condition met | |
| node/k3d-testing-cert-manager-helm-chart-server-0 condition met | |
| helm repo add jetstack https://charts.jetstack.io | |
| "jetstack" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --wait cert-manager jetstack/cert-manager --create-namespace -n cert-manager --set installCRDs=true | |
| NAME: cert-manager | |
| LAST DEPLOYED: Mon Dec 27 15:01:06 2021 | |
| NAMESPACE: cert-manager | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| cert-manager v1.6.1 has been deployed successfully! | |
| In order to begin issuing certificates, you will need to set up a ClusterIssuer | |
| or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). | |
| More information on the different types of issuers and how to configure them | |
| can be found in our documentation: | |
| https://cert-manager.io/docs/configuration/ | |
| For information on how to configure cert-manager to automatically provision | |
| Certificates for Ingress resources, take a look at the `ingress-shim` | |
| documentation: | |
| https://cert-manager.io/docs/usage/ingress/ | |
| helm repo add kubewarden https://charts.kubewarden.io | |
| "kubewarden" already exists with the same configuration, skipping | |
| helm repo update | |
| Hang tight while we grab the latest from your chart repositories... | |
| ...Successfully got an update from the "apache-airflow" chart repository | |
| ...Successfully got an update from the "kubewarden" chart repository | |
| ...Successfully got an update from the "ingress-nginx" chart repository | |
| ...Successfully got an update from the "jaegertracing" chart repository | |
| ...Successfully got an update from the "elastic" chart repository | |
| ...Successfully got an update from the "jetstack" chart repository | |
| ...Successfully got an update from the "prometheus-community" chart repository | |
| ...Successfully got an update from the "stable" chart repository | |
| ...Successfully got an update from the "bitnami" chart repository | |
| Update Complete. ⎈Happy Helming!⎈ | |
| helm install --create-namespace -n kubewarden kubewarden-crds kubewarden/kubewarden-crds | |
| NAME: kubewarden-crds | |
| LAST DEPLOYED: Mon Dec 27 15:01:41 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| helm install --wait -n kubewarden kubewarden-controller kubewarden/kubewarden-controller | |
| NAME: kubewarden-controller | |
| LAST DEPLOYED: Mon Dec 27 15:01:51 2021 | |
| NAMESPACE: kubewarden | |
| STATUS: deployed | |
| REVISION: 1 | |
| TEST SUITE: None | |
| NOTES: | |
| kubewarden-controller installed. | |
| You can start defining cluster admission policies by using the | |
| `clusteradmissionpolicies.policies.kubewarden.io` resource. | |
| For more information checkout https://kubewarden.io/ | |
| > **Warning:** the `ClusterAdmissionPolicy` resources of version | |
| > `v1alpha1` are now removed. Refer to the `v0.2.0` release notes to | |
| > find out how to migrate them to `v1alpha2` if you still need to do | |
| > so. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment