While using kubectl port-forward function I was able to succeed in port forwarding a local port to a remote port. However it seems that after a few minutes idling the connection is dropped. Not sure why that is so.

Here is the command used to portforward:

    kubectl --namespace somenamespace port-forward somepodname 50051:50051

Error message:

    Forwarding from 127.0.0.1:50051 -&gt; 50051
    Forwarding from [::1]:50051 -&gt; 50051
    E1125 17:18:55.723715    9940 portforward.go:178] lost connection to pod

Was hoping to be able to keep the connection up

kubectl port forwarding timeout issue

When deploying a service via a Helm Chart, the installation failed because the `tiller` serviceaccount was not allowed to create a `ServiceMonitor` resource.

Note:

 - `ServiceMonitor` is a CRD defined by the Prometheus Operator to automagically get metrics of running containers in Pods.
 - Helm Tiller is installed in a single namespace and the RBAC has been setup using Role and RoleBinding.

I wanted to verify the permissions of the `tiller` serviceaccount.  
`kubectl` has the `auth can-i` command, queries like these (see below) always return `no`.

 - `kubectl auth can-i list deployment --as=tiller`
 - `kubectl auth can-i list deployment --as=staging:tiller`

What is the proper way to check permissions for a serviceaccount?  
How to enable the `tiller` account to create a ServiceMonitor resource?

Kubernetes check serviceaccount permissions

I am learning Kubernetes recently, and I am not very clear about the difference between &quot;kubectl apply&quot; and &quot;kubectl replace&quot;. Is there any situation that we can only use one of them?

What is the difference between kubectl apply and kubectl replace

I am trying to install several GCP components from the [gcloud command-line tool](https://cloud.google.com/sdk/gcloud) and always get the same error:

    $ gcloud components list
    
    Your current Cloud SDK version is: 146.0.0
    The latest available version is: 146.0.0
    
    ┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
    │                                                  Components                                                 │
    ├───────────────┬──────────────────────────────────────────────────────┬──────────────────────────┬───────────┤
    │     Status    │                         Name                         │            ID            │    Size   │
    ├───────────────┼──────────────────────────────────────────────────────┼──────────────────────────┼───────────┤
    │ Not Installed │ App Engine Go Extensions                             │ app-engine-go            │  47.9 MiB │
    │ Not Installed │ Bigtable Command Line Tool                           │ cbt                      │   3.8 MiB │
    │ Not Installed │ Cloud Datalab Command Line Tool                      │ datalab                  │   &lt; 1 MiB │
    │ Not Installed │ Cloud Datastore Emulator                             │ cloud-datastore-emulator │  15.4 MiB │
    │ Not Installed │ Cloud Datastore Emulator (Legacy)                    │ gcd-emulator             │  38.1 MiB │
    │ Not Installed │ Cloud Pub/Sub Emulator                               │ pubsub-emulator          │  21.0 MiB │
    │ Not Installed │ Google Container Registry&#39;s Docker credential helper │ docker-credential-gcr    │   3.3 MiB │
    │ Not Installed │ gcloud app Java Extensions                           │ app-engine-java          │ 128.3 MiB │
    │ Not Installed │ gcloud app Python Extensions                         │ app-engine-python        │   7.2 MiB │
    │ Not Installed │ kubectl                                              │ kubectl                  │  11.5 MiB │
    │ Installed     │ BigQuery Command Line Tool                           │ bq                       │   &lt; 1 MiB │
    │ Installed     │ Cloud SDK Core Libraries                             │ core                     │   5.7 MiB │
    │ Installed     │ Cloud Storage Command Line Tool                      │ gsutil                   │   2.8 MiB │
    │ Installed     │ Default set of gcloud commands                       │ gcloud                   │           │
    │ Installed     │ gcloud Alpha Commands                                │ alpha                    │   &lt; 1 MiB │
    │ Installed     │ gcloud Beta Commands                                 │ beta                     │   &lt; 1 MiB │
    └───────────────┴──────────────────────────────────────────────────────┴──────────────────────────┴───────────┘
    
Then attempting to install [kubectl](https://kubernetes.io/docs/reference/kubectl/overview/)

    $ gcloud components install kubectl

    You cannot perform this action because this Cloud SDK installation is 
    managed by an external package manager.  If you would like to get the 
    latest version, please see our main download page at:
    https://cloud.google.com/sdk/
    ERROR: (gcloud.components.install) The component manager is disabled for this installation

Any idea why is this error raised?

Install Google Cloud components error from gcloud command

i&#39;m getting an error when running kubectl one one machine (windows)

the k8s cluster is running on CentOs 7 kubernetes cluster 1.7
master, worker

Here&#39;s my .kube\config

&lt;pre&gt;
  &lt;code&gt;
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: REDACTED
    server: https://10.10.12.7:6443
  name: kubernetes
contexts:
- context:
    cluster: kubernetes
    user: system:node:localhost.localdomain
  name: system:node:localhost.localdomain@kubernetes
current-context: system:node:localhost.localdomain@kubernetes
kind: Config
preferences: {}
users:
- name: system:node:localhost.localdomain
  user:
    client-certificate-data: REDACTED
    client-key-data: REDACTED
  &lt;/code&gt;
&lt;/pre&gt;

the cluster is built using kubeadm with the default certificates on the pki directory

kubectl unable to connect to server: x509: certificate signed by unknown authority


kubectl unable to connect to server: x509: certificate signed by unknown authority

I need to print only specific fields of Kubernetes Events, sorted by a specific field. 

This is to help me gather telemetry and analytics about my namespace 

How could I do that?

What kubectl command can I use to get events sorted by specific fields and print only specific details of events?

I executed the following command:  `% kubectl get service`

It returned this list of services that were created at one point in time with kubectl:  

    NAME                     CLUSTER-IP   EXTERNAL-IP   PORT(S)                         AGE
    car-example-service      10.0.0.129   &lt;nodes&gt;       8025:31564/TCP,1025:31764/TCP   10h
    circle-example-service   10.0.0.48    &lt;nodes&gt;       9000:30362/TCP                  9h
    demo-service             10.0.0.9     &lt;nodes&gt;       8025:30696/TCP,1025:32047/TCP   10h
    example-servic           10.0.0.168   &lt;nodes&gt;       8080:30231/TCP                  1d
    example-service          10.0.0.68    &lt;nodes&gt;       8080:32308/TCP                  1d
    example-service2         10.0.0.184   &lt;nodes&gt;       9000:32727/TCP                  13h
    example-webservice       10.0.0.35    &lt;nodes&gt;       9000:32256/TCP                  1d
    hello-node               10.0.0.224   &lt;pending&gt;     8080:32393/TCP                  120d
    kubernetes               10.0.0.1     &lt;none&gt;        443/TCP                         120d
    mouse-example-service    10.0.0.40    &lt;nodes&gt;       9000:30189/TCP                  9h
    spring-boot-web          10.0.0.171   &lt;nodes&gt;       8080:32311/TCP                  9h
    spring-boot-web-purple   10.0.0.42    &lt;nodes&gt;       8080:31740/TCP                  9h

I no longer want any of these services listed, because when I list resources:
`% kubectl get rs`

I am expecting that I only see the spring-boot-web resource listed.

    NAME                         DESIRED   CURRENT   READY     AGE
    spring-boot-web-1175758536   1         1         0         18m

Please help clarify why I am seeing services that are listed , when the resources only show 1 resource.




how to delete kubectl service

I&#39;m using `kubectl run` with environment parameters to create temporary docker containers for me (e.g. some forwarding for debugging purposes).
Since several weeks `kubectl` is complaining about `kubectl run` being deprecated. Unfortunately I can&#39;t find an appropriate replacement.

This is the old command:

    $KUBECTL run -i -t --attach=false --image djfaze/port-forward --env=&quot;REMOTE_HOST=$REMOTE_HOST&quot; --env=&quot;REMOTE_PORT=$REMOTE_PORT&quot; $POD_NAME

When issuing this, `kubectl` complains with this message:

&gt;`kubectl run --generator=deployment/apps.v1beta1` is DEPRECATED and will be removed in a future version. Use kubectl create instead.

Any ideas how to replace this run command?

kubectl run is deprecated - looking for alternative

`kubectl get` command has this flag `-o` to format the output.

Is there a similar way to format the output of the `kubectl describe` command?

For example:

    kubectl describe -o=&quot;jsonpath={...}&quot; pods my-rc

would print a JSON format for the list of pods in `my-rc` replication controller. But `-o` is not accepted for the `describe` command.

How to format the output of kubectl describe to JSON

I have started pods with command

```shell
$ kubectl run busybox \
--image=busybox \
--restart=Never \
--tty \
-i \
--generator=run-pod/v1
```

Something went wrong, and now I can&#39;t delete this `Pod`.

I tried using the methods described below but the `Pod` keeps being recreated.

```shell
$ kubectl delete pods  busybox-na3tm
pod &quot;busybox-na3tm&quot; deleted

$ kubectl get pods
NAME                                     READY     STATUS              RESTARTS   AGE
busybox-vlzh3                            0/1       ContainerCreating   0          14s

$ kubectl delete pod busybox-vlzh3 --grace-period=0

$ kubectl delete pods --all
pod &quot;busybox-131cq&quot; deleted
pod &quot;busybox-136x9&quot; deleted
pod &quot;busybox-13f8a&quot; deleted
pod &quot;busybox-13svg&quot; deleted
pod &quot;busybox-1465m&quot; deleted
pod &quot;busybox-14uz1&quot; deleted
pod &quot;busybox-15raj&quot; deleted
pod &quot;busybox-160to&quot; deleted
pod &quot;busybox-16191&quot; deleted

$ kubectl get pods --all-namespaces
NAMESPACE   NAME            READY     STATUS              RESTARTS   AGE
default     busybox-c9rnx   0/1       RunContainerError   0          23s
```


Kubernetes pod gets recreated when deleted

I have a pod `test-1495806908-xn5jn` with 2 containers. I&#39;d like to restart one of them called `container-test`. Is it possible to restart a single container within a pod and how? If not, how do I restart the pod?

The pod was created using a `deployment.yaml` with:

    kubectl create -f deployment.yaml



Restart container within pod

`kubectl config view` shows contexts and clusters corresponding to clusters that I have deleted.

How can I remove those entries?

The command

    kubectl config unset clusters

appears to delete all clusters. Is there a way to selectively delete cluster entries? What about contexts?

Kubernetes: How do I delete clusters and contexts from kubectl config?

Reading the [Kubernets documentation][1] it looks to be possible to select a certain range of pods based on labels. I want to select all the pods on one node but I don&#39;t want to label each pod on their corresponding node.

Am I missing something from the documentation or is it just not possible to select by node?

If I do:

```lang-shell
kubectl get pods \
--output=wide
--namespace=$NS \
--server=$SERVER | head

#=&gt;

NAME   READY     STATUS             RESTARTS   AGE       NODE
```

Can any of these headers be used as selector? If yes, how to do it with `kubectl`?  How to do it with the API?


[1]: http://kubernetes.io/docs/user-guide/labels/#selecting-sets-of-nodes

Kubernetes API - Get Pods on Specific Nodes

    kubectl logs &lt;pod-id&gt;

gets latest logs from my deployment - I am working on a bug and interested to know the logs at runtime - How can I get continuous stream of logs ?

edit: corrected question at the end.

kubectl logs - continuously

I&#39;ve created a secret using

```lang-shell
kubectl create secret generic production-tls \
  --from-file=./tls.key \
  --from-file=./tls.crt
```

If I&#39;d like to update the values - how can I do this?


How can I update a secret on Kubernetes when it is generated from a file?

`kubectl` exposes commands that can be used to create a Service for an application and assigns an IP address to access it from internet.

As far as I understand, to access any application within Kubernetes cluster there should be a Service resource created and that should have an IP address which is accessible from an external network.

But in case of `port-forward` how does `kubectl` create a connection to the application without an IP address which is accessible externally?

How kubectl port-forward works?

I can sort my Kubernetes pods by name using:

    kubectl get pods --sort-by=.metadata.name

How can I sort them (or other resoures) by age using `kubectl`?

Kubernetes sort pods by age

I would like to see all resources in a namespace.

Doing `kubectl get all` will, despite of the name, not list things like services and ingresses.

If I know the the type I can explicitly ask for that particular type, but it seems there is also no command for listing all possible types. (Especially `kubectl get` does for example not list custom types).

Any idea how to show all resources before for example deleting that namespace?


Listing all resources in a namespace

I have followed the helloword tutorial on http://kubernetes.io/docs/hellonode/. 

When I run:

    kubectl run hello-node --image=gcr.io/PROJECT_ID/hello-node:v1 --port=8080

I get: 

&gt; The connection to the server localhost:8080 was refused - did you specify the right host or port?

Why does the command line try to connect to the localhost? 

did you specify the right host or port? error on Kubernetes

I had the below YAML for my Ingress and it worked (and continues to work):

```yaml
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  namespace: test-layer
annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - host: mylocalhost.com
      http:
        paths:
          - path: /
            backend:
              serviceName: test-app
              servicePort: 5000
```

However, it tells me that it&#39;s deprecated and I should change to using `networking.k8s.io/v1`. When I do that (see below) it throws an error.

```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: test-ingress
  namespace: test-layer
annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - host: mylocalhost.com
      http:
        paths:
          - path: /
            backend:
              serviceName: test-app
              servicePort: 5000
```

**ERROR**
```
error: error validating &quot;test-ingress.yaml&quot;: 
  error validating data: [ValidationError(Ingress.spec.rules[0].http.paths[0].backend): 
    unknown field &quot;serviceName&quot; in io.k8s.api.networking.v1.IngressBackend, 
    ValidationError(Ingress.spec.rules[0].http.paths[0].backend): 
      unknown field &quot;servicePort&quot; in io.k8s.api.networking.v1.IngressBackend]; 
      if you choose to ignore these errors, turn validation off with --validate=false
```

Other than changing the API version, I made no other changes.

`kubectl version` returns:

```
Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;19&quot;, GitVersion:&quot;v1.19.0&quot;, GitCommit:&quot;e19964183377d0ec2052d1f1fa930c4d7575bd50&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2020-08-26T14:30:33Z&quot;, GoVersion:&quot;go1.15&quot;, Compiler:&quot;gc&quot;, Platform:&quot;windows/amd64&quot;}

Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;19&quot;, GitVersion:&quot;v1.19.0&quot;, GitCommit:&quot;e19964183377d0ec2052d1f1fa930c4d7575bd50&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2020-08-26T14:23:04Z&quot;, GoVersion:&quot;go1.15&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
```

Get error &quot;unknown field &quot;serviceName&quot; in io.k8s.api.networking.v1.IngressBackend&quot; when switch from v1beta1 to v1 in Kubernetes Ingress

I have my deployment.yaml file within the templates directory of Helm charts with several environment variables for the container I will be running using Helm.

Now I want to be able to pull the environment variables locally from whatever machine the helm is ran so I can hide the secrets that way.

How do I pass this in and have helm grab the environment variables locally when I use Helm to run the application?

Here is some part of my deployment.yaml file

    ...
    ...
        spec:
          restartPolicy: Always
          containers:
            - name: sample-app
              image: &quot;sample-app:latest&quot;
              imagePullPolicy: Always
              env:          
                - name: &quot;USERNAME&quot;
                  value: &quot;app-username&quot;
                - name: &quot;PASSWORD&quot;
                  value: &quot;28sin47dsk9ik&quot;
    ...
    ...


How can I pull the value of USERNAME and PASSWORD from local environment variables when I run helm?

Is this possible? If yes, then how do I do this?


How to pull environment variables with Helm charts

When I run `kubectl -n abc-namespace describe pod my-pod-zl6m6`, I get a lot of information about the pod along with the Events in the end. 

Is there a way to output just the Events of the pod either using `kubectl describe` or `kubectl get` commands?

kubectl get events only for a pod

Let say I want to find the kubelet and apiserver version of my k8s master(s), what&#39;s the best way to do it?

I am aware of the following commands:

    kubectl cluster-info

which only shows the endpoints.

    kubectl get nodes; kubectl describe node &lt;node&gt;;

which shows very detail information but only the nodes and not master.

There&#39;s also

    kubectl version

but that only shows the kubectl version and not the kubelet or apiserver version.

What other commands can I use to identify the properties of my cluster?

What is command to find detailed information about Kubernetes master(s) using kubectl?

I&#39;m looking for a way to tell (from within a script) when a Kubernetes Job has completed. I want to then get the logs out of the containers and perform cleanup. 

What would be a good way to do this? Would the best way be to run `kubectl describe job &lt;job_name&gt;` and grep for `1 Succeeded` or something of the sort?

Tell when Job is Complete

`kubectl logs -f pod` shows all logs from the beginning and it becomes a problem when the log is huge and we have to wait for a few minutes to get the last log. Its become more worst when connecting remotely. Is there a way that we can tail the logs for the last 100 lines of logs and follow them?

Tailing few lines from huge logs of kubectl logs -f

What I understood by the documentation is that:

 * ```shell
   kubectl create
   ```
   Creates a new k8s resource in the cluster
 * ```shell
   kubectl replace
   ```
   Updates a resource in the live cluster
 * ```shell
   kubectl apply
   ```
   If I want to do create + replace (_[Reference][1]_)

**My questions are**

1. Why are there three operations for doing the same task in a cluster?
2. What are the use cases for these operations?
3. How do they differ from each other under the hood? 

[1]: https://kubernetes.io/docs/user-guide/kubectl-overview/

kubectl apply vs kubectl create?

my question is simple.

How to execute a bash command in the pod? I want to do everything with one bash command?

    [root@master ~]# kubectl exec -it --namespace=&quot;tools&quot; mongo-pod --bash -c &quot;mongo&quot;
    Error: unknown flag: --bash

So, the command is simply ignored.

    [root@master ~]# kubectl exec -it --namespace=&quot;tools&quot; mongo-pod bash -c &quot;mongo&quot;
    root@mongo-deployment-78c87cb84-jkgxx:/# 

Or so.

    [root@master ~]# kubectl exec -it --namespace=&quot;tools&quot; mongo-pod bash mongo
    Defaulting container name to mongo.
    Use &#39;kubectl describe pod/mongo-deployment-78c87cb84-jkgxx -n tools&#39; to see all of the containers in this pod.
    /usr/bin/mongo: /usr/bin/mongo: cannot execute binary file
    command terminated with exit code 126

If it&#39;s just a bash, it certainly works. But I want to jump into the mongo shell immediatelly.

I found a solution, but it does not work. Tell me if this is possible now? 
https://stackoverflow.com/questions/43499313/executing-multiple-commands-or-from-a-shell-script-in-a-kubernetes-pod


Thanks.

Execute bash command in pod with kubectl?

I&#39;m following that tutorial (https://www.baeldung.com/spring-boot-minikube)
I want to create Kubernetes deployment in yaml file (simple-crud-dpl.yaml):

```
apiVersion: apps/v1
kind: Deployment
metadata:
  name: simple-crud
spec:
  selector:
      matchLabels:
        app: simple-crud
  replicas: 3
  template:
    metadata:
      labels:
        app: simple-crud
    spec:
      containers:
        - name: simple-crud
          image: simple-crud:latest
          imagePullPolicy: Never
          ports:
            - containerPort: 8080
```

but when I run ```kubectl create -f simple-crud-dpl.yaml``` i got:
```error: SchemaError(io.k8s.api.autoscaling.v2beta2.MetricTarget): invalid object doesn&#39;t have additional properties```

I&#39;m using the newest version of kubectl: 
```
kubectl version
Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;10&quot;, GitVersion:&quot;v1.10.11&quot;, GitCommit:&quot;637c7e288581ee40ab4ca210618a89a555b6e7e9&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2018-11-26T14:38:32Z&quot;, GoVersion:&quot;go1.9.3&quot;, Compiler:&quot;gc&quot;, Platform:&quot;darwin/amd64&quot;}
Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;14&quot;, GitVersion:&quot;v1.14.0&quot;, GitCommit:&quot;641856db18352033a0d96dbc99153fa3b27298e5&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2019-03-25T15:45:25Z&quot;, GoVersion:&quot;go1.12.1&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
```

I&#39;m also using minikube locally as it&#39;s described in tutorial. Everything is working till deployment and service. I&#39;m not able to do it.

Kubernetes create deployment unexpected SchemaError

I&#39;ve created a Kubernetes cluster on AWS with [kops](https://github.com/kubernetes/kops) and can successfully administer it via `kubectl` from my local machine.

I can view the current config with `kubectl config view` as well as directly access the stored state at `~/.kube/config`, such as:


    apiVersion: v1
    clusters:
    - cluster:
        certificate-authority-data: REDACTED
        server: https://api.{CLUSTER_NAME}
      name: {CLUSTER_NAME}
    contexts:
    - context:
        cluster: {CLUSTER_NAME}
        user: {CLUSTER_NAME}
      name: {CLUSTER_NAME}
    current-context: {CLUSTER_NAME}
    kind: Config
    preferences: {}
    users:
    - name: {CLUSTER_NAME}
      user:
        client-certificate-data: REDACTED
        client-key-data: REDACTED
        password: REDACTED
        username: admin
    - name: {CLUSTER_NAME}-basic-auth
      user:
        password: REDACTED
        username: admin


I need to enable other users to also administer. This [user guide](https://kubernetes.io/docs/user-guide/sharing-clusters/) describes how to define these on another users machine, but doesn&#39;t describe how to actually create the user&#39;s credentials within the cluster itself. How do you do this?

Also, is it safe to just share the `cluster.certificate-authority-data`?


How to Add Users to Kubernetes (kubectl)?

I have an admin.conf file containing info about a cluster, so that the following command works fine:

    kubectl --kubeconfig ./admin.conf get nodes

How can I `config` kubectl to use the cluster, user and authentication from this file as default in one command? I only see separate set-cluster, set-credentials, set-context, use-context etc. I want to get the same output when I simply run:

    kubectl get nodes


How to configure kubectl with cluster information from a .conf file?

I&#39;m trying to install a helm package on a kubernetes cluster which allegedly has RBAC disabled.
I&#39;m getting a permission error mentioning `clusterroles.rbac.authorization.k8s.io`, which is what I&#39;d expect if RBAC was *enabled*.

Is there a way to check with `kubectl` whether RBAC really is disabled?

What I&#39;ve tried:

* `kubectl describe nodes --all-namespaces | grep -i rbac` : nothing comes up
* `kubectl describe rbac --all-namespaces | grep -i rbac` : nothing comes up
* `kubectl config get-contexts | grep -i rbac` : nothing comes up
* `k get clusterroles` it says &quot;No resources found&quot;, not an error message. So does that mean that RBAC *is* enabled?
* `kuebctl describe cluster` isn&#39;t a thing

I&#39;m aware that maybe this is the [x-y problem](https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem) because it&#39;s possible the helm package I&#39;m installing is expecting RBAC to be enabled. But still, I&#39;d like to know how to check whether or not it is enabled/disabled.

how to check whether RBAC is enabled, using kubectl

I&#39;m debugging log output from kubectl that states:

    Error from server (BadRequest): a container name must be specified for pod postgres-operator-49202276-bjtf4, choose one of: [apiserver postgres-operator]

OK, so that&#39;s an explanatory error message, but looking at my JSON template it ought to just create both containers specified, correct? What am I missing? (please forgive my ignorance.)

I&#39;m using just a standard kubectl create -f command to create the JSON file within a shell script. The JSON deployment file is as follows:

    {
        &quot;apiVersion&quot;: &quot;extensions/v1beta1&quot;,
        &quot;kind&quot;: &quot;Deployment&quot;,
        &quot;metadata&quot;: {
            &quot;name&quot;: &quot;postgres-operator&quot;
        },
        &quot;spec&quot;: {
            &quot;replicas&quot;: 1,
            &quot;template&quot;: {
                &quot;metadata&quot;: {
                    &quot;labels&quot;: {
                        &quot;name&quot;: &quot;postgres-operator&quot;
                    }
                },
                &quot;spec&quot;: {
                    &quot;containers&quot;: [{
                        &quot;name&quot;: &quot;apiserver&quot;,
                        &quot;image&quot;: &quot;$CCP_IMAGE_PREFIX/apiserver:$CO_IMAGE_TAG&quot;,
                        &quot;imagePullPolicy&quot;: &quot;IfNotPresent&quot;,
                        &quot;env&quot;: [{
                            &quot;name&quot;: &quot;DEBUG&quot;,
                            &quot;value&quot;: &quot;true&quot;
                        }],
                        &quot;volumeMounts&quot;: [{
                            &quot;mountPath&quot;: &quot;/config&quot;,
                            &quot;name&quot;: &quot;apiserver-conf&quot;,
                            &quot;readOnly&quot;: true
                        }, {
                            &quot;mountPath&quot;: &quot;/operator-conf&quot;,
                            &quot;name&quot;: &quot;operator-conf&quot;,
                            &quot;readOnly&quot;: true
                        }]
                    }, {
                        &quot;name&quot;: &quot;postgres-operator&quot;,
                        &quot;image&quot;: &quot;$CCP_IMAGE_PREFIX/postgres-operator:$CO_IMAGE_TAG&quot;,
                        &quot;imagePullPolicy&quot;: &quot;IfNotPresent&quot;,
                        &quot;env&quot;: [{
                            &quot;name&quot;: &quot;DEBUG&quot;,
                            &quot;value&quot;: &quot;true&quot;
                        }, {
                            &quot;name&quot;: &quot;NAMESPACE&quot;,
                            &quot;valueFrom&quot;: {
                                &quot;fieldRef&quot;: {
                                    &quot;fieldPath&quot;: &quot;metadata.namespace&quot;
                                }
                            }
                        }, {
                            &quot;name&quot;: &quot;MY_POD_NAME&quot;,
                            &quot;valueFrom&quot;: {
                                &quot;fieldRef&quot;: {
                                    &quot;fieldPath&quot;: &quot;metadata.name&quot;
                                }
                            }
                        }],
                        &quot;volumeMounts&quot;: [{
                            &quot;mountPath&quot;: &quot;/operator-conf&quot;,
                            &quot;name&quot;: &quot;operator-conf&quot;,
                            &quot;readOnly&quot;: true
                        }]
                    }],
                    &quot;volumes&quot;: [{
                        &quot;name&quot;: &quot;operator-conf&quot;,
                        &quot;configMap&quot;: {
                            &quot;name&quot;: &quot;operator-conf&quot;
                        }
                    }, {
                        &quot;name&quot;: &quot;apiserver-conf&quot;,
                        &quot;configMap&quot;: {
                            &quot;name&quot;: &quot;apiserver-conf&quot;
                        }
                    }]
                }
            }
        }
    }



Kubernetes / kubectl - &quot;A container name must be specified&quot; but seems like it is?

How can I use `kubectl` or the API to retrieve the current image for containers in a pod or deployment?

For example, in a deployment created with the below configuration, I want to retrieve the value `eu.gcr.io/test0/brain:latest`.

    apiVersion: v1
       kind: Deployment
       metadata:
         name: flags
       spec:
         replicas: 6
         template:
           metadata:
          labels:
            app: flags
           spec:
             containers:
             - name: flags
               image: eu.gcr.io/test0/brain:latest

Get current image of kubernetes deployment

    kubectl get pod run-sh-1816639685-xejyk 
    NAME                      READY     STATUS    RESTARTS   AGE
    run-sh-1816639685-xejyk   2/2       Running   0          26m

What&#39;s the meaning of &quot;READY=2/2&quot;? The same with &quot;1/1&quot;?

What&#39;s the meaning of &quot;READY=2/2&quot; output by command &quot;kubectl get pod $yourpod&quot;

I am trying to use kubectl run command to pull an image from private registry and run a command from that. But I don&#39;t see an option to specify image pull secret. It looks like it is not possible to pass image secret as part for run command. 

Is there any alternate option to pull a container and run a command using kubectl? The command output should be seen on the console. Also once the command finishes the pod should die.

All Kubectl Solutions on Gang of Coders

Total of 35 Kubectl Solutions