Skip to content

feature: Implement secretRef for oidc client secret in Custom Resources instead of string value #130

@MuneebAijaz

Description

@MuneebAijaz

Feature Description

Currently the secret value is added as a string in the custom resources, which isn't considered safe. It's recommended to use secretRef instead to pass credentials.

Proposed Solution

For now, both implementations can exist to avoid breaking changes.

  auth:
    oidc:
      clientID: xyz
      clientSecret: abc
      secretRef:
        name: oidc-client-secret
        namespace: kcp-operator

Alternative Solutions

Nothing at the moment.

Want to contribute?

  • I would like to work on this issue.

Additional Context

No response

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions