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.

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

Support Proxy in Ubuntu 22, 24 autoinstall #1541

Open
vignesh-goutham opened this issue Aug 13, 2024 · 4 comments
Open

Support Proxy in Ubuntu 22, 24 autoinstall #1541

vignesh-goutham opened this issue Aug 13, 2024 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@vignesh-goutham
Copy link
Contributor

When image builder is running in an air-gapped proxy available environment, the proxy configs http_proxy, https_proxy & no_proxy overrides are not used on the Ubuntu autoinstall, leading to failed OS install.

Adding proxy variables to the autoinstall should fix this issue.

/kind bug

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 13, 2024
@mohsenkamini
Copy link

If I am not mistaken, the Ubuntu auto install will fail if the VM has an IP address but not internet access(because it runs apt commands and they'll fail). I think we might consider fixing this too.

@sriramandev
Copy link
Contributor

@vignesh-goutham / @mohsenkamini Which provider are we talking about here?

@mohsenkamini
Copy link

mohsenkamini commented Aug 28, 2024

@vignesh-goutham / @mohsenkamini Which provider are we talking about here?

well my case was with prometheus. But I have experienced this issue across ESXi too(not as a provider for image-builder tho). I guess this is the default behaviour of ubuntu installer.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants