comminutus

@makkes Thanks for your reply. I do already have a Flux Kustomization for Sealed Secrets: ``` apiVersion: kustomize.toolkit.fluxcd.io/v1 kind: Kustomization metadata: name: sealed-secrets namespace: flux-system spec: sourceRef: kind: GitRepository name:...

@stefanprodan I do indeed have that (one named `cert-manager-controller` and another named `cert-manager-configs`). The problem still manifested regardless, because of what I mentioned about the `kustomization.yaml` file at ./cluster ....

@stefanprodan I realize that's what works for this kind of structure. However I thought one of the benefits to flux was that the developers are free to create a more...

Can this please be addressed? This is a pretty big limitation since often a headset is all I have and my phone has to be secured away. In this scenario...

Upon Seraphis, I think it'd make sense to version it as v19.0.0 to avoid confusion. Some may get the idea that v1.0 or variations (v1.0.0) are older than v0.18.3.1 for...

@iamamyth I totally agree. In the current semantics then, how is each component of the version defined?

I get the same issue sometimes and when it manifests it causes a lot of connectivity issues.

I keep getting bit by this. I only have one public IP which is the service IP and control plane IP. Often the lease holder of these two leases are...

I wish I could help diagnose it but I'm not even sure where to start.

This is enlightening @lubronzhan , I didn't realize this configuration wasn't really supported. I'll have to rethink the few clusters I maintain with this configuration and see if I can...