Open MattiasGees opened 20 hours ago
Can you provide the configuration that is ultimately passed into the controller?
The chart by default does not watch all entries, but instead only watches ones with a generated className.
There's 4 ways to go from here.
I am having some problems with clusterstaticentries not being created. I have SPIRE deployed with the helm-charts. I am using the following version:
spire-server: 1.11.0 spire-controller-manager: 0.6.0 spire-crd (helm): 0.5.0 spire (helm): 0.24.0
I am using the following helm values:
I am joining an external host through the x509pop and that works without any problem. I can see it showing up in the SPIRE server as
spiffe://spire.internal.mattiasgees.be/spire/agent/x509pop/<fingerprint>
The Kubernetes auto-discovery with ClusterSPIFFEIds works correctly, but when I add a clusterStaticEntry for a workload running on that x509pop, it doesn't get created in the SPIRE server. The clusterStaticEntry looks the following:
In the SPIRE controller manager logs, I can see that the reconciliation is starting, but nothing else. It doesn't show any errors or further output.