I’m a noob to AWS so please bear with me, but I’m hoping someone can point out where I’ve messed something up with my setup on AWS. The architecture of the application is: 1 VPC with 2 public + 2 private subnets 1 RDS MySQL database within the same VPC 1 Elasticache Redis store within […]
- Tags "apiVersion":"extensions/v1beta1", "name":"my-app-ingress", "Name":"my-app-ingress"} I0802 06:41:37.739524 1 controller.go:236] kubebuilder/controller "level"=1 "msg"="Successfully Reconciled" ", "Name":"my-app-ingress"} I0802 06:41:38.149869 1 controller.go:236] kubebuilder/controller "level"=1 "msg"="Successfully Reconciled" ", "Name":"my-app-ingress"} My ingress definition I think is ok (worked fine when testing with digital ocean at least) and I've added various a, "Name":"my-app-ingress"} W0802 06:38:42.924349 1 reflector.go:270] pkg/mod/k8s.io/client-go@v0.0.0-20181213151034-8d9ed539ba31/tools/ca, "namespace":"default"}, "resourceVersion":"400603"} "reason"="MODIFY" I0802 05:46:45.440737 1 controller.go:236] kubebuilder/controller "level"=1 "msg"="Succes, "uid":"02ce21a7-fba1-4605-9339-509bf3745538", and got through the guide without any issues, and on the surface things appear to be setup correctly. The ingress controller logs suggest that it's working correctly I0802 05:46:45.1301, but I'm hoping someone can point out where I've messed something up with my setup on AWS. The architecture of the application is: 1 VPC wit, but the browser just terminates immediately giving a "We can't find that site" page but there's not 404 response from the server itself that, can access them directly, can't see any errors anywhere. When I try and connect to my load balancer URL however, I get an immediate failure. No status or anything, I'm a noob to AWS so please bear with me, if I try a ping on the URL it resolves to the IP address that I can find in AWS, is that I haven't yet setup an SSL certificate (haven't got that far). When I try and load the URL in the browser, it does immediately switch it to an https request so it seems as though something somewhere is triggering that switchover, more like it simply can't find the URL. The DNS resolves correctly, or ways of debugging this as I'm a bit lost at this point, PathPatternConfig: { Values: ["/*"] } }] I0802 05:46:45.130576 1 recorder.go:53] kubebuilder/manager/events "level"=1 "msg"="N, PathPatternConfig: { Values: [\"/*\"] } }]" "object"={"kind":"Ingress", so is it possible that the ALB is immediately closing the connection due to there being no certificate setup? Any pointers in the right dire, they're able to communicate with the database/redis correctly so I don't THINK there are any issues in this part of the system. Then I came