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

k8s-keystone-auth-policy is missing $PROJECT_ID #483

Open
mariusleu opened this issue Jan 25, 2025 · 0 comments
Open

k8s-keystone-auth-policy is missing $PROJECT_ID #483

mariusleu opened this issue Jan 25, 2025 · 0 comments

Comments

@mariusleu
Copy link

The k8s-keystone-auth-policy ConfigMap gets rendered without the project id, thus Keystone tokens can't be used to access the cluster.

In my case it looks like this

      "users":{
         "projects":[
            "$PROJECT_ID"
         ],
         "roles":[
            "k8s_admin"
         ]
      }

After replacing $PROJECT_ID with the actual project id, then restarting k8s-keystone-auth pods, the authentication works well using Keystone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant