diff --git a/README.md b/README.md
index 8b699b4..c2b24b0 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@
   * [cert-manager](https://cert-manager.io/)
     * selfsigned issuer
     * LetsEncrypt issuers (Prod and Staging)
-  * [zabbix-proxy](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.4)
+  * [zabbix-proxy](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F7.0)
   * [keel](https://keel.sh)
   * [reloader](https://github.com/stakater/Reloader)
 
@@ -49,7 +49,7 @@ data:
 #### cert-manager
 
 > However, when you have the PROXY protocol enabled, the external load balancer does modify the traffic, prepending the PROXY line before each TCP connection. If you connect directly to the web server internally, bypassing the external load balancer, then it will receive traffic without the PROXY line.
->
+> 
 > This is particularly a problem when using cert-manager for provisioning SSL certificates.
 
 After enabling the PROXY protocol cert-manager is unable to perform a self check ("propagation check failed", "failed to perform self check GET request").
diff --git a/manifests/monitoring/zabbix-proxy.jsonnet b/manifests/monitoring/zabbix-proxy.jsonnet
index 92016b4..124c7aa 100644
--- a/manifests/monitoring/zabbix-proxy.jsonnet
+++ b/manifests/monitoring/zabbix-proxy.jsonnet
@@ -5,8 +5,8 @@ app + {
   name:: "zabbix-proxy",
   namespace:: "monitoring",
   chart:: "zabbix-helm-chrt",
-  repo:: "https://cdn.zabbix.com/zabbix/integrations/kubernetes-helm/6.4",
-  version:: "1.3.*",
+  repo:: "https://cdn.zabbix.com/zabbix/integrations/kubernetes-helm/7.0",
+  version:: "0.0.*",
   values:: |||
     zabbixAgent:
       enabled: false