Fix cni plugin for AWS scale tests

[prateekgogia]

No description provided.

[k8s-ci-robot]

Hi @prateekgogia. 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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dims]

/ok-to-test
/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, prateekgogia

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

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/kops/OWNERS [dims]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hakman]

/hold

[hakman]

@prateekgogia @dims Amazon VPC CNI doesn't work with Ubuntu 22.04 (see aws/amazon-vpc-cni-k8s#2103).

I suggest to also add the scale tests with Calico, as we know it's working.

[prateekgogia]

@prateekgogia @dims Amazon VPC CNI doesn't work with Ubuntu 22.04 (see aws/amazon-vpc-cni-k8s#2103).

I suggest to also add the scale tests with Calico, as we know it's working.

Will create another follow up PR to change to Ubuntu 20.04, once this PR kubernetes/kops#15557 passes the tests

[hakman]

/hold cancel
/lgtm cancel

config/jobs/kubernetes/kops/build_jobs.py:1068:0: C0301: Line too long (109/100) (line-too-long)
config/jobs/kubernetes/kops/build_jobs.py:1077:0: C0301: Line too long (109/100) (line-too-long)

[prateekgogia]

/test presubmit-kops-aws-scale-amazonvpc-using-cl2

[k8s-ci-robot]

@prateekgogia: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-test-infra-gubernator
• /test pull-test-infra-integration
• /test pull-test-infra-prow-checkconfig
• /test pull-test-infra-prow-image-build-test
• /test pull-test-infra-unit-test
• /test pull-test-infra-verify-cri-o
• /test pull-test-infra-verify-lint

The following commands are available to trigger optional jobs:

• /test pull-test-infra-bazel
• /test pull-test-infra-prow-checkconfig-loose
• /test pull-test-infra-unit-test-race-detector-nonblocking

Use /test all to run the following jobs that were automatically triggered:

• pull-test-infra-gubernator
• pull-test-infra-prow-checkconfig
• pull-test-infra-prow-checkconfig-loose
• pull-test-infra-unit-test
• pull-test-infra-unit-test-race-detector-nonblocking
• pull-test-infra-verify-lint

In response to this:

/test presubmit-kops-aws-scale-amazonvpc-using-cl2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[hakman]

/lgtm

[hakman]

/retest

[hakman]

/retest

[hakman]

/test pull-test-infra-unit-test

[k8s-triage-robot]

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

[k8s-triage-robot]

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

[k8s-triage-robot]

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

[k8s-ci-robot]

@prateekgogia: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key kops-periodics-distros.yaml using file config/jobs/kubernetes/kops/kops-periodics-distros.yaml
• key kops-periodics-grid.yaml using file config/jobs/kubernetes/kops/kops-periodics-grid.yaml
• key kops-periodics-misc2.yaml using file config/jobs/kubernetes/kops/kops-periodics-misc2.yaml
• key kops-presubmits-distros.yaml using file config/jobs/kubernetes/kops/kops-presubmits-distros.yaml
• key kops-presubmits-scale.yaml using file config/jobs/kubernetes/kops/kops-presubmits-scale.yaml

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.