Skip to content

Better definition of spec, status and config for the Operator to control the application #73

Description

@kirankt

Currently we have 'spec' and 'config' sections in the Operator's CR. We need better separation of these. Also, we could utilize the 'status' struct.

Reference: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions