Serving: helloworld-go IngressNotConfigured, Ingress has not yet been reconciled

[lpwwd]

helloworld-go status is Unknown:

App helloworld-go doesn't work, why?

kubectl get ksvc helloworld-go -o yaml

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"serving.knative.dev/v1","kind":"Service","metadata":{"annotations":{},"name":"helloworld-go","namespace":"default"},"spec":{"template":{"spec":{"containers":[{"env":[{"name":"TARGET","value":"Go Sample v2"}],"image":"gcr.io/knative-samples/helloworld-go"}]}}}}
serving.knative.dev/creator: admin
serving.knative.dev/lastModifier: admin
creationTimestamp: "2019-12-27T07:54:35Z"
generation: 1
name: helloworld-go
namespace: default
resourceVersion: "5149808"
selfLink: /apis/serving.knative.dev/v1/namespaces/default/services/helloworld-go
uid: fa393276-fa0a-4f8d-b5e8-ef39186b1a31
spec:
template:
metadata:
creationTimestamp: null
spec:
containerConcurrency: 0
containers:
- env:
- name: TARGET
value: Go Sample v2
image: gcr.io/knative-samples/helloworld-go
name: user-container
readinessProbe:
successThreshold: 1
tcpSocket:
port: 0
resources: {}
timeoutSeconds: 300
traffic:
- latestRevision: true
percent: 100
status:
address:
url: http://helloworld-go.default.svc.k8s.local
conditions:
- lastTransitionTime: "2019-12-27T07:54:40Z"
status: "True"
type: ConfigurationsReady
- lastTransitionTime: "2019-12-27T07:54:40Z"
message: Ingress has not yet been reconciled.
reason: IngressNotConfigured
status: Unknown
type: Ready
- lastTransitionTime: "2019-12-27T07:54:40Z"
message: Ingress has not yet been reconciled.
reason: IngressNotConfigured
status: Unknown
type: RoutesReady
latestCreatedRevisionName: helloworld-go-s4zrx
latestReadyRevisionName: helloworld-go-s4zrx
observedGeneration: 1
traffic:
- latestRevision: true
percent: 100
revisionName: helloworld-go-s4zrx
url: http://helloworld-go.default.svc.k8s.local

[daisy-ycguo]

@lpwwd
Please use the latest version of Knative and try again.

The Knative Installation Guide in doc uses Knative 0.9.0. We are now on Knative 0.11.0.

You can change 0.9.0 to 0.11.0 when you are installing Knative and try again.

[lpwwd]

@lpwwd
Please use the latest version of Knative and try again.

The Knative Installation Guide in doc uses Knative 0.9.0. We are now on Knative 0.11.0.

You can change 0.9.0 to 0.11.0 when you are installing Knative and try again.

I am using Knative v0.11.0.

[qhh0205]

@lpwwd @daisy-ycguo I have the same issue, the knative version is latest, does the problem solved? I am confused!

[richard2006]

I have the same issue, and descirbe the ingress, the event like this :

Type     Reason          Age                 From                Message
  ----     ------          ----                ----                -------
  Normal   Created         22s                 ingress-controller  Created VirtualService "meteor-cloud-gateway1-mesh"
  Normal   Created         22s                 ingress-controller  Created VirtualService "meteor-cloud-gateway1"
  Normal   Updated         22s (x2 over 22s)   ingress-controller  Updated status for Ingress "meteor-cloud-gateway1"
  Warning  InternalError   20s (x10 over 22s)  ingress-controller  failed to create VirtualService: virtualservices.networking.istio.io "meteor-cloud-gateway1-mesh" already exists
  Warning  CreationFailed  18s (x11 over 22s)  ingress-controller  Failed to create VirtualService meteor/meteor-cloud-gateway1-mesh: virtualservices.networking.istio.io "meteor-cloud-gateway1-mesh" already exists

[vagababov]

is this solved by https://github.com/knative/serving/pull/6509
/cc @ZhiminXiang

[sxmon]

The problem still happens in v0.12.0

[zhangtbj]

Hi all,
Does anyone try to install the latest master branch Knative serving with Istio 1.3.8 or 1.4.x ?

The Istio 1.2.2 works fine with the latest master branch of Knative serving, but when I switched the Istio to 1.3.8 or 1.4.x, all created ksvc became IngressNotConfigured status:

config-map-volume-jtcmrwak               http://config-map-volume-jtcmrwak.serving-tests.example.com               config-map-volume-jtcmrwak-4h7bm                 config-map-volume-jtcmrwak-4h7bm                 Unknown   IngressNotConfigured
projected-config-map-volume-hgviclqr     http://projected-config-map-volume-hgviclqr.serving-tests.example.com     projected-config-map-volume-hgviclqr-hjs2k       projected-config-map-volume-hgviclqr-hjs2k       Unknown   IngressNotConfigured
projected-secret-volume-apgapaie         http://projected-secret-volume-apgapaie.serving-tests.example.com         projected-secret-volume-apgapaie-pr45n           projected-secret-volume-apgapaie-pr45n           Unknown   IngressNotConfigured

But I can still access them well and the pods are running correctly:

✔ $ kubectl get ksvc
NAME   URL                                                                                                                  LATESTCREATED   LATESTREADY    READY     REASON
echo   http://echo-default.coligoserving-193911-f891c22e52f4c0e385707f50c191a2c4-0000.us-south.containers.appdomain.cloud   echo-cgdrx-1    echo-cgdrx-1   Unknown   IngressNotConfigured

✔ $ curl http://echo-default.coligoserving-193911-f891c22e52f4c0e385707f50c191a2c4-0000.us-south.containers.appdomain.cloud
Hello World!

I tried on both kube 1.15 and 1.16, the failures are the same.

I didin't find any useful debug info, this is the ksvc status:

Status:
  Address:
    URL:  http://echo.default.svc.cluster.local
  Conditions:
    Last Transition Time:        2020-02-25T10:12:57Z
    Status:                      True
    Type:                        ConfigurationsReady
    Last Transition Time:        2020-02-25T10:12:58Z
    Message:                     Ingress has not yet been reconciled.
    Reason:                      IngressNotConfigured
    Status:                      Unknown
    Type:                        Ready
    Last Transition Time:        2020-02-25T10:12:58Z
    Message:                     Ingress has not yet been reconciled.
    Reason:                      IngressNotConfigured
    Status:                      Unknown
    Type:                        RoutesReady

If I change back to Istio 1.2.2 or the change back to the official knative serving v0.12.1 release. it works!!!

So I don't know if there is any change in the latest master branch, Does anyone can help me?

Thanks a lot!!

[tcnghia]

/assign @tcnghia

[tcnghia]

@zhangtbj can you please reach out on Slack (knative.slack.com)? I'd like to poke around the cluster a bit to see if we can dig up some useful information for root cause.

[JCzz]

I can confirm: this is still an issue on knative v0.12, Istio 1., k8s 1.15

Please help on this as it is probably cascading: https://github.com/knative/serving/issues/7035

[zhangtbj]

Hi @tcnghia and all,

I have solved by problem by using the latest cluster-local config in the thrid-party/istio-1.4.4 folder.

The solution is in the issue:
https://github.com/knative/serving/issues/7005

Thanks!