Feature Overview (aka. Goal Summary)

An elevator pitch (value statement) that describes the Feature in a clear,
concise way.

The scaffolder backend module kubernetes was contributed in the early days of Janus IDP and RHDH. As such it seems like the scaffolder action was not properly added to RHDH. This feature is to capture the work that will be required to properly add the module.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

Add the kubernetes action to RHDH, contribute the e2e tests, and contribute documentation for the action.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

Plugin work has already been completed. So this is mainly a feature to capture the work that is still left.

• Docs
• E2E

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.

Currently the documentation that we have includes the plugin readme.

Support level will be Tech Preview for now. We can consider full support in next version