[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Adding master to 3 node install

On Fri, Aug 12, 2016 at 8:58 AM, Philippe Lafoucrière <philippe lafoucriere tech-angels com> wrote:

On Thu, Aug 11, 2016 at 8:42 PM, Jason DeTiberus <jdetiber redhat com> wrote:
This sounds like your registry was using ephemeral storage rather than being backed by a PV or object storage.

It's should not.
We're using:

docker_register_volume_source='{"nfs": { "server": "10.x.x.x", "path": "/zpool-1234/registry/"}}'

Anyway, it seems this variable isn't used anymore :( (in favor of the portion you mentionned in your link)
I will investigate that.

Yet, I can see the volume present in the yaml manifest:

      name: registry-storage
        server: 10.x.x.x
        path: /zpool-1234/registry/
      name: registry-token-xmulp
        secretName: registry-token-xmulp
    name: registry-storage
    mountPath: /registry
    name: registry-token-xmulp
    readOnly: true
    mountPath: /var/run/secrets/kubernetes.io/serviceaccount

but not in the console:

Inline image 1

Weird :)

Indeed. Where there any errors generated in the node logs? I would expect issues mounting the volume or accessing the volume would have prevented the pod from starting. I also must say that I'm not overly familiar with the changes that were introduced between 1.2.0 and 1.2.1 and if there is something there that could have an impact.

Jason DeTiberus

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]