-
Notifications
You must be signed in to change notification settings - Fork 887
Provisioner using PSK will not be selected if a scope
tag is absent
#9234
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
Comments
I think the issue could be happening because of the difference in logic here (assuming defaulting to org scope is acceptable): Lines 1083 to 1091 in 69ec8d7
coder/enterprise/coderd/provisionerdaemons.go Lines 190 to 196 in 69ec8d7
|
cc @spikecurtis |
All provisioner jobs default to I guess we should also default this tag for external provisioners. In the meantime @pratheekrebala, you can work around the issue by explicitly setting the tag in your Helm values.yaml. |
@pratheekrebala PSK auth will now automatically set the provisionerd scope to organization. |
Good Evening!
I have been trying to deploy external provisioners using the pre-shared key based authentication. Despite various attempts using different configurations, I was unable to get the provisioner to be selected. However, I was able to select the provisioner when using my personal user token.
Upon further inspection, it seems that an external provisioner that is missing an
scope=organization
tag will never be selected. I am not sure if this is intended behaviour. It would make sense that provisioner deployments have to be explicit about specific the scopes that they would be serving. I only realized this when looking at the/api/v2/organizations/me/provisionerdaemons
endpoint and noticed that all the inbuilt provisioners have thescope=organization
tag on them.The current helm chart does not add this tag which means that jobs will just hang unless the in-built provisioner daemons are enabled.
The text was updated successfully, but these errors were encountered: