---
title: "Discussion on \"Kube-Prometheus-Stack And ArgoCD 2.3 - How to remove a workaround\" | Hashnode"
description: "Discussion on \"Kube-Prometheus-Stack And ArgoCD 2.3 - How to remove a workaround\". \"prometheuses.monitoring.coreos.com\" is invalid: metadata.annotations: Too long: must have at most 262144 bytes"
url: "https://hashnode.com/posts/kube-prometheus-stack-and-argocd-23-how-to-remove-a-workaround/6238ccb66622115cc804860b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Kube-Prometheus-Stack And ArgoCD 2.3 - How to remove a workaround](https://blog.ediri.io/kube-prometheus-stack-and-argocd-23-how-to-remove-a-workaround?utm_source=hashnode&utm_medium=feed)

"prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

Mar 21, 2022 · 2 min read · blog.ediri.io  
Updated Nov 26, 2022  
Read the article

-   [#infrastructure](https://hashnode.com/tag/infrastructure)
-   [#cloud](https://hashnode.com/tag/cloud)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#monitoring](https://hashnode.com/tag/monitoring)

## Written by

[Engin Diri](https://hashnode.com/@ediri)

@ediri · Germany

  
[View profile](https://hashnode.com/@ediri)

Customer Experience Architect @ Pulumi

Cloud Native Pilgrim | Kubernetes Enthusiast | Serverless Believer | Customer Experience Architect @ Pulumi | (he/him) | CK{A,AD} |

## Responses 2

Markdown supported · ⌘↵ to post

[Theodore Andrew](https://hashnode.com/@theodoreandrew)

[Oct 17, 2022](https://hashnode.com/posts/kube-prometheus-stack-and-argocd-23-how-to-remove-a-workaround/6238ccb66622115cc804860b/comment/634dea04cc3d1e8318d0fc7b)

[Engin Diri](https://hashnode.com/@ediri) Hi, I would like to ask about this approach. If I am not using helm, will this 2 Applications.yaml deployment work? Thanks!

[Engin Diri](https://hashnode.com/@ediri)

[Oct 21, 2022](https://hashnode.com/posts/kube-prometheus-stack-and-argocd-23-how-to-remove-a-workaround/6238ccb66622115cc804860b/comment/634dea04cc3d1e8318d0fc7b#reply-63527a892ef5b2c2eaabd3eb)

Yes, or you can use the SSA feature in the latest version of ArgoCD -> [argo-cd.readthedocs.io/en/latest/proposals/server…](https://argo-cd.readthedocs.io/en/latest/proposals/server-side-apply/)

[venkata mutyala](https://hashnode.com/@venkatamutyala)

[Aug 2, 2022](https://hashnode.com/posts/kube-prometheus-stack-and-argocd-23-how-to-remove-a-workaround/6238ccb66622115cc804860b/comment/62e88fdf430bd1d04a8489fc)

Thanks for sharing. I came up with a similar solution, and it is nice to see I'm not alone on this approach.

[venkata mutyala](https://hashnode.com/@venkatamutyala)

[Aug 2, 2022](https://hashnode.com/posts/kube-prometheus-stack-and-argocd-23-how-to-remove-a-workaround/6238ccb66622115cc804860b/comment/62e88fdf430bd1d04a8489fc#reply-62e891c7053e6bd57842bd28)

[Engin Diri](https://hashnode.com/@ediri) Any reason you choose such a large number difference for the sync-wave (ex. 2 and 10)? I'm doing things slightly different where I have the CRD's create the namespace, which prevents the other argocd application from running.

[Engin Diri](https://hashnode.com/@ediri)

[Aug 11, 2022](https://hashnode.com/posts/kube-prometheus-stack-and-argocd-23-how-to-remove-a-workaround/6238ccb66622115cc804860b/comment/62e88fdf430bd1d04a8489fc#reply-62f5278c69fa1793160bd5c1)

[venkata mutyala](https://hashnode.com/@venkatamutyala) Just random to show that CRD app has to run before and the create namespace flag went lost here :D Will add it, thanks pointing out!
