Feature Overview (aka. Goal Summary)

Provide a way for non-it/linux people (aka "Hard hats") to configure and operate MicroShift using the well known RHEL cockpit UX.  

Goals (aka. expected user outcomes)

• Deployments to special environment sometimes need special configuration (e.g. with little/no network, static network etc). Currently, users need to ssh into the system and use vi to edit config files. That is out of the scope for most hard hat users. The goal is to provide a user / non-it people friendly way to change configuration aspects of MicroShift
• Certain day2 operation/troubleshooting activities need more information (e.g. number of pods, CPU/memory consumption etc). 

Requirements (aka. Acceptance Criteria):

1. Provide a basic cockpit plugin that allows for editing MicroShift config file and basic monitoring.

Out of Scope

n/a 

Background

See the shiftweek PoC/Demo from Egli here: https://docs.engineering.redhat.com/pages/viewpage.action?spaceKey=PLUG&title=Edge+Sprint+Demos#EdgeSprintDemos-Sprint245

Customer Considerations

Certain well known EAP customers have asked for a cockpit plugin. We should contact them for further refinement and UX development

Documentation Considerations

• Needs a dedicated book "Configuring and Operating MicroShift using cockpit"

Interoperability Considerations

Must interoperate with the RHEL cockpit