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

voyager 5-rc3 non kube-system ingress , error #689

Closed
fvigotti opened this issue Nov 6, 2017 · 3 comments

Comments

Projects
None yet
1 participant
@fvigotti
Copy link

commented Nov 6, 2017

Hi I'm getting error from ingress when gets moved out of kube-system namespaces ( there works fine )

this is the error :

W1106 14:34:51.197146       7 client_config.go:529] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
W1106 14:34:51.197537       7 client_config.go:534] error creating inClusterConfig, falling back to default config: unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined
F1106 14:34:51.197825       7 tlsmounter.go:64] invalid configuration: no configuration has been provided

I've tried to create default kubernetes service in that namespace, bot with clusterIp and externalname but seems to not work ( when kubernetes.$CUSTOMNS..... exists and it's clusterip the error is different, the pods get the env variables but obviously the endpoint is wrong.. )

with this instead, still get the error here above...

kubernetes ExternalName kubernetes.kube-system.svc.cluster.local 443/TCP 3m

any ideas ?

@fvigotti

This comment has been minimized.

Copy link
Author

commented Nov 6, 2017

at the moment I'm no longer able to make configurations for virtualhosts working..
ie : https://github.com/appscode/voyager/blob/master/docs/user-guide/ingress/named-virtual-hosting.md

works only if I select a default backend and redirect everything there.. :(

@fvigotti

This comment has been minimized.

Copy link
Author

commented Nov 6, 2017

ok, I've found that the problems seems to be in NodePort I'm investigating I'll post updates..

@fvigotti

This comment has been minimized.

Copy link
Author

commented Nov 6, 2017

Ok,
I've had to create a
" ingress.appscode.com/type: Internal"
ingress with then a custom service with same selectors of the voyager created ones, but with nodeport-over-externalip and port ( the port must be the same specified in backends in the ingress ) and the ip of the external server

the important part is that
the ingress type must be internal or doesn't work, an alternative is to use the hostport ( which in reality means that voyager run ha hostnetwork: true ( which is a bit ambiguous because hostport means a port redirection in kubernetes not hostnetwork)

thank you,
Francesco

@fvigotti fvigotti closed this Nov 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.