Skip to content

[TASK] Agree on architecture/implementation details for secrets management APIs #633

@andyatmiami

Description

@andyatmiami

Certification

  • I certify I am an Epic Owner for Kubeflow Notebooks 2.0 and expected to create planning-related issues.

Description

As a community, we need to agree on how the Secrets Management APIs will be designed and implemented. An initial proposal has been worked on by @andyatmiami and @thaorell and written up as a Markdown file:

We need to review and revise this document so that the expectations on the Secrets API is well-defined and able to be used as a source of truth for implementation.

Acceptance Criteria

  • API Proposal for Secrets Management API is agreed upon by community

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Needs Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions