[question]: Authentik server is unable to be created due to missing PriorityClass (also means there is no authentik server running for auth)

pambalos commented 2 months ago

Prior Search

[X] I have already searched this project's issues to determine if a similar question has already been asked.

What is your question?

I was in the process of upgrading my panfactum stack version, but am now stuck because the authentic server went down and is no longer available to provide access to my cluster. What happens now is that it sends out the SAML request first to AWS, then it redirects to the borked Authentik Server.

Looking into AWS, I see that a missing PriorityClass is the root cause of the deployments' failure to progress.

pods "authentik-server-6b74ff947c-" is forbidden: no PriorityClass with name database was found

I was going to add the database priority class, but terragrunt is unable to talk to my cluster. Is this recoverable? Vault is still running as expected, and my root token is still valid, but how can I resolve this auth flow issue?

What primary components of the stack does this relate to?

Authentik, Kube, AWS, Vault

Code of Conduct

[X] I agree to follow this project's Code of Conduct

pambalos commented 2 months ago

Am I correct in assuming that I should be able to recover by reverting the AWS and Kube configurations to the starting profiles I used to set everything up initially?

pambalos commented 2 months ago

I was indeed able to revert the AWS and Kube configs to resolve cluster access

Panfactum / stack