EKS networking with VPC CNI in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the CNI plugin for EKS cluster networking.

AWS

eksctl create cluster --name my-cluster --version 1.24 --region us-west-2 --nodegroup-name standard-workers --node-type t3.medium --nodes 3 --nodes-min 1 --nodes-max 4 --managed --[1]

Drag options to blanks, or click blank then click option'

Acalico

Bcni-plugin

Cnetwork-plugin

Dvpc-cni

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic terms like 'network-plugin' instead of the specific 'vpc-cni'.

Confusing with other CNI plugins like Calico.

The AWS VPC CNI plugin is specified with the vpc-cni option when creating an EKS cluster with eksctl.

2fill in blank

medium

Complete the code to enable pod networking with the VPC CNI plugin in the EKS cluster.

AWS

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/[1]/config/v1.7/aws-k8s-cni.yaml

Drag options to blanks, or click blank then click option'

Arelease-1.7

Bv1.7

Cmaster

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'main' or 'master' which may not have stable manifests.

Using a tag like 'v1.7' instead of the release branch.

The VPC CNI plugin manifest is applied from the release-1.7 branch to match version 1.7 of the plugin.

3fill in blank

hard

Fix the error in the IAM policy statement to allow the VPC CNI plugin to manage ENIs.

AWS

{
  "Effect": "Allow",
  "Action": [
    "ec2:CreateNetworkInterface",
    "ec2:DescribeNetworkInterfaces",
    "ec2:DeleteNetworkInterface",
    "ec2:AttachNetworkInterface"
  ],
  "Resource": [1]
}

Drag options to blanks, or click blank then click option'

A"arn:aws:ec2:::network-interface"

B"arn:aws:ec2:::network-interface/*"

C"*"

D"arn:aws:ec2:::eni/*"

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect ARN formats for network interfaces.

Restricting resource too narrowly causing permission errors.

The resource must be set to "*" to allow the plugin to manage all network interfaces as required.

4fill in blank

hard

Fill both blanks to configure the environment variables for the VPC CNI plugin to enable custom networking and set the IP target.

AWS

env:
  - name: [1]
    value: "true"
  - name: [2]
    value: "10"

Drag options to blanks, or click blank then click option'

AAWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG

BAWS_VPC_K8S_CNI_LOGLEVEL

CAWS_VPC_K8S_CNI_TARGET_IP

DAWS_VPC_K8S_CNI_ENABLE_DEBUG

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing log level or debug variables with networking config.

Setting wrong variable names causing plugin misconfiguration.

The environment variable AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG enables custom networking, and AWS_VPC_K8S_CNI_TARGET_IP sets the target number of IP addresses per ENI.

5fill in blank

hard

Fill all three blanks to create a Kubernetes ConfigMap for the VPC CNI plugin with custom network config and enable prefix delegation.

AWS

apiVersion: v1
kind: ConfigMap
metadata:
  name: aws-node
  namespace: kube-system
data:
  [1]: "true"
  [2]: "true"
  [3]: "true"

Drag options to blanks, or click blank then click option'

Acustom-network-config

Benable-prefix-delegation

Ceni-config-label-definitions

Denable-warm-ip-target

Attempts:

3 left

💡 Hint

Common Mistakes

Using eni-config-label-definitions which is unrelated to these flags.

Missing one or more required keys causing incomplete config.

The ConfigMap keys custom-network-config, enable-prefix-delegation, and enable-warm-ip-target are used to configure the VPC CNI plugin for advanced networking features.