aws / aws/aws-application-networking-k8s
EKS and Lattice configuration reconciliation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 278
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Description
1. Create Kubernetes service in EKS, add the service to Lattice using gateway and httproute which only have http listener configured
2. When Lattice service is operational for http configure an additional listener via the AWS console for https
3. Lattice service will now be available via both http and https, be it for a limited time
4. EKS configuration will overwrite console configuration and the https listener will disappear, somewhere between 10-30 minutes
Question: should configurations which belong in EKS be greyed out and prohibited from being changed in the AWS console?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Reproduce the EKS and VPC Lattice sequence described in the report, then investigate how reconciliation handles the HTTPS listener and determine the intended policy for AWS console changes; done requires an agreed behavior and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100