-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
istioctl kube-inject 0.2.0 references images which do not exist #553
Comments
Done created those 2. |
thanks a lot ! super fast fix ! |
@sebastienvas Can you also create https://hub.docker.com/r/istio/proxy/tags/ 0.2.0? |
@mclarke47 curious, why ? (only proxy_init and proxy_debug are referenced as far as I can tell) |
It's just the non debug version of the debug proxy image I think |
Pushed docker.io/istio/proxy:0.2.0 |
mandarjog
added a commit
to mandarjog/istio
that referenced
this issue
Oct 30, 2017
* add proto parse support for descriptors This enables 1. Use of symbolic enum names. 2. special json encoding for several data types: proto.duration, proto.time have more user friendly json encodings. Former-commit-id: ee56a6084cf888395f5991a4864bbaf238d11662
mandarjog
added a commit
that referenced
this issue
Oct 31, 2017
* add proto parse support for descriptors This enables 1. Use of symbolic enum names. 2. special json encoding for several data types: proto.duration, proto.time have more user friendly json encodings. Former-commit-id: 01545a21df4bc24a4e6d889a9256c7e0b6e1520c
rshriram
pushed a commit
to rshriram/istio
that referenced
this issue
Jul 31, 2018
howardjohn
pushed a commit
to howardjohn/istio
that referenced
this issue
Jan 12, 2020
* Update crd-all.gen.yaml * Fix crd * Remove invalid stuff
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
can we push those images asap (or make a 0.2.1 with working images/kube-inject) ?
(I guess it's somewhat related to, but not a dup of (imo) #538 but somewhat more acute as it's not working at the moment)
The text was updated successfully, but these errors were encountered: