Skip to content

Convergence of APIKeyRequest & APIKeyApproval #48

@didierofrivia

Description

@didierofrivia

The current implementation of the APIKey feature involves 3 key resources, as defined in the Kuadrant console plugin design document.

It would be valuable to at least consider a different approach simplifying the amount of objects needed for the management of issuing API keys to just 2, similar to what the Cert Manager does when issuing X.509 certificates:

The objective of this issue is to evaluate if it makes sense for us to align with similar battle tested solutions such as cert manager, and what would involve for us making the change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for Feature.

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions