Skip to content

v1.3.0
Compare
Choose a tag to compare
@nmanoogian nmanoogian released this 27 Jul 15:27
· 9 commits to main since this release
v1.3.0
1d18bce
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
  • Allow reconciliation of dopplersecret resources with refs in same namespace

DopplerSecret Reconciliation

This release updates the reconciliation behavior introduced in v1.2.0 to accommodate multi-tenancy use cases.

Before v1.2.0, the operator could reconcile a DopplerSecret in any namespace with references to secrets in any other namespaces. This posed a security risk because a user with access to a single namespace in the cluster could use the operator to read secrets from Doppler using token secrets that they couldn't read themselves.

In v1.2.0, the behavior was changed so that a DopplerSecret couldn't be reconciled unless it was in the same namespace as the operator itself (i.e. doppler-operator-system). This worked to address the security issue but made things significantly harder for teams with multi-tenant use cases.

This release updates the behavior again. DopplerSecrets in the operator's namespace behave as they did in v1.2.0, in that they can reference secrets in their own or any other namespaces. Additionally, the operator will reconcile DopplerSecrets in other namespaces if all references are in the same namespace as the DopplerSecret itself. For example, a DopplerSecret in the app1 namespace can reference token secrets and managed secrets in app1 only.

Reminder: As a convenience, the namespace may be omitted from secret references in the DopplerSecret resource and the operator will use the DopplerSecret's namespace as the default. This behavior has been in place before v1.2.0 and has not changed.

Assets 3
Loading