Config.php is not regenerated when i change the ConfigMap ?

[R-Nabil]

Hi,

Sorry if this is a dumb one but I can't figure it out.
It seems like the config.php file is not regenerated with new values when I update my config map.

For instance, if I change 10.0.0.0/24 to 10.0.0.0/16, I exec into the pod and look at the config.php file, I still see /24.

Is there something I am missing ?

  configs:
    proxy.config.php: |-
      <?php
      $CONFIG = array (
        'trusted_proxies' => array(
          0 => '127.0.0.1',
          1 => '10.0.0.0/24',
        ),
        'forwarded_for_headers' => array('HTTP_X_FORWARDED_FOR'),
        
      );

[jessebot]

Have you tried restarting the pod to pick up the latest config map changes?

[R-Nabil]

Yes ofc. Few times

[jessebot]

hmmm, I seem to recall this coming up before. @provokateurin, slowly coming back to this repo issue by issue :) Is the config file not updating expected behavior? Is the config.php only processed on first install?

[provokateurin]

Hm maybe the pvc is mounted on top of the config map? @R-Nabil could you try deleting the config file inside the pod and then restarting it? Either the file won't be regenerated at all or it should contain the new config map values.

[R-Nabil]

Yes that’s what I did eventually but this looks more like a workaround than an intended behaviour right?

…

________________________________ From: Kate ***@***.***> Sent: Friday, March 22, 2024 6:31:42 PM To: nextcloud/helm ***@***.***> Cc: R-Nabil ***@***.***>; Mention ***@***.***> Subject: Re: [nextcloud/helm] Config.php is not regenerated when i change the ConfigMap ? (Discussion #539) Hm maybe the pvc is mounted on top of the config map? @R-Nabil<https://github.com/R-Nabil> could you try deleting the config file inside the pod and then restarting it? Either the file won't be regenerated at all or it should contain the new config map values. — Reply to this email directly, view it on GitHub<#539 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQARXXSADTXKJBNPIGBOHILYZQCA5AVCNFSM6AAAAABD6H4XGKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DQNZWGQYDM>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[provokateurin]

Yeah I agree, there must be something wrong in the order of how we mount the pvc and the config map.

[provokateurin]

After reading kubernetes/kubernetes#68249 I'm not sure if this comes down to the runtime you are using. Can you tell us what k8s distro etc. you are using?

[R-Nabil]

I’m using k3s v1.26.14

i can spend sometimes maybe in the next few days reconfirming step by step what I did at the time.