Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

provisioner helm chart: stop requiring psk to be set #14985

Assignees
johnstcn
Labels
must-doIssues that must be completed by the end of the Sprint. Or else. Only humans may set this.
@bpmct

Description

@bpmct

Now that we support--key auth and user auth, let's stop requiring a PSK secret in the provisionerd. As a workaround, the user can set the value to "" and use the key instead.

Secret:

apiVersion:v1kind:Secretmetadata:name:coder-org1-provisioner-keytype:OpaquestringData:key:"the-key"psk:""

Helm values:

coder:env:    -name:CODER_URLvalue:"https://dev.coder.com"    -name:CODER_PROVISIONER_DAEMON_KEYvalueFrom:secretKeyRef:name:coder-org1-provisioner-keykey:keyreplicaCount:1provisionerDaemon:pskSecretName:coder-org1-provisioner-key

But we don't want to have users doing this long-term.

Let's also work with@EdwardAngert to update the provisioner docs to explain how to configure this in Helm

Metadata

Metadata

Assignees

Labels

must-doIssues that must be completed by the end of the Sprint. Or else. Only humans may set this.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2025 Movatter.jp