To start, it’s useful to note and remember that in Kubernetes, every pod gets its own ip address from 10.*, that is usable only within the cluster. Now, the port-forward feature of kubectl simply tunnels the traffic from a specified port at your local host machine to the specified port on the specified pod. API … Read more
As of release 1.7 Dashboard supports user authentication based on: Authorization: Bearer <token> header passed in every request to Dashboard. Supported from release 1.6. Has the highest priority. If present, login view will not be shown. Bearer Token that can be used on Dashboard login view. Username/password that can be used on Dashboard login view. … Read more
As stated inkubectl help: kubectl cp –help Copy files and directories to and from containers. Examples: # !!!Important Note!!! # Requires that the ‘tar’ binary is present in your container # image. If ‘tar’ is not present, ‘kubectl cp’ will fail. # Copy /tmp/foo_dir local directory to /tmp/bar_dir in a remote pod in the default … Read more
Deployments and ReplicationControllers are meant for stateless usage and are rather lightweight. StatefulSets are used when state has to be persisted. Therefore the latter use volumeClaimTemplates / claims on persistent volumes to ensure they can keep the state across component restarts. So if your application is stateful or if you want to deploy stateful storage … Read more
Is it possible to restart a single container Not through kubectl, although depending on the setup of your cluster you can “cheat” and docker kill the-sha-goes-here, which will cause kubelet to restart the “failed” container (assuming, of course, the restart policy for the Pod says that is what it should do) how do I restart … Read more
For example you have a configmap which contain 2 config files: kubectl create configmap config –from-file <file1> –from-file <file2> You could use subPath like this to mount single file into existing directory: — volumeMounts: – name: “config” mountPath: “/<existing folder>/<file1>” subPath: “<file1>” – name: “config” mountPath: “/<existing folder>/<file2>” subPath: “<file2>” restartPolicy: Always volumes: – name: … Read more
As mentioned in the accepted answer the PR is now merged and you can get pods by node as follows: kubectl get pods –all-namespaces -o wide –field-selector spec.nodeName=<node>
As @Sukumar commented, you need to have your Dockerfile have a Command to run or have your ReplicationController specify a command. The pod is crashing because it starts up then immediately exits, thus Kubernetes restarts and the cycle continues.