search

berops / claudie

Cloud-agnostic managed Kubernetes
https://docs.claudie.io/
Apache License 2.0
600 stars 41 forks source link

Bug: GCP VMs can't reach their metadata servers when using proxy #1514

Closed JKBGIT1 closed 1 month ago

JKBGIT1 commented 1 month ago

Current Behaviour

Claudie can't utilize a proxy when using the GCP VMs because the proxy server can't reach the GCP metadata servers.

The following logs are from the proxy server.

1727094082.406      0 104.199.110.247 TCP_MISS/502 4066 GET http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/ - HIER_NONE/- text/html
1727094108.056      1 104.199.110.247 TCP_MISS/502 4066 GET http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/ - HIER_NONE/- text/html
1727094159.310      4 104.199.110.247 TCP_MISS/502 4066 GET http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/ - HIER_NONE/- text/html

Expected Behaviour

Add GCP metadata servers to no proxy envs. This way the GCP VMs will succeed in reaching their metadata servers because the requests won't go through the proxy server.

Steps To Reproduce

  1. Turn on the HTTP_PROXY_MODE by setting its value to on
  2. Create a manifest with GCP VM
  3. Apply the manifest and wait for the failure in kube-eleven