Now why is it not done? Simply because pod have a random ID added to their names at creation (something like: nginx-ingress-1234456) and if it crashes and get recreates the name won't be the same. That applies to stateless apps, you may be able to deduct the name of the pod in a stateful state with only one pod...

kubectl handles locating and authenticating to the API server. If you want to directly access the REST API with an http client like F accepts parameters like -F "name=contents". If you want the contents to be read from a file, use @filename as contents. When specifying a file, you can also specify the file content type by appending ;type= to the file name. You can also post the contents of several files in one field. For example, the field name coolfiles is used to send three files, with different content types using the following syntax: curl -F "[email protected];type=image/gif,fil2.txt,fil3.html"die with it, and the ReplicaSet inside the Deployment will create new ones, with different IPs. This is I am logged into a Kubernetes pod using the following command: ./cluster/kubectl.sh exec my-nginx-0onux -c my-nginx -it bash Note that the HTTP server must have been configured to accept PUT before this can be done successfully. If there is a normal post, you use -d to post. -d takes a full post string, which is in the format =&=&... minikube is executed inside a virtual machine, so the curl 172.17.0.18:8080 would only work from inside that virtual machine.

By default, curl trusts the same set of CAs the underlying operating system does. For instance, on Ubuntu or Debian, the list of trusted CAs can be found at /etc/ssl/certs/ca-certificates.crt. Evidently, minikube doesn't add its certs to this file. context" "fmt" "k8s.io/apimachinery/pkg/apis/meta/v1" "k8s.io/client-go/kubernetes" "k8s.io/client-go/tools/clientcmd" ) Some proxies require special authentication. Specify by using -U as above: curl -U user:passwd -x my-proxy:888 http://www.example.com/Unlike the apparently unprotected /version endpoint, Kubernetes generally restricts access to its API endpoints. If you can’t get any of these images, because you’re perhaps running a cluster which is closed off from the internet, then you could try one of these instead: Store the HTTP headers in a separate file (headers.txt in the example): curl --dump-header headers.txt curl.se Note that using FTPS:// as prefix is the implicit way as described in the standards while the recommended explicit way is done by using FTP:// and the --ssl-reqd option. SFTP / SCP From within the cluster (e.g. via kubectl exec) this pod will also be directly accessible via it's associated pod IP 172.17.0.3: kubectl describe pod sise | grep IP: