Added Test cases for EnvVars check on CNI daemonset

[cgchinmay]

What type of PR is this?
Added ginkgo test for testing env vars on cni daemonset

What does this PR do / Why do we need it:
Need CNI automation using Ginkgo framework

If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:

cd test/integration-new/cni/env_vars
ginkgo -v --failOnPending -- --cluster-kubeconfig=<kubeconfig> --cluster-name=<cluster>--aws-region=<region>--aws-vpc-id=<vpc-id>

Testing done on this change:

Running Suite: Cni Suite
========================
Random Seed: 1618598445
Will run 3 of 3 specs

cni env test CNI Environment Variables 
  Verifying that secondary ENI is created
  /Users/cgadgil/Documents/amazon-vpc-cni-k8s/test/integration-new/cni/env_vars/env_test.go:22
•
------------------------------
cni env test CNI Environment Variables 
  Changing AWS_VPC_ENI_MTU and AWS_VPC_K8S_CNI_VETHPREFIX
  /Users/cgadgil/Documents/amazon-vpc-cni-k8s/test/integration-new/cni/env_vars/env_test.go:36
STEP: getting the aws-node daemon set in namesapce kube-system
STEP: setting the environment variables on the ds to map[AWS_VPC_ENI_MTU:1300 AWS_VPC_K8S_CNI_VETHPREFIX:veth]
STEP: updating the daemon set with new environment variable
STEP: Deploying a BusyBox deployment
STEP: Validating new MTU value
STEP: Validating new VETH Prefix
STEP: Deleting BusyBox Deployment
STEP: Restoring old value on daemonset
STEP: getting the aws-node daemon set in namesapce kube-system
STEP: setting the environment variables on the ds to map[AWS_VPC_ENI_MTU:1300 AWS_VPC_K8S_CNI_VETHPREFIX:veth]
STEP: updating the daemon set with new environment variable
•
------------------------------
cni env test CNI Environment Variables 
  Changing AWS_VPC_K8S_CNI_LOG_FILE
  /Users/cgadgil/Documents/amazon-vpc-cni-k8s/test/integration-new/cni/env_vars/env_test.go:101
STEP: getting the aws-node daemon set in namesapce kube-system
STEP: setting the environment variables on the ds to map[AWS_VPC_K8S_CNI_LOG_FILE:/host/var/log/aws-routed-eni/ipamd_test.log]
STEP: updating the daemon set with new environment variable
STEP: Restoring old value on daemonset
STEP: getting the aws-node daemon set in namesapce kube-system
STEP: setting the environment variables on the ds to map[AWS_VPC_K8S_CNI_LOG_FILE:/host/var/log/aws-routed-eni/ipamd-logs/ipamd.log]
STEP: updating the daemon set with new environment variable

• [SLOW TEST:88.605 seconds]
cni env test
/Users/cgadgil/Documents/amazon-vpc-cni-k8s/test/integration-new/cni/env_vars/env_test.go:19
  CNI Environment Variables
  /Users/cgadgil/Documents/amazon-vpc-cni-k8s/test/integration-new/cni/env_vars/env_test.go:21
    Changing AWS_VPC_K8S_CNI_LOG_FILE
    /Users/cgadgil/Documents/amazon-vpc-cni-k8s/test/integration-new/cni/env_vars/env_test.go:101
------------------------------

Ran 3 of 3 Specs in 99.584 seconds
SUCCESS! -- 3 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No

Does this change require updates to the CNI daemonset config files to work?:

Assumes using latest CNI

Does this PR introduce any user-facing change?:

No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[jayanthvn]

LGTM :)..will wait for Abhinav to review.

[abhipth]

LGTM

Following improvements can be made in subsequent iterations

• Use test helper docker image to test MTU
• Instead of deploying a deployment with single replica and getting the pod from the deployment. Deploy a single pod. The utility method for the same will be available once the PR is merged.