I am fairly new to the Google Cloud platform and Docker and set-up a cluster of nodes, made a Dockerfile that copies a repo and runs a Clojure REPL on a public port. I can connect to it from my IDE and play around with my code, awesome!

That REPL should however probably tunneled through SSH, but here is where my problem starts. __I can&#39;t find a suitable place to SSH into__ for making changes to the repo that Docker runs the REPL on:

  - The exposed IP just exposes the REPL service (correct kubernetes term?) and does not allow me to SSH in. 
  - Neither does the cluster master endpoint, it gives me a public key error even though I&#39;ve followed the `Adding or removing SSH keys for all of the instances in your project` part [here](https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys).

I would like to edit the source files via SSH but I would need to access the docker code repo. I don&#39;t know how to proceed.

I understand this isn&#39;t exactly a typical way to deploy applications so I am not even sure it&#39;s possible to have multiple nodes work with a modified docker codebase (do the nodes share the JVM somehow?).

Concretely my question is how do I SSH into the docker container to access the codebase?

How to SSH to docker container in kubernetes cluster?

I&#39;m looking for a pattern that allows to share volumes between two containers running on the same pod in Kubernetes.

My use case is:
I have a Ruby on Rails application running inside a docker container.
The docker image contains static assets in `/app/&lt;app-name&gt;/public` directory, and I need to access those assets from the nginx container running alongside in the same pod.

In &#39;vanilla&#39; docker I would have used `--volumes-from` flag to share this directory:

    docker run --name app -v /app/&lt;app-dir&gt;/public &lt;app-image&gt;
    docker run --volumes-from app nginx

After reading this doc: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/volumes.md
I tried this (only relevant entries presented):

    spec:
      containers:
        - image: &lt;app-image&gt;
          name: &lt;app-name&gt;
          volumeMounts:
            - mountPath: /app/&lt;app-name&gt;/public
              name: assets
        - image: nginx
          name: nginx
          volumeMounts:
            - mountPath: /var/www/html
              name: assets
              readOnly: true
        volumes:
          - name: assets
            hostPath:
	          path: /tmp/assets

But:

 - Even though `/tmp/assets` on the node exists, it&#39;s empty
 - `/app/&lt;app-name&gt;/public` inside the app container is also empty

As a workaround I&#39;m gonna try to populate the shared directory when the application container is up (simply `cp /app/&lt;app-name&gt;/public/*` to shared directory), but I really dislike this idea.

**Question:** how to mimic `--volumes-from` in Kubernetes, or if there is no direct counterpart, how can I share files from one container to other running in the same pod ?

`apiVersion: v1beta3`

    Client Version: version.Info{Major:&quot;0&quot;, Minor:&quot;17&quot;, GitVersion:&quot;v0.17.0&quot;, GitCommit:&quot;82f8bdac06ddfacf493a9ed0fedc85f5ea62ebd5&quot;, GitTreeState:&quot;clean&quot;}
    Server Version: version.Info{Major:&quot;0&quot;, Minor:&quot;17&quot;, GitVersion:&quot;v0.17.0&quot;, GitCommit:&quot;82f8bdac06ddfacf493a9ed0fedc85f5ea62ebd5&quot;, GitTreeState:&quot;clean&quot;}


How to mimic &#39;--volumes-from&#39; in Kubernetes

TL;DR. I&#39;m lost as to how to access the data after deleting a PVC, as well as why PV wouldn&#39;t go away after deleting a PVC.

Steps I&#39;m taking:

1. created a disk in GCE manually:

        gcloud compute disks create --size 5Gi disk-for-rabbitmq --zone europe-west1-b

2. ran:
  
        kubectl apply -f /tmp/pv-and-pvc.yaml

    with the following config:

        # /tmp/pv-and-pvc.yaml
        apiVersion: v1
        kind: PersistentVolume
        metadata:
          name: pv-for-rabbitmq
        spec:
          accessModes:
          - ReadWriteOnce
          capacity:
            storage: 5Gi
          gcePersistentDisk:
            fsType: ext4
            pdName: disk-for-rabbitmq
          persistentVolumeReclaimPolicy: Delete
          storageClassName: standard
        ---
        apiVersion: v1
        kind: PersistentVolumeClaim
        metadata:
          name: pvc-for-rabbitmq
        spec:
          accessModes:
          - ReadWriteOnce
          resources:
            requests:
              storage: 5Gi
          storageClassName: standard
          volumeName: pv-for-rabbitmq

3. deleted a PVC manually (on a high level: I&#39;m simulating a disastrous scenario here, like accidental deletion or misconfiguration of a `helm` release):

        kubectl delete pvc pvc-for-rabbitmq

At this point I see the following:

    $ kubectl get pv
    NAME              CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS     CLAIM                      STORAGECLASS   REASON   AGE
    pv-for-rabbitmq   5Gi        RWO            Delete           Released   staging/pvc-for-rabbitmq   standard                8m
    $

&gt; A side question, just improve my understanding: **why PV is still there, even though it has a reclaim policy set to `Delete`?** Isn&#39;t this what the [docs](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#delete) say for the `Delete` reclaim policy?

Now if I try to re-create the PVC to regain access to the data in PV:

    $ kubectl apply -f /tmp/pv-and-pvc.yaml
    persistentvolume &quot;pv-for-rabbitmq&quot; configured
    persistentvolumeclaim &quot;pvc-for-rabbitmq&quot; created
    $

I still get this for `pv`s, e.g. a PV is stuck in `Released` state:

    $
    kubectl get pv
    NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS     CLAIM                             STORAGECLASS   REASON    AGE
    pv-for-rabbitmq                            5Gi        RWO            Delete           Released   staging/pvc-for-rabbitmq          standard                 15m
    $

...and I get this for `pvc`s:

    $
    kubectl get pvc
    NAME               STATUS    VOLUME            CAPACITY   ACCESS MODES   STORAGECLASS   AGE
    pvc-for-rabbitmq   Pending   pv-for-rabbitmq   0                         standard       1m
    $

Looks like my PV is stuck in `Released` status, and PVC cannot access the PV which is not in `Available` status.

So, why the same PV and PVC cannot be friends again? **How do I make a PVC to regain access to data in the existing PV?**

What to do with Released persistent volume?

Running `kubectl logs` shows me the stderr/stdout of one Kubernetes container.  

How can I get the aggregated stderr/stdout of a set of pods, preferably those created by a certain replication controller?

How do I get logs from all pods of a Kubernetes replication controller?

I&#39;m now trying to run a simple container with shell (/bin/bash) on a Kubernetes cluster.

I thought that there was a way to keep a container running on a Docker container by using `pseudo-tty` and detach option (`-td` option on `docker run` command).

For example,

    $ sudo docker run -td ubuntu:latest

Is there an option like this in Kubernetes?

I&#39;ve tried running a container by using a `kubectl run-container` command like:

    kubectl run-container test_container ubuntu:latest --replicas=1

But the container exits for a few seconds (just like launching with the `docker run` command without options I mentioned above). And ReplicationController launches it again repeatedly.

Is there a way to keep a container running on Kubernetes like the `-td` options in the `docker run` command?




How can I keep a container running on Kubernetes?

I have Kubernetes working well in two different environments, namely in my local environment (MacBook running minikube) and as well as on Google&#39;s Container Engine (GCE, Kubernetes on Google Cloud).  I use the MacBook/local environment to develop and test my YAML files and then, upon completion, try them on GCE.  

Currently I need to work with each environment individually:  I need to edit the YAML files in my local environment and, when ready, (git) clone them to a GCE environment and then use/deploy them.  This is a somewhat cumbersome process.

Ideally, I would like to use kubectl from my Macbook to easily switch between the local minikube or GCE Kubernetes environments and to easily determine where the YAML files are used. Is there a simple way to switch contexts to do this?

How to switch kubectl clusters between gcloud and minikube

I&#39;ve created a [Kubernetes Scheduled Job](https://kubernetes.io/docs/user-guide/cron-jobs/), which runs twice a day according to its schedule. However, I would like to trigger it manually for testing purposes. How can I do this?

How can I trigger a Kubernetes Scheduled Job manually?

I am trying to deploy my app to *Kubernetes* running in *Google Container
Engine*.

The app can be found at: https://github.com/Industrial/docker-znc.

The *Dockerfile* is built into an image on *Google Container Registry*.

I have deployed the app in *Kubernetes* via the + button. I don&#39;t have the YAML
for this.

I have inserted a *Secret* in *Kubernetes* for the PEM file required by the app.

  1. How do I get the YAML for the *Deployment*, *Service* and *Pod* created by
     Kubernetes by filling in the form?
  1. How do I get the *Secret* into my *Pod* for usage?

Get YAML for deployed Kubernetes services?

`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?

    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 have scheduled an application to run as a Cronjob in Kubernetes. When there is a code change, I&#39;m also changing the image of the CronJob.

I&#39;m looking for an option where I can disable the currently running CronJob and deploy a new CronJob with the latest Image version. 

How can I disable a Cronjob in Kubernetes without deleting its yaml manifest?

Disabling cronjob in Kubernetes

As stated in the title, is it possible to find out a K8s cluster name from the API? I looked around the API and could not find it.

How to get Kubernetes cluster name from K8s API

I wanted to know what is the difference between a Replication Controller and a Deployment within Kubernetes (1.2). Going through the getting started document (http://kubernetes.io/docs/hellonode/) I have created a deployment - but it doesn&#39;t show up on the web UI.

When I create apps from the web UI - they are created as replication controllers. Functionally though, they seem very similar (they both manage pods and have services).

So - what is the difference and when should I use each?

Replication Controller VS Deployment in Kubernetes

After the latest updates to gcloud and docker I&#39;m unable to access images on my google container repository.  Locally when I run: `gcloud auth configure-docker` as per the instructions after updating gcloud, I get the following message:

    WARNING: `docker-credential-gcloud` not in system PATH.
    gcloud&#39;s Docker credential helper can be configured but it will not work until this is corrected.
    gcloud credential helpers already registered correctly.

Running `which docker-credential-gcloud` returns `docker-credential-gcloud not found`.

I have no other gcloud-related path issues and for the life of me can&#39;t figure out how to install/add docker-credential-gcloud to path. Here&#39;s what I have installed (shown via `gcloud version`):

    Google Cloud SDK 197.0.0
    beta 2017.09.15
    bq 2.0.31
    container-builder-local
    core 2018.04.06
    docker-credential-gcr
    gsutil 4.30

I also have Docker CE Version 18.03.0-ce-mac60 (23751).

Here&#39;s my $PATH:`/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin`

I also ran `source /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/path.zsh.inc` on original gcloud install.



`docker-credential-gcloud` not in system PATH

I would like to deploy an application cluster by managing my deployment via k8s Deployment object. The documentation has me extremely confused. My basic layout has the following components that scale independently:

 1. API server
 2. UI server
 3. Redis cache
 4. Timer/Scheduled task server

Technically, all 4 above belong in separate pods that are scaled independently. 

My questions are:

 1. Do I need to create `pod.yml` files and then somehow reference them in `deployment.yml` file or can a deployment file also embed pod definitions?
 2. K8s documentation seems to imply that the `spec` portion of `Deployment` is equivalent to defining *one* pod. Is that correct? What if I want to declaratively describe multi-pod deployments? Do I do need multiple deployment.yml files?

How to configure a Kubernetes Multi-Pod Deployment

I have been digging through the Kubernetes documentation for hours.  I understand the core design, and the notion of services, controllers, pods, etc.  

What I don&#39;t understand, however, is the process in which I can declaratively configure the cluster.  That is, a way for me to write a config file (or a set thereof) to define the makeup, and scaling options of the cloud deployment.  I want to be able to declare which containers I want in which pods, how they will communicate, how they will scale, etc. without running a ton of cli commands.

***Is there [docker-compose][1] functionality for Kubernetes?***

I want my application to be defined in git—to be version controlled–without relying on manual cli interactions. 

Is this possible to do in a concise way?  Is there a reference that is more clear than the official documentation?


  [1]: https://docs.docker.com/compose/overview/

Can Kubernetes be used like Docker Compose?

Is there a way to force an SSL upgrade for incoming connections on the ingress load-balancer? Or if that is not possible with, can I disable port :80? I haven&#39;t found a good documentation pages that outlines such an option in the YAML file. Thanks a lot in advance!

All Google Kubernetes-Engine Solutions on Gang of Coders

Total of 17 Google Kubernetes-Engine Solutions