Thanks to visit codestin.com
Credit goes to github.com

Skip to content

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

@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: v1
kind: Secret
metadata:
  name: coder-org1-provisioner-key
type: Opaque
stringData:
  key: "the-key"
  psk: ""

Helm values:

coder:
  env:
    - name: CODER_URL
      value: "https://dev.coder.com"
    - name: CODER_PROVISIONER_DAEMON_KEY
      valueFrom:
        secretKeyRef:
          name: coder-org1-provisioner-key
          key: key
  replicaCount: 1
provisionerDaemon:
  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