kubed | data visualization DSL embedded within the Kotlin | Data Visualization library

Chris,

I haven't used linode or kong and don't know what your frontend actually does, so I'll just point out what I can see:

• The simplest dns check is to curl (or ping, dig, etc.):

  • http://[dataapi's pod ip]:80 from a host node
  • http://[kong-proxy svc's internal ip]/dataapi/api/values from a host node (or another pod - see below)

• default path matching on nginx ingress controller is pathPrefix, so your nginx ingress with path: / and nginx.ingress.kubernetes.io/rewrite-target: / actually matches everything and rewrites to /. This may not be an issue if you properly specify all your ingresses so they take priority over "/".

• you said 'using a kong ingress as a proxy to redirect incoming', just want to make sure you're proxying (not redirecting the client).

• Is chrome just relaying its upstream error from frontend-service? An external client shouldn't be able to resolve the cluster's urls (unless you've joined your local machine to the cluster's network or done some other fancy trick). By default, dns only works within the cluster.

• cluster dns generally follows [service name].[namespace name].svc.cluster.local. If dns cluster dns is working, then using curl, ping, wget, etc. from a pod in the cluster and pointing it to that svc will send it to the cluster svc ip, not an external ip.

• is your dataapi service configured to respond to /dataapi/api/values or does it not care what the uri is?

If you don't have any network policies restricting traffic within a namespace, you should be able to create a test pod in the same namespace, and curl the service dns and the pod ip's directly:

The answer is that

Both assumptions are correct.

It's running in a VM, a VM which is running in your PC and exposing the Kubernetes API so that you can access it with kubectl without needing to get into the VM.

There could be plenty of reasons for that. You may just need to:

LoadBalancer type service internally creates NodePort. So you can access it via http://NODEIP:31578 where 31578 is the NodePort as you can see in output of kubectl get service. To get NODEIP you can use kubectl get nodes -o wide

If you look at the output of minikube service hello-node it's has got the same NODEIP and NODEPORT. Unfortunately there is no equivalent command in kind and so you need to use the method described above.

EXTERNAL-IP will be pending because there is no cloud(AWS, GCP, Azure) like implementation in local kind cluster. If you really want to make LoadBalancer type service work you can use metallb as loadbalancer implementation. In this way you will have EXTERNAL-IP assigned instead of pending and you can use that IP to access the pod.

Here is a guide on how to make metallb with kind work.

I have uninstalled and re-installed Kubernetes version - v1.19.0 Now everything working fine. Thanks.

export KUBERNETES_MASTER=http://MasterIP:8080 is not correct because the port should be 6443 and protocol should be https for external connection coming to Kubernetes API Server.

Don't know which tutorial you are following and not sure how you created the pod but if it worked for them and it doesn't work for you then the issue is probably in that you are running newer version of kubernetes.

Using kubectl run ... used to create pod as well as replication controller. Nowadays (since 1.18) it only creates a single pod. You need either replication controller (deprecated), or relicaset or deployment in order to scale it. You can't scale a single pod (pod resource doesn't have a concept of replicas that you might scale - increase/decrease).

You can replace the old run command with