Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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 ?
    monsio
    @kaizokun
    ok so I could just create a new pvc cool
    Guillaume
    @dracorpg
    yeah but BUT if you delete the previous one, the underlying PV (and even OpenStack Cinder volume) will be deleted with it, by default
    you first have to change the current PV's reclamation policy to "Retain" instead of "Delete"
    monsio
    @kaizokun
    ok thank you very much
    Guillaume
    @dracorpg
    then you should add a volumeName: 'your-pv-name-here' line to the PVC's spec
    so the claim will bind to this existing PV instead of dynamically provisioning a new (empty) PV as per default
    (not very elegant, this whole stuff, but it should work and avoid resorting to an dump-and-load process for your data)
    monsio
    @kaizokun
    apparently the chart create de pv et pvc automaticly
    I guess that I ll be able to target the old pv from the new pvc
    Guillaume
    @dracorpg
    you'll have to hack your spec.volumeName in the chart template
    monsio
    @kaizokun
    ok I just tried to modify the pvc config but It doesn't work :)
    Guillaume
    @dracorpg
    once the PVC is created and a new PV has been dynamically provisioned for it, I'm not suuure you can un-bind the PVC and change its definition to bind it to another pre-existing PV instead
    yeah, you'll have to do the hack in the original yml that is applied to create the PVC (for a Helm chart I guess it's somewhere in templates ?)
    monsio
    @kaizokun
    probably there is a pvc.yalm in the templates folder but it uses variables
    I don't know where the vars are declared
    it seems more tricky than I thought I'll find an easier way ^^
    Guillaume
    @dracorpg
    you don't really need to care about the variables Helm injects, just add your line in the template and it should work - but yeah, not absolutely trivial
    kobrasz
    @kobrasz
    probably you can change variables in values.yaml, you can find this file in repository of your chart, I think that you have to create pvc on your own, attach there old pv and configure values.yaml to use your pvc insted of dynamically provisioned
    arduinio
    @arduinio
    Is there any way to allow a comunication between container inside OVH kubernetes and virtual machine inside on private cloud OVH ?
    Chaya56
    @Chaya56

    Hello,
    Do we have an incident currently in managed kubernetes service ?

    alt

    Joël LE CORRE
    @jlecorre_gitlab
    Hello @Chaya56
    I will check that with you in private if you want.
    Joël LE CORRE
    @jlecorre_gitlab
    Problem solved for @Chaya56.
    And for your information, we haven't any on going outage on our platform.
    Chaya56
    @Chaya56
    fyi, problem is due to have multiple cluster, with node having the same name
    Guilhem30
    @Guilhem30
    Hello, I'm trying to get the client real ip in the ingress controller and in my applications logs but it seems i'm only able to retrieve private ip addresses
    even in the ingress controller (nginx) logs all the ip are in 10.110.X.Y
    i modified my loadblancer to "externalTrafficPolicy: Local" but i'm still getting only private ip
    Chaya56
    @Chaya56
    @Guilhem30 what kind of ingress controller are you using ? nginx-ingress-controller ?
    Guilhem30
    @Guilhem30
    yes i'm using this https://github.com/kubernetes/ingress-nginx
    deployed with helm
    Chaya56
    @Chaya56
    you have to create a configmap with following values:
    use-proxy-protocol: "true"
proxy-real-ip-cidr: "0.0.0.0/32"
use-forwarded-headers: "false"
log-format-upstream: '$proxy_protocol_addr etc...'
http-snippet: |
  geo $realip_remote_addr $is_lb {
    default       0;
    10.108.0.0/14 1;
  }
server-snippet: |
  if ($is_lb != 1) {
    return 403;
  }