Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Ghost
    @ghost~5bc6039cd73408ce4faba551
    Hi, I have some issue with deployment who doesn't create pod .
    kubectl get deployments.apps
    NAME                            READY   UP-TO-DATE   AVAILABLE   AGE
    vnodejs                         1/1     1            1           20d
    vroum                           0/1     0            0           74s
    No pods come in pending state when I create the deployment.
    Devops TC
    @devops-tc
    Same here when set with replica set, no rs created, no pod neither
    abstract-entity
    @abstract-entity
    @bmagic what do you get with a 'describe' of deployment ?
    Joël LE CORRE
    @jlecorre_gitlab
    Hello, we will check our platform. I'll keep you informed of the situation.
    Ghost
    @ghost~5bc6039cd73408ce4faba551
    Nothing special in describe :
    OldReplicaSets:    <none>
    NewReplicaSet:     <none>
    Events:            <none>
    Ghost
    @ghost~5bc6039cd73408ce4faba551
    Seems fine now
    thx
    Joël LE CORRE
    @jlecorre_gitlab
    OK, nice, we have just restarted some pods stucked with DNS errors.
    Sorry for the inconvenience.
    Devops TC
    @devops-tc
    No problem, thank you
    arduinopepe
    @arduinopepe
    hy guys
    any experience whith rancher on ovh ?
    Joël LE CORRE
    @jlecorre_gitlab
    Hello @arduinio
    No experience with Rancher in OVH Managed Kubernetes team. Sorry.
    arduinopepe
    @arduinopepe
    i'm going crazy
    bcarriou
    @bcarriou
    Hi @arduinio , I use Rancher on my k8s cluster hosted by OVH Managed Kubernetes. What's is the problem ?
    arduinopepe
    @arduinopepe
    @bcarriou i just resolve my problem, it was openstack cloud provider.
    thanks
    arduinopepe
    @arduinopepe
    good morning to all
    why my control-manager and scheduler are Unhealty
    [root@k8s-mngt ~]# kubectl get cs NAME STATUS MESSAGE ERROR controller-manager Unhealthy Get http://127.0.0.1:10252/healthz: dial tcp 127.0.0.1:10252: connect: connection refused scheduler Unhealthy Get http://127.0.0.1:10251/healthz: dial tcp 127.0.0.1:10251: connect: connection refused etcd-1 Healthy {"health":"true"} etcd-2 Healthy {"health":"true"} etcd-0 Unhealthy HTTP probe failed with statuscode: 503
    Philippe Vienne
    @PhilippeVienne_gitlab
    This is because rancher can not access them as they are not reachable and only managed by OVH
    arduinopepe
    @arduinopepe
    ok
    thanks
    Joël LE CORRE
    @jlecorre_gitlab
    Hello @arduinio, as @PhilippeVienne_gitlab said, this behaviour is due to our infrastructure design and this is totally normal.
    Philippe Vienne
    @PhilippeVienne_gitlab
    Hi, do you have ETA for cluster upgrades ?
    arduinopepe
    @arduinopepe
    @jlecorre_gitlab thx.
    Pierrick Gicquelais
    @Kafei59
    Hello @PhilippeVienne_gitlab, we're on it. It should be ok for next week ;)
    Philippe Vienne
    @PhilippeVienne_gitlab
    Oh, great news for us, we will be able to move from our 1.12
    Philippe Vienne
    @PhilippeVienne_gitlab
    Hi, do you have change something on LoadBalancer today, my binding on port 22 fails
    Thomas Coudert
    @thcdrt
    Hello @PhilippeVienne_gitlab , seeing with you in private
    Philippe Vienne
    @PhilippeVienne_gitlab
    Thanks @thcdrt
    arduinopepe
    @arduinopepe
    hy guys
    i need to create a pod whith 3 volume (persistant)
    can i use the same pvc ??
    or i need to have a map 1:1 pv:pvc ??
    Philippe Vienne
    @PhilippeVienne_gitlab
    Yes, the pvc create the pv but in your pod simply use subPath inside the pvc to mount different parts of the PVC to different system path or containers
    arduinopepe
    @arduinopepe
    ` volumes:
      - name: vol1
        persistentVolumeClaim:
          claimName: vol-pv-claim
      - name: vol2
        persistentVolumeClaim:
          claimName: vol-pv-claim
      - name: vol3
        persistentVolumeClaim:
          claimName: vol-pv-claim`
    correct ?
    Philippe Vienne
    @PhilippeVienne_gitlab
    No just specify one, it's on the mount you will use a subPath
    arduinopepe
    @arduinopepe
    ` volumeMounts:
        - name: vol1
          mountPath: /mounta
        - name: vol1
          mountPath: /mountb
        - name: vol1
          mountPath: /mountc`
    and use one pvc and one pv ?
    correct ?
    Philippe Vienne
    @PhilippeVienne_gitlab
    arduinopepe
    @arduinopepe
    any issue with registry ?
    denied: requested access to the resource is denied
    Pierrick Gicquelais
    @Kafei59
    Hello @arduinio, are you talking about Private Registry product ?
    arduinopepe
    @arduinopepe
    yes
    Pierrick Gicquelais
    @Kafei59
    If yes, there's a special Gitter channel for it :)
    arduinopepe
    @arduinopepe
    ok