Skip to content

Lack of Documentation in Key Areas #231

@smithmiro7-ui

Description

@smithmiro7-ui

Lack of Documentation in Key Areas

There is a lack of documentation in several important areas:

  1. Development Environment

When attempting to test new features, it takes a significant amount of time to properly set up the development environment and run the project locally.

  1. Running Locally

After executing make run, numerous go vet errors are encountered, with no clear guidance on how to resolve them.

  1. Debugging

There is no documentation explaining how to debug the operator (e.g., profiling, adjusting log levels, etc.).

  1. Development Cycle

There is no clear documentation describing the development workflow, including how to make changes, test them, and validate the results end-to-end.

Proposal

I propose adding comprehensive documentation that covers these topics to improve the developer and tester experience.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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