Skip to content

Metadig-worker and Metadig-scheduler Helm chart pv.yaml name/namespace update #471

@doulikecookiedough

Description

@doulikecookiedough

In the pv.yaml files found below, there appears to be a mismatch in credentials.

helm/metadig-scheduler/pv.yaml
helm/metadig-worker/pv.yaml

Per @artntek's PR feedback:

the credentials in this csi-cephfs-secret don't appear to match those in the security repo (security/k8s/cephfs-subvols.gpg). Instead, it's listed as:

subvolume: k8sdevsubvol
user: (redacted)
group: k8sdevsubvolgroup
path: /volumes/k8sdevsubvolgroup/k8sdevsubvol/4b7cd044-4055-49c5-97b4-d1240d276856/
key: (matches this one) 

(note the different path, too)

The credentials for:

## PRODUCTION
rootPath: /volumes/pdg-subvol-group/pdg-subvol/a5c90f20-f824-4ce9-b175-6685d7846520/repos
## DEV/TEST
rootPath: /volumes/tdg-subvol-group/tdg-subvol/a5c90f20-f824-4ce9-b175-6685d7846520/repos

...are already installed in secrets named:

  • csi-cephfs-prod-data-pdg-subvol (for prod), and
  • csi-cephfs-test-data-tdg-subvol (for dev)

For consistency and to reduce confusion, it would be good to replace name: csi-cephfs-secret with name: csi-cephfs-prod-data-pdg-subvol (and ideally to delete csi-cephfs-secret (if nothing else is using it).

Review, apply and test these changes.

  • Note, access to dev k8s is required so that the updated name/namespace can be applied. This cannot be done via dev-metadig k8s directly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions