# Lenses Agent v6 not updating to new Schema Registry URL

**URL:** <https://ask.lenses.io/t/lenses-agent-v6-not-updating-to-new-schema-registry-url/466>\
**Category:** Lenses\
**Tags:** schema-registry, agent, lenses6\
**Created:** [February 18, 2026, 11:08am UTC](https://ask.lenses.io/t/lenses-agent-v6-not-updating-to-new-schema-registry-url/466 "2026-02-18T11:08:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![superbrain\_bug](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@superbrain\_bug](https://ask.lenses.io/u/superbrain_bug)\
**Post date:** [February 18, 2026, 11:08am UTC](https://ask.lenses.io/t/lenses-agent-v6-not-updating-to-new-schema-registry-url/466/1 "2026-02-18T11:08:53Z")

</div>

I’ve checked the provision.yaml file and the schema url is correctly updated there

$ kubectl exec -n lenses lenses-agent-000111b7f8-btbhh – ls -la /mnt/provision-secrets/files/  
confluentSchemaRegistry:

- configuration:  
schemaRegistryUrls:  
value:
  - [https://schema-registry.xxx.xxx.xxx](https://schema-registry.xxx.xxx.xxx/)

but in the UI in schema configuration I see the old url

In the logs we do see this error

`WARN Provisioning validation failed: Connection ‘schema-registry’ validation failed - templateName: Unrecognized template`  
`WARN Error updating connections configuration:`

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?

Can you help me?

---

<div class="post-metadata">

**Author:** ![iMajna](https://dub1.discourse-cdn.com/flex017/user_avatar/ask.lenses.io/imajna/32/116_2.png) [@iMajna](https://ask.lenses.io/u/iMajna)\
**Post date:** [February 25, 2026, 12:14pm UTC](https://ask.lenses.io/t/lenses-agent-v6-not-updating-to-new-schema-registry-url/466/2 "2026-02-25T12:14:43Z")

</div>

Hi superbrain\_bug

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

1. 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.

Kind regards,  
Ivan