You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While troubleshooting a chart that depends on patroni, we discovered that Spilo tries to get AWS instance data via a request to http://instance-data/... in one location only (other locations use the IP address 169.254.169.254). This hostname isn't documented or supported by AWS: https://forums.aws.amazon.com/message.jspa?messageID=536813
and in some cases it doesn't work (including ours). We were able to work around by cramming it into our kube DNS server but it would be more consistent to make the request by IP address.
One other note: while reading the current issue list, I noticed #186 and read through the comments. I'm not familiar with how OpenStack is supported but it sounded like they might be relying on the DNS name lookup failure? I'm not sure how fixing this might affect that behavior.
The text was updated successfully, but these errors were encountered:
While troubleshooting a chart that depends on patroni, we discovered that Spilo tries to get AWS instance data via a request to http://instance-data/... in one location only (other locations use the IP address 169.254.169.254). This hostname isn't documented or supported by AWS:
https://forums.aws.amazon.com/message.jspa?messageID=536813
and in some cases it doesn't work (including ours). We were able to work around by cramming it into our kube DNS server but it would be more consistent to make the request by IP address.
One other note: while reading the current issue list, I noticed #186 and read through the comments. I'm not familiar with how OpenStack is supported but it sounded like they might be relying on the DNS name lookup failure? I'm not sure how fixing this might affect that behavior.
The text was updated successfully, but these errors were encountered: