Fix kops cluster create for weekly runs

[jayanthvn]

What happened:
Kops cluster create is failing because of

github-runner is not in the sudoers file.  This incident will be reported.

Need to fix this line - https://github.com/aws/amazon-vpc-cni-k8s/blob/master/scripts/lib/cluster.sh#L59

Attach logs

What you expected to happen:
Successful creation of kops cluster

How to reproduce it (as minimally and precisely as possible):
N/A

Anything else we need to know?:
N/A

Environment:

• Kubernetes version (use kubectl version):
• CNI Version
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):

[vikasmb]

After the fixes linked to this PR were merged, kops cluster in weekly test suite gets created and the conformance tests pass with latest version of CNI image too.

However, while deleting the resources created, it runs into trouble deleting security and vpc related configs, thus marking the kops test as failed.

Not all resources deleted; waiting before reattempting deletion
	route-table:rtb-064aae08b0cfc2372
Error: not making progress deleting resources; giving up
	vpc:vpc-0b662442aa62fec2b
	security-group:sg-01c0b981a689724af
	dhcp-options:dopt-045ed3eed08d3f266
	subnet:subnet-02cc937a1a2f287bf
Error with exit code 1 occurred on line 116

[vikasmb]

Error during de-provisioning of kops cluster is due to a leaked ENI preventing further cleanup of VPC resources. Leakage of ENI during node termination is an existing issue tracked in #1223

[vikasmb]

With these fixes, we now have a successful kops test run in https://github.com/aws/amazon-vpc-cni-k8s/runs/5382771558?check_suite_focus=true. Closing out this issue.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.