And when I look at the configuration in the UI, in the provision validation it says value must be 1. I did update it to “2” to force the update of url, but maybe that’s a wrong move?
Every time Lenses (agent) restarts it is rebuilding its state - not everything is stored necessarily in database. If you have already restarted it and you see the same issue, can you execute in agent pod and extract what’s in the provisioning.yaml file?
File should be located in /mnt/provisionin-secrets/provisioning.yaml . If it is not, you can cat/data/lenses-agent.conf and you will find reference to the file under lenses.provisioning.path . Has schema url changed there?
What also can happen is, Agent might have a problem connecting to new Schema Registry and that’s why it did not load new change? In your case, I would suggest to
Change `version` under confluentSchemaRegistry connection in provisioning.yaml and afterwards check whether connection is possible. If not, you can provide agent logs and will try to assist you further.