Hi @sats-23. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Thank you @sats-23! Would you mind changing this to the full image, not just the tag?
Also, why change from headless to driver?

Thank you @sats-23! Would you mind changing this to the full image, not just the tag? Also, why change from headless to driver?

Hi @hakman, thank you for the comments.

1. I have made the changes to support the full image, please refer: cf65d92

2. The Nvidia driver was constantly upgraded and the current version used is nvidia-driver-535-server.
   Refer:

   kops/pkg/apis/kops/containerdconfig.go

   Line 25 in 5f564fe

   const NvidiaDefaultDriverPackage = "nvidia-driver-535-server"

   
   While the driver kept up with the updates, the comments were still referencing the old driver version, so I just updated those to reflect the current usage.

/ok-to-test

/retest

@sats-23 this LGTM, so pretty much just the tests need to finish running.
Would you mind also squashing the commits, it makes it easier to cherry-pick.
Thanks!

@sats-23 this LGTM, so pretty much just the tests need to finish running. Would you mind also squashing the commits, it makes it easier to cherry-pick. Thanks!

Thank you for the feedback, I have squashed all commits.

Awesome! 🚀
/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

/test pull-kops-e2e-gce-cni-calico
/retest

/retest

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

/test pull-kops-e2e-gce-cni-calico
/retest

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

/hold for fixing test failures

/hold for fixing test failures

Hi @hakman
Is there any clue on the infra issues at the moment? Any pending action from my end?

Hi @sats-23

Is there any clue on the infra issues at the moment?

not yet

Any pending action from my end?

no

/test all
/unhold

/test pull-kops-e2e-k8s-gce-cilium
/test pull-kops-e2e-k8s-gce-ipalias
/retest

/retest

/override pull-kops-e2e-cni-amazonvpc

@hakman: Overrode contexts on behalf of hakman: pull-kops-e2e-cni-amazonvpc

@sats-23: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.