search

jenkins-x / exposecontroller-service

A long running service for using exposecontroller in development or your Edit environment
Apache License 2.0
0 stars 3 forks source link

errors for new dev environment #1

Open mataerial opened 6 years ago

mataerial commented 6 years ago

After creating a new dev environment the exposecontroller is in a crash loop:

I0828 00:48:32.736226       1 exposecontroller.go:60] Using build: '2.3.70'
I0828 00:48:32.785312       1 config.go:22] No /etc/exposecontroller/config.yml file found.  Will try to figure out defaults
W0828 00:48:32.785366       1 exposecontroller.go:81] %!s(<nil>)
W0828 00:48:32.787346       1 exposecontroller.go:98] Could not find ConfigMap exposecontroller in namespace jx-edit-mattmor2
I0828 00:48:32.787606       1 exposecontroller.go:103] Config file before overrides exposer: ""
path-mode: ""
apiserver-protocol: ""
watch-namespaces: ""
watch-current-namespace: false
http: false
tls-acme: false
I0828 00:48:32.787763       1 exposecontroller.go:133] Config file after overrides exposer: ""
path-mode: ""
apiserver-protocol: ""
watch-namespaces: ""
watch-current-namespace: true
http: false
tls-acme: false
I0828 00:48:32.787781       1 exposecontroller.go:165] Watching services in namespaces: `jx-edit-mattmor2`
I0828 00:48:32.787933       1 controller.go:78] NewController false
I0828 00:48:32.809603       1 auto.go:32] Using exposer strategy: ingress
F0828 00:48:32.834721       1 exposecontroller.go:169] failed to create new strategy: failed to create auto expose strategy: failed to get a domain: failed to find any nodes: nodes is forbidden: User "system:serviceaccount:jx-edit-mattmor2:exposecontroller-service" cannot list nodes at the cluster scope: Unknown user "system:serviceaccount:jx-edit-mattmor2:exposecontroller-service"

Does it need a ClusterRoleBinding instead of RoleBinding?

helm list --namespace jx-edit-mattmor2
NAME                REVISION    UPDATED                     STATUS      CHART                           APP VERSION NAMESPACE
jx-edit-mattmor2-es 4           Tue Aug 28 12:42:35 2018    DEPLOYED    exposecontroller-service-1.0.4              jx-edit-mattmor2
jenkins-x-bot commented 5 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

iftachsc commented 4 years ago

hitting this as well when setting custom expose.config.urltemplate

jenkins-x-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale