Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Thomas Coudert
    @thcdrt
    We're seeing how we can get around the problem until this modification has been prodded
    Michał Frąckiewicz
    @SystemZ
    I'll try to build docker image from master
    Jawher Moussa
    @jawher_twitter
    Thank you @thcdrt , I appreciate the prompt response ! I'll try building fluentbit from master :+1:
    Thomas Coudert
    @thcdrt
    Ok @jawher_twitter , keep me updated :)
    Michał Frąckiewicz
    @SystemZ
    I'll already pushed it systemzz/fluent-bit:latest
    so far it doesn't show that error, I'll check if logs are being sent
    yep, it works, only docker image needs to be changed
    no errors, logs visible in graylog
    Thomas Coudert
    @thcdrt
    Great, thanks @SystemZ :)
    We will push it on one of our repo and modify doc until fluentbit release its new version
    Michał Frąckiewicz
    @SystemZ
    :thumbsup:
    Michał Frąckiewicz
    @SystemZ
    I see that calico-node is pretty chatty, any idea how to ignore containers from sending logs to graylog ?
    arduinio
    @arduinio
    you could use pipeline in graylog to remove or prevent
    i thimnk it will be possible
    think
    Michał Frąckiewicz
    @SystemZ
    on selfhosted, yea, on ovh offer I think it's not available
    arduinio
    @arduinio
    i use my custom graylog stack
    sorry
    Michał Frąckiewicz
    @SystemZ
    I used my too but each malfunction of graylog + ES debugging melted my brain too much
    Thomas Coudert
    @thcdrt
    Hello @SystemZ , you can use this filter => https://docs.fluentbit.io/manual/v/1.2/filter/grep
    It allow to exclude some logs
    Thomas Coudert
    @thcdrt
    We deployed the docker image on ovhcom/fluent-bit. We're updating the doc too.
    Thomas Coudert
    @thcdrt
    Pull request on ovh/docs is opened => ovh/docs#339
    Michał Frąckiewicz
    @SystemZ
    thanks! grep works wonderful in fluent bit
    I added something like this to the end of filter-kubernetes.conf config map:
        [FILTER]
            Name    grep
            Match   *
            Exclude kubernetes_container_name calico-node
        [FILTER]
            Name    grep
            Match   *
            Exclude kubernetes_container_name wormhole
    Thomas Coudert
    @thcdrt
    @SystemZ Glad to hear !
    bcarriou
    @bcarriou
    Hi, I'am not sure but can you confirm me if my etcd cluster is UP on my cluster ?
    I have some message on my RAncher cluster about that
    E0917 15:25:22.936453 9 leaderelection.go:286] Failed to update lock: etcdserver: request timed out
    2019/09/17 15:25:24 [ERROR] ClusterController local [cluster-stats] failed with : etcdserver: request timed out
    Philippe Vienne
    @PhilippeVienne_gitlab
    @bcarriou Same on my side since days and etcd is fine, just liveness is not replying because on another network.
    Thomas Coudert
    @thcdrt
    Hello @bcarriou , where do you see those logs ?
    bcarriou
    @bcarriou
    @PhilippeVienne_gitlab ok thanks :)
    @thcdrt It is on my Rancher cluster but it is due because etcd isn't accessible now => thx @PhilippeVienne_gitlab
    bcarriou
    @bcarriou
    Hi, I tried to upgrade version from 1.12 to 1.13 but I have the state Erreur in my OVH UI.
    Some info:
    k get nodes
    NAME       STATUS                        ROLES    AGE    VERSION
    worker-1   Ready                         <none>   202d   v1.12.10
    worker-2   Ready                         <none>   158d   v1.12.10
    worker-3   NotReady,SchedulingDisabled   <none>   92d    v1.12.10
    bcarriou
    @bcarriou
    my cluster id: 1aa61333-b08c-4ea9-abc0-82f8b39b5cb2
    SebastienJardin
    @SebastienJardin
    Hi @bcarriou I'm working on your problem, we can switch on DM if you want?
    bcarriou
    @bcarriou
    @SebastienJardin yes thx
    kobrasz
    @kobrasz

    Hi, I have problem with my Load balancer, I want to expose my oauth2 pod with k8s ovh load balancer, when I'm using

    annotations:
        service.beta.kubernetes.io/ovh-loadbalancer-proxy-protocol: "v1"
    spec:
      type: LoadBalancer
      externalTrafficPolicy: Local

    I'm getting ERR_SSL_PROTOCOL_ERROR in my browser

    Thomas Coudert
    @thcdrt
    Hello @kobrasz
    Checking with you in private
    kobrasz
    @kobrasz
    kk
    monsio
    @kaizokun
    hi everybody, is that possible to move a deployment to another namespace ?
    Guillaume
    @dracorpg
    Hi. Simply re-deploy it in your new namespace.
    (if you don't have its yaml definition file at hand, kubectl edit will handily open it in your text editor)
    monsio
    @kaizokun
    OK i use the dashboard actually and I have a error when I try to modify the namespace
    Guillaume
    @dracorpg
    I don't think you can change any fundamental attribute such as name or namespace for existing resources
    monsio
    @kaizokun
    it s for a wordpress deployment that I installed with Helm
    Guillaume
    @dracorpg
    I don't use Helm but the chart should allow you to easily specify the namespace in which resources should be created
    monsio
    @kaizokun
    ok so the only solution is to reinstall it
    Guillaume
    @dracorpg
    yeah - which should be 1 command ;)
    monsio
    @kaizokun
    ok so I'll just have to find a good way to move the datas from my old wordpress installaiton to the new one
    Guillaume
    @dracorpg
    (this is the actual spirit of devops BTW - as little is changed by hand, operations are done by deploying configuration files)
    PersistentVolumes are not namespaced, but PersistentVolumeClaims are
    I suppose the PV where SQL data is persisted was dynamically provisioned by a PVC ?