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

[upgrade by operator from 1.5.1 to 1.5.4] svc istio-pilot is missing, istio-ingressgateway Envoy is NOT ready #25237

Closed
pixystone opened this issue Jul 6, 2020 · 2 comments
Labels
area/environments/operator Issues related to Operator or installation lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while

Comments

@pixystone
Copy link

pixystone commented Jul 6, 2020

Bug description

2020-07-06T07:10:22.579428Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected;
 lds updates: 0 successful, 0 rejected

the discovery-address is

--discoveryAddress="istio-pilot.istio-system.svc:15012"

but no svc named istio-pilot in my cluster, it may be chaned to istiod.

$ki get svc
NAME                        TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                                                    AGE
istio-citadel               ClusterIP   None         <none>        8060/TCP,15014/TCP                                         4h39m
istio-ingressgateway        ClusterIP   None         <none>        80/TCP,443/TCP                                             73d
istiod                      ClusterIP   None         <none>        15012/TCP,443/TCP                                          73d
jaeger-agent                ClusterIP   None         <none>        5775/UDP,6831/UDP,6832/UDP                                 73d
jaeger-collector-headless   ClusterIP   None         <none>        14250/TCP                                                  73d
kiali                       ClusterIP   None         <none>        20001/TCP                                                  73d
prometheus                  ClusterIP   None         <none>        9090/TCP                                                   73d

I added a istio-pilot svc to workaround it.

[ ] Configuration Infrastructure
[ ] Docs
[ x ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Expected behavior

Steps to reproduce the bug

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)

How was Istio installed?

Environment where bug was observed (cloud vendor, OS, etc)

@pixystone
Copy link
Author

The root cause may the same as #25235

@pixystone pixystone changed the title [upgrade by operator from 1.5.1 to 1.5.4] istio-ingressgateway Envoy is not Ready [upgrade by operator from 1.5.1 to 1.5.4] svc istio-pilot is missing, istio-ingressgateway Envoy is NOT ready Jul 6, 2020
@esnible esnible added the area/environments/operator Issues related to Operator or installation label Jul 6, 2020
@istio-policy-bot istio-policy-bot added the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Oct 4, 2020
@istio-policy-bot
Copy link

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2020-07-06. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.

@istio-policy-bot istio-policy-bot added the lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. label Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/environments/operator Issues related to Operator or installation lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while
Projects
None yet
Development

No branches or pull requests

3 participants