Closed benjaminlostandfound closed 1 month ago
@benjaminlostandfound: 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.
The project deployment documentation for AWS is here and it looks like you are not using the documented installation, because the yaml manifest from project configures NLB and but your message suggestes yo are using ALB.
/remove-kind bug /kind support
From your ingress logs: [software-dev-oftware-dev-80] [] - - - - f54d30f6fd3e97f6f4c9a344274dd8fc
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
I have problem that after change of endpoint ip (for example after rollout restart ) my service not accessible from ingress some time, but it accessible inside cluster by servicename. In your case do you do restart,redeploy or whatever like that ?
/close
@longwuyuan: Closing this issue.
What happened:
I got random 503 errors. Its not happen often but it happens during the time. I got these errors from ingress-nginx but the actuall service gives a 200 for the request.
"503 Service Temporarely Unavailable"
What you expected to happen:
As the service behind the ingress is giving a 200 OK, i expect ingress doing the same.
Logs
Ingress:
Application:
Details
NGINX Ingress controller version:
v1.1.1
Kubernetes version:
v1.23.4
Environment:
Single node kubernetes cluster for development purpose. Installed with kubeadm on Ubuntu.
How was the ingress-nginx-controller installed
Installed by yaml from documentation.
Current State of the controller
ingress-class
I dont know why there is a lable "managed by helm" because its definitelly not
ressources in namespace:
describe pod
describe svc
App deployment
Ressources in namespace:
Ingress:
Service:
Deployment:
Endpoint:
In front of the ingress there is an AWS application LB
INFO
I changed some stuff like namings of the software, host, usw....