You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to d...@kubernetes.io, kubernetes-...@googlegroups.com, kubernetes-sig-c...@googlegroups.com
Hi All
I'm working on replacing kube-up clusters(clusters created from the cluster/* shell scripts in the kubernetes/kubernetes repo) with kops clusters for running Kubernetes e2e tests. The shell scripts that provision kube-up clusters are very fragile and no new features are being added to it.
I created a copy of the following critical release informing/blocking jobs:
ci-kubernetes-e2e-gci-gce-serial
I'm still stabilising this test. It was running with the wrong parallel value.
kops & AllAlpha feature gate is broken, I need to investigate this.
ci-kubernetes-gce-conformance-latest
The kops equivalent is passing
ci-kubernetes-e2e-gci-gce
Most of the tests are passing, except for these:
Kubernetes e2e suite.[It] [sig-apps] ReplicaSet should serve a basic image on each replica with a private image
Kubernetes e2e suite.[It] [sig-apps] ReplicationController should serve a basic image on each replica with a private image
Kubernetes e2e suite.[It] [sig-autoscaling] DNS horizontal autoscaling kube-dns-autoscaler should scale kube-dns pods in both nonfaulty and faulty scenarios
Kubernetes e2e suite.[It] [sig-network] Firewall rule should have correct firewall rules for e2e cluster
Kubernetes e2e suite.[It] [sig-node] NodeProblemDetector should run without error
The sig-apps failures are happening because of a missing KubeletCredentialProvider. kops fix
The sig-autoscaling test needs to be rewritten. kops deploys coredns and the kube-dns-autoscaler resources with different names.
The sig-network test needs to be removed, it tests the existence of firewall rules created by kube-up clusters. kops cluster provisioning business logic is already well tested in kubernetes/kops repo.