Skip to content

enable nested virtualization in prow GCP tests #21826

@medyagh

Description

@medyagh

currently

the prow kvm test use (32 cores)
n2-standard-32

while our internal gcp project (old infra) uses
n2-standard-8 (8 vCPUs, 32 GB Memory)

but our old infra uses special image that supports nested virtuazliation
(as explained here http://www.brianlinkletter.com/enable-nested-virtualization-on-google-cloud/)

the prow tests despite having much more cores are running signifancly slower
as seen in these two gopoghs (Sort by Duration)

Prow:
https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/minikube/21556/integration-kvm-docker-linux-x86-64/1982572213521354752/artifacts/test.html

minikube internal gcp project:
https://storage.googleapis.com/minikube-builds/logs/master/42124/KVM_Linux.html

Example Prow:
TestKubernetesUpgrade | 676.92 seconds
Example Minikube Jenkins:
TestKubernetesUpgrade | 208.78

(check full gopogh links above and sort by duraiton)

Metadata

Metadata

Assignees

No one assigned

    Labels

    sig/k8s-infraCategorizes an issue or PR as relevant to SIG K8s Infra.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions