-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workload attestation fails in k8s/quickstart #75
Comments
Were there any logs above those two lines you've pasted, particularly any from the k8s workload attestor plugin? |
Here's the full agent log:
|
I can confirm that an entry with a unix selector works:
|
I have the same problem the spire-agent logs is : how did you solve this problem?? @donaldh ,can you help me |
I change something ,It run success . change the clusterName "demo-cluster",It run success : " -selector k8s_sat:cluster:demo-cluster " |
I followed the K8S quickstart guide https://spiffe.io/docs/latest/try/getting-started-k8s/ but the final step failed:
From the spire-agent logs it seems like there are only unix selectors available but the registration entry uses k8s selectors:
The text was updated successfully, but these errors were encountered: