ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When I am running the below command to record the change cause - kubectl set image deployment.v1.apps/deploy1 nginx=nginx:1.16.0 --record Then it records the change cause but shows that --record has been deprecated. Flag --record has been deprecated, `--record` will be removed in the future deployment.apps/deploy1 image updated And when I run the command kub
I am trying to deploy a mongo db deployment together with service, as follows: apiVersion: apps/v1 kind: Deployment metadata: name: mongo-deployment labels: app: mongo spec: replicas: 1 selector: matchLabels: app: mongo template: metadata: labels: app: mongo spec: containers: - name: mongo image: mongo:5.0 ports: - containerPort: 27017 env: - name: MONGO_INI
I deployed a helm chart using helm install and after this I want to see if the pods/services/cms related to just this deployment have come up or failed. Is there a way to see this? Using kubectl get pods and greping for the name works but it does not show the services and other resources that got deployed when this helm chart is deployed.
I'm using MicroK8S in Ubuntu. I'm trying to run a simple "hello world" program but I got the error when a pod is created. kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to "Default" policy Here is my deployment.yaml file which I'm trying to apply : apiVersion: v1 kind: Service metadata: name: gr
I need to copy dump data from pod to local. Below the commands I am trying but I am getting error: unexpected EOF kubectl cp device-database-79fc964c8-q7ncc:tmp /Users/raja error: unexpected EOF or kubectl cp device-database-79fc964c8-q7ncc:tmp/plsql_data/prod.dump /Users/raja/prod.dump error: unexpected EOF kubectl version kubectl version --client Client Ve
I am trying to debug a pod with the status "ImagePullBackOff". The pod is in the namespace minio-operator, but when I try to to describe the pod, it is apparently not found. Why does that happen? [psr-admin@zon-psr-2-u001 ~]$ kubectl get all -n minio-operator NAME READY STATUS RESTARTS AGE pod/minio-operator-5dd99dd858-n6fdj 0/1 ImagepullBackoff 0 7d NAME RE
To exec into a container in a pod, I use the following two commands (note the template flag in the first command trims the output to print just the name of the pods): $ kubectl get pods --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}' app-api-6421cdf4fd-x9tbk app-worker-432f86f54-fknxw app-frontend-87dd65d49c-6b4mn app-rabbit-413632c874-s2ptw $
I found specifying like kubectl --context dev --namespace default {other commands} before kubectl client in many examples. Can I get a clear difference between them in a k8's environment?
The command kubectl get pods <POD NAME> will return the specific pod with that name. I wonder if there is a way that I can use part of the name, for instance, a command that returns all pods that start with j .
commented · 09 Jan 2024, 00:22 UTC
kubernetes
docker