Closed lsambolino closed 1 year ago
Is that the entire pod log? It looks like a piece of Ambassador died early on, and that's what would be helpful to see...
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Closing this issue. If it persists on newer versions 2.x or 3.x please feel free to reopen.
Describe the bug When trying to deploy Ambassador Edge Stack 1.4.2 via Kubernetes YAML on a Kubernetes v1.13, the ambassador pod refuses to start showing __Connection _refused_ error.
To Reproduce
Expected behavior The ambassador pods should be deployed and go in Running state with no issues.
Versions:
Additional context
YAMLs: aes142-crds.yaml:
aes142.yaml:
The output of applying the original YAMLs is:
The log of ambassador pod is: