Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
JKBGIT1 opened this issue Sep 23, 2024 · 0 comments · Fixed by #1517
Closed

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

JKBGIT1 opened this issue Sep 23, 2024 · 0 comments · Fixed by #1517
Labels
bug Something isn't working

Comments

@JKBGIT1
Copy link
Contributor

JKBGIT1 commented Sep 23, 2024

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
@JKBGIT1 JKBGIT1 added the bug Something isn't working label Sep 23, 2024
@JKBGIT1 JKBGIT1 mentioned this issue Sep 24, 2024
Merged
github-merge-queue bot pushed a commit that referenced this issue Sep 27, 2024
@JKBGIT1
add GCP metadata server IP and hostnames to no proxy envs (#1517)
5ea5c4c 
closes #1514

This supports building K8s clusters with GCP VMs using an HTTP proxy.

When using an HTTP Proxy this
`metadata,metadata.google.internal,169.254.169.254,metadata.google.internal.`
has to be in the no proxy envs. Otherwise Claudie fails to build the k8s
cluster.

This PR also contains an update of `.env` file, cause it should run the
e2e tests with proxy mode turned on and using an HTTP proxy that
supports access to a limited set of domains. Once the e2e tests finish
successfully the changes in the `.env` file will be reverted.

---------

Co-authored-by: CI/CD pipeline <CI/CD-pipeline@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add GCP metadata server IP and hostnames to no proxy envs berops/claudie
1 participant
@JKBGIT1