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

Busybox image not configurable #13501

Closed
joaquinfll opened this issue Apr 22, 2019 · 3 comments
Closed

Busybox image not configurable #13501

joaquinfll opened this issue Apr 22, 2019 · 3 comments

Comments

@joaquinfll
Copy link

Bug description
The location where busybox is downloaded is not configurable.

Expected behavior
Busybox image should be configurable.

Steps to reproduce the bug
Install Istio with Helm
Prometheus will fail because busybox cannot be downloaded.
Version (include the output of istioctl version --remote and kubectl version)
1.1.3

How was Istio installed?
With Helm
Environment where bug was observed (cloud vendor, OS, etc)

Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

In a restricted environment an internal docker registry is commonly used, having deployments without configurable image values make it not possible to deploy easily.

@sdake
Copy link
Member

sdake commented Apr 23, 2019

Depending on how tidy the change is, this should be considered for backport to the 1.1 series. Not being able to deploy in a firewalled environment is a problem.

@duderino agree?

Cheers
-steve

@sdake sdake added this to the 1.1 milestone Apr 23, 2019
@linsun
Copy link
Member

linsun commented Apr 23, 2019

agreed this should be configurable, most of our images are already configurable, think we missed this one.

@bianpengyuan
Copy link
Contributor

Init container has been removed. so configurability is no longer needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants