-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subnet Id not found when it exists #12471
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Show the url of the image in the controller po
…On Thu, 12 Dec, 2024, 10:13 Kubernetes Prow Robot, ***@***.***> wrote:
This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will
accept it by applying the triage/accepted label and provide further
guidance.
The triage/accepted label can be added by org members by writing /triage
accepted in a comment.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes-sigs/prow
<https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:>
repository.
—
Reply to this email directly, view it on GitHub
<#12471 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZVWT32GQMVS5NVVVHYBT2FEH55AVCNFSM6AAAAABTO5WAVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZXHAYDEMZRGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
/remove-kind bug |
This looks like an error for the AWS Load Balancer controller. Does the ingress-nginx RBAC/IAM have permission to describe subnets? |
/triage needs-information |
Failed build model due to operation error EC2: DescribeSubnets, https response error StatusCode: 400, RequestID: b3348ce4-2215-403a-8c56-c418efd5147a, api error InvalidSubnetID.NotFound: The subnet ID 'subnet-018ee4ce6ac310793' does not exist
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: voting-app-ingress
annotations:
alb.ingress.kubernetes.io/scheme: internet-facing
alb.ingress.kubernetes.io/target-type: ip
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}]'
alb.ingress.kubernetes.io/subnets: "subnet-0cee6592fc25eb61f, subnet-04b987dfadd099e9d, subnet-018ee4ce6ac310793"
alb.ingress.kubernetes.io/vpc-id: "vpc-061589e79b5151399"
spec:
ingressClassName: alb
rules:
- host: {{ .Values.ingress.host }}
http:
paths:
- path: /vote
pathType: Prefix
backend:
service:
name: {{ .Values.ingress.services.vote }}
port:
number: {{ .Values.ingress.ports.vote }}
- path: /result
pathType: Prefix
backend:
service:
name: {{ .Values.ingress.services.result }}
port:
number: {{ .Values.ingress.ports.result }}
The text was updated successfully, but these errors were encountered: