cernvmfs.gridpp.rl.ac.uk and cvmfs-stratum-one.cern.ch in Squid logs

[eylenth]

Dear CVMFS-CSI community

We are using the CVMFS-CSI plugin in our environment since last year in our environment.
The only Stratum-S0 and S1 servers that we are using + configured in the CSI fleet config are servers maintained by our organisation.

Our S0, S1 and the name our repository are configured via the extra-configmaps.yaml fleet file. This works all fine in our Kubernetes environment.

But for some reason, we still see a lot of calls reaching out to cernvmfs.gridpp.rl.ac.uk and cvmfs-stratum-one.cern.ch in our Squid logs from the squid servers that we maintain:

TCP_CF_REFRESH_MODIFIED/200 1178 GET http://cernvmfs.gridpp.rl.ac.uk/cvmfs/cvmfs-config.cern.ch/.cvmfspublished - HIER_NONE/- application/x-cvmfs
TCP_HIT/200 1185 GET http://cernvmfs.gridpp.rl.ac.uk/cvmfs/cvmfs-config.cern.ch/.cvmfspublished - HIER_NONE/- application/x-cvmfs
1737396633.012    121 10.65.196.92 TCP_REFRESH_MODIFIED/200 1141 GET http://cvmfs-stratum-one.cern.ch/cvmfs/cvmfs-config.cern.ch/.cvmfspublished - HIER_DIRECT/128.142.194.62 application/x-cvmfs

Those calls are coming from the kubernetes nodes where the CVMFS CSI plugin is configured.

Not sure what we are missing. My first guess that we need to override --endpoint and --drivername to the name of the repository that we are using: see
But I'm not sure if that will break something.