Question: and just making it the default backend?

Asked By
Asked At
2018-05-10 19:35:06

Found 15 possible answers.

User Answered At Possible Answer
cmarcano631 2018-05-10 19:35:19 Eyy @dghubble I am trying to use Typhoon(DigitalOcena) + RexRay (BlockStorage) and I have this problem Error dynamically probing plugins: Error creating Flexvolume plugin from directory rexray~flexrex, skipping. Error: unexpected end of JSON input Is better if I try with ?
smerrill 2018-05-10 19:35:56 I think you might be confused about what the default backend is
dghubble 2018-05-10 19:36:52 @cmarcano631 perhaps? There are addons atop the cluster, I haven't tried them all These are probably questions for the plugin providers in question
chancez 2018-05-10 19:37:49 just based on reading that, it's likely you have an empty file that's supposed to contain json my guess is flexvolumes have some kinda json manifest indicating how to invoke it or something
smerrill 2018-05-10 19:38:08 It's the service that will get proxied to if no Ingress rules match the hostname
vexoon 2018-05-10 19:39:20 my kubedns pod sidecar container can not resolve kubernetes.default.svc.cluster.local. and when looking at its resolv.conf I only have 'nameserver & search eu-central-1.compute.internal' in it...all my other pods have ndots 5 and a lot more in the resolv.conf. Anyone willing to explain this to me maybe and how I can solve this? Its giving me issues in the kubedns pod :confused:
chancez 2018-05-10 19:40:10 kubedns itself is what makes kubernetes.default resolve kube-dns should be using a clusterIP to talk to the kubernetes API and that would be why querying inside the pod doesn't resolve.kubernetes.default so it _only_ having the AWS DNS servers in resolv.conf makes sense. so it can forward DNS queries for things it's not authorative for but it's own DNS settings will be the same as the nodes
vexoon 2018-05-10 19:41:48 hm
chancez 2018-05-10 19:42:12 put another way kube-dns is the DNS server that makes kubernetes.default resolve
vexoon 2018-05-10 19:42:29 yes I understand that part :slightly_smiling_face:
chancez 2018-05-10 19:42:33 it doesn't really make sense for it to use itself to resolve that
vexoon 2018-05-10 19:42:51 just wondering how I can fix the sidecar then so I can resolve
chancez 2018-05-10 19:42:53 particularly since it needs to talk to Kube before it has any DNS state determined. it shouldnt' need to use internal DNS names just configure it to use the kuberenetes serviceIP why not use it as a regular deployment or daemonset? why are you running it as a sidecar?
vexoon 2018-05-10 19:43:38 ah no srr, so I have a pod for kubedns the sidecar is failing in the pod there is a kubedns, dnsmasq and a healthz sidecar
chancez 2018-05-10 19:43:57 ok i see what you mean :slightly_smiling_face:

Related Questions