kubeflow: in KF0.6.2 IAP GKE install, 'iap-enabler' pod is crash-looping

/kind bug

using KF0.6.2 w/ IAP on GKE.

I see the iap-enabler-* pod continuously crash-looping. Hereโ€™s its logs:

kubectl logs iap-enabler-778889874f-4vrfd -n istio-system
Activated service account credentials for: [kf062test-admin@xxxx.iam.gserviceaccount.com]
[component_manager]
disable_update_check = true
[core]
account = kf062test-admin@xxxx.iam.gserviceaccount.com
disable_usage_reporting = true
project =xxxx
[metrics]
environment = github_docker_image

Your active configuration is: [default]
node port is 31380
fetching backends info with envoy-ingress: {"k8s-be-31380--5810244e269b1626":"HEALTHY","k8s-be-32253--5810244e269b1626":"HEALTHY"}
backend name is k8s-be-31380--5810244e269b1626
Waiting for backend id PROJECT=xxxx NAMESPACE=istio-system SERVICE=istio-ingressgateway filter=name~k8s-be-31380--5810244e269b1626
BACKEND_ID=6347129120648147983
patch JWT audience: /projects/xxxx/global/backendServices/6347129120648147983
policy.authentication.istio.io/ingress-jwt not patched
Clearing lock on service annotation
service/istio-ingressgateway not patched
Fri Aug 30 17:48:10 UTC 2019 WARN: Backend check failed, restarting container.

I saw this w/ both kfctl-based install and using the (staging) c2d webapp.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 7
  • Comments: 16 (10 by maintainers)

Commits related to this issue

Most upvoted comments

Issue-Label Bot is automatically applying the label kind/bug to this issue, with a confidence of 0.80. Please mark this comment with ๐Ÿ‘ or ๐Ÿ‘Ž to give our bot feedback!

Links: app homepage, dashboard and code for this bot.