-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the com…
-
Consumers of this module recently received the following email from AWS.
> Hello,
>
> We have observed that your Amazon VPC resources are using a shared NAT Gateway across multiple Availability …
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Community Note
* Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-…
-
It seems that we might have a NAT64 bug.
- Use the docker.gateway.firez.one Gateway on staging
- Try to `ping6` a DNS resource through it.
- Observe `Source not allowed` with an IPv4 address in t…
-
### Is your feature request related to a problem? Please describe.
With the API of NSX it can be possible to create NAT under 3 different categories/sections (INTERNAL, USER and DEFAULT).
https:…
-
Implementing support for Gateway Load Balancer would provide the ability to horizontally scale out fck-nat instances and also simplify some of the HA deployment options.
I have had good experiences…
ozcrn updated
1 month ago
-
### Describe the Bug
It seems AWS no longer offers a NAT instance AMI.
When `nat_instance_enabled=true`, it causes
> Error: Your query returned no results. Please change your search criteria an…
-
{
"platform":"",
"hub-mirror": [
"ghcr.io/openfaas/queue-worker:0.14.1",
"ghcr.io/openfaas/gateway:0.27.5",
"docker.io/prom/prometheus:v2.49.1",
"docker.i…
-
`gateway.gateways` and `leafnodes.remotes` are both lists that support a `tls` block
Also, a server might not need to be listening on the `leafnodes` port in order to have a `leafnodes.remote` bloc…
-
Issue summary:
When creating a nat gateway with nat_ip_allocate_option=AUTO_ONLY, the nat gateway terraform module does not output the ip addresses that were assigned to the nat gateway. Deriving th…