Skip to content
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

Server 1.10.0+ crashes when deployed with eks example #5666

Open
vassilvk opened this issue Nov 26, 2024 · 1 comment
Open

Server 1.10.0+ crashes when deployed with eks example #5666

vassilvk opened this issue Nov 26, 2024 · 1 comment
Labels
help wanted Issues with this label are ready to start work but are in need of someone to do it priority/backlog Issue is approved and in the backlog
Milestone

Comments

@vassilvk
Copy link

vassilvk commented Nov 26, 2024

  • Version: 1.10.0
  • Platform: Kubernetes (EKS)
  • Subsystem: server

Deploying SPIRE server using the EKS deployment example, works up to version 1.9.6.

Switching the server (and agent) image to 1.10.0 or above (I tested up to 1.11.0), leads to spire-server going into a crash loop backoff issuing the following message:

time="2024-11-26T22:36:32Z" level=error msg="Server crashed" error="datastore-sql: unable to open database file: no such file or directory"

Note on persistence: I performed all version deployments against empty namespaces with no pre-existing PVCs or volumes.

@amartinezfayo amartinezfayo added the triage/in-progress Issue triage is in progress label Nov 28, 2024
@amartinezfayo
Copy link
Member

This seems to be an issue in the configuration of the example, not an issue in SPIRE itself.
It's probably a permission problem due to the changes to run SPIRE as not root.
This example is using the k8s_sat node attestor, which is deprecated. We should also update it to use k8s_psat instead.

@amartinezfayo amartinezfayo added help wanted Issues with this label are ready to start work but are in need of someone to do it priority/backlog Issue is approved and in the backlog and removed triage/in-progress Issue triage is in progress labels Nov 28, 2024
@amartinezfayo amartinezfayo added this to the 1.11.2 milestone Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issues with this label are ready to start work but are in need of someone to do it priority/backlog Issue is approved and in the backlog
Projects
None yet
Development

No branches or pull requests

2 participants