aws-samples / aws-samples/eks-workshop-v2

[Bug]: several part of the Networking>Amazon VPC Lattice is not working

Open
#1,825 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
HCL
Stars
626
Forks
613
Avg merge
2d 7h
Merged PRs (30d)
9

Description

### Installation method

Workshop Studio

### What happened?

The VPC Lattice part of the workshop suffers from several issues during execution and regarding the expected results:

**1.** The Gateway API CRD installation command (https://github.com/aws-samples/eks-workshop-v2/blob/3ef7ef797989ed52cb976d0c0040cef125bea18c/website/docs/networking/vpc-lattice/setup.md?plain=1#L37) doesn't install the v1alpha2 version of `TLSRoute` CRD making the AWS Gateway API Controller failing to start with error:

```
{"level":"fatal","ts":"2026-04-03T10:29:15.759Z","logger":"setup","caller":"runtime/proc.go:283","msg":"required CRDs check failed:missing required CRDs: gateway.networking.k8s.io/v1alpha2, Kind=TLSRoute"}
```

The experimental version of the CRDs is needed (alpha* are included in it when only beta and GA are in standard).

**2.** Several environment variables defined in Deployments and ConfigMaps are incorrect, they seem require prefixes to work (changes tracked to the v1 release of the sample application – https://github.com/aws-samples/eks-workshop-v2/pull/1539).

```
SHIPPING_NAME_PREFIX -> RETAIL_CHECKOUT_SHIPPING_NAME_PREFIX
ENDPOINTS_CHECKOUT -> RETAIL_UI_ENDPOINTS_CHECKOUT
```

Also, the value of the variable RETAIL_CHECKOUT_PERSISTENCE_REDIS_URL has been reverted from `redis://checkout-redis.checkout:6379` to `redis://checkout-redis:6379` in the same pull request making the second checkout deployment in checkoutv2 namespace not working ("Configure route section" page of the workshop).

### What did you expect to happen?

The workshop run without issue and as described in the website.

### How can we reproduce it?

Proceed with the VPC Lattice part of the workshop.

### Anything else we need to know?

_No response_

### EKS version

1.33

Contributor guide

Open the contributing guide

Research direction

Start with the VPC Lattice setup.md command linked in the issue and compare it with the Gateway API Controller's required CRDs, including TLSRoute v1alpha2. Review the Deployments and ConfigMaps used by the VPC Lattice workshop and the changes in pull request 1539. Re-run the workshop and verify the controller starts, both checkout deployments work, and the documented results are reached.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, devops, documentation, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.