Harbor Helm chart expects 'secret' key not 'CORE_SECRET' for the CORE_SECRET environment variable. This was causing jobservice pod to fail with CreateContainerConfigError. Fixes: harbor-jobservice-757bbf44cc-tvznq error
54 lines
1.5 KiB
YAML
54 lines
1.5 KiB
YAML
# ------------------------------------------------------------------------------
|
|
# ExternalSecret — Harbor Credentials
|
|
# Pulled from 1Password via Connect Server, materialized as a K8s secret
|
|
# in the-seas namespace for use by Harbor components.
|
|
#
|
|
# In 1Password, these are stored in the "the-seas" item in the "mk-labs" vault
|
|
# with fields: harbor-admin-password, database-password, redis-password,
|
|
# core-secret, jobservice-secret, registry-password
|
|
# ------------------------------------------------------------------------------
|
|
apiVersion: external-secrets.io/v1beta1
|
|
kind: ExternalSecret
|
|
metadata:
|
|
name: harbor-credentials
|
|
namespace: harbor
|
|
spec:
|
|
secretStoreRef:
|
|
kind: ClusterSecretStore
|
|
name: onepassword-connect
|
|
refreshInterval: "1h"
|
|
target:
|
|
name: harbor-credentials
|
|
creationPolicy: Owner
|
|
data:
|
|
- secretKey: HARBOR_ADMIN_PASSWORD
|
|
remoteRef:
|
|
key: the-seas
|
|
property: harbor-admin-password
|
|
|
|
- secretKey: DATABASE_PASSWORD
|
|
remoteRef:
|
|
key: the-seas
|
|
property: database-password
|
|
|
|
- secretKey: REDIS_PASSWORD
|
|
remoteRef:
|
|
key: the-seas
|
|
property: redis-password
|
|
|
|
# Core secret - Harbor Helm chart expects key named 'secret' not 'CORE_SECRET'
|
|
- secretKey: secret
|
|
remoteRef:
|
|
key: the-seas
|
|
property: core-secret
|
|
|
|
- secretKey: JOBSERVICE_SECRET
|
|
remoteRef:
|
|
key: the-seas
|
|
property: jobservice-secret
|
|
|
|
- secretKey: REGISTRY_PASSWD
|
|
remoteRef:
|
|
key: the-seas
|
|
property: registry-password
|