fix(troubleshooting): alb not showing up - #1924
Open
arcegacardenas wants to merge 1 commit into
Open
arcegacardenas wants to merge 1 commit into
arcegacardenas wants to merge 1 commit into
Conversation
…ress The troubleshooting/alb setup applied the ui ingress via a plain 'kubectl apply -k', so the 'alb.ingress.kubernetes.io/inbound-cidrs: $INBOUND_CIDRS' annotation was stored as a literal string. The AWS Load Balancer Controller then failed model-building on every reconcile with 'invalid CIDR address: $INBOUND_CIDRS', so the ALB was never created -- masking the intended subnet-tag (alb_fix_1) and IAM (alb_fix_5) scenarios and leaving alb_fix_5 Step 4 unable to show an ALB hostname. Apply the ingress through envsubst using the module's inbound_cidrs variable (mirroring how alb_fix_7 applies fix_ingress) so a valid CIDR is baked in at setup. The backend service-ui / ui-app selector issues are left untouched for alb_fix_7. Verified on a local deployment: after prepare-environment the annotation holds a real CIDR, the documented subnet/IAM errors surface as intended, and alb_fix_5 Step 4 returns an ALB hostname.
✅ Deploy Preview for eks-workshop ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Hit this same issue. I applied the documented alb_fix_1 subnet remediation on top of the broken state: subnet-discovery errors dropped to 0, but CIDR rejections continued (14 more) and the Ingress ADDRESS stayed empty. Also breaks CI: alb_fix_5 declares hookTimeout=600 and its hook polls .status.loadBalancer.ingress[*].hostname, which never populates while the Ingress is unreconcilable — so the hook burns the full 600s and fails. Scoping envsubst '$INBOUND_CIDRS' to the one variable is a nice touch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ress
The troubleshooting/alb setup applied the ui ingress via a plain 'kubectl apply -k', so the 'alb.ingress.kubernetes.io/inbound-cidrs: $INBOUND_CIDRS' annotation was stored as a literal string. The AWS Load Balancer Controller then failed model-building on every reconcile with 'invalid CIDR address: $INBOUND_CIDRS', so the ALB was never created -- masking the intended subnet-tag (alb_fix_1) and IAM (alb_fix_5) scenarios and leaving alb_fix_5 Step 4 unable to show an ALB hostname.
Apply the ingress through envsubst using the module's inbound_cidrs variable (mirroring how alb_fix_7 applies fix_ingress) so a valid CIDR is baked in at setup. The backend service-ui / ui-app selector issues are left untouched for alb_fix_7.
Verified on a local deployment: after prepare-environment the annotation holds a real CIDR, the documented subnet/IAM errors surface as intended, and alb_fix_5 Step 4 returns an ALB hostname.
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Quality checks
make test module="<module>"it was successful (see https://github.com/aws-samples/eks-workshop-v2/blob/main/docs/automated_tests.md)By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.