Elad Dolev

Hey friends Thinking of adding the ability to set Pod Topology Spread Constraints and enable them by default https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/ Also thinking of updating labels according to best practices https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/ https://helm.sh/docs/chart_best_practices/labels/...

Hi @slimus ! Not sure I understand the question, but if I go to a screen of a CRD of some sort, for example `ServiceMonitor` and try to sort by...

Hi @slimus The "equivalent" kubectl command would be `kubectl get sealedsecrets.bitnami.com --sort-by=.metadata.creationTimestamp` for example Thanks !

Still occurring with latest version :cry: 

happens to me to a few times a day I don't remember it happened with `v0.25.18` but it occurs on all versions `v0.25.19` and later

you can try and use the following, then adjust with offset when you're drawing the graph ```yaml serviceMonitor: honorTimestamps: false ```

any chance somebody can review this ? this thing causes random pod restart on every helm apply...

Upgrade should not fail, but may cause unnecessary pods restart

We're trying to peer two GKE clusters, where the destination cluster got Dataplane V2 (Cilium based) and we also encounter those `TLS handshake` errors in `liqo-auth` Peering `in-band` fails with...

seems that it is actually also broken in `v0.10.3` works in `v0.10.1` when the following can be still supplied ```yaml networking: iptables: mode: legacy ```