Epic Goal

Support non-kube resources
drafted doc: https://docs.google.com/document/d/1vOM57iGPJfHEmro6FX5maWblboKbCUpUkUiYiozh5Jw/edit?tab=t.0#heading=h.ezdo8tjjsgpy
1. Add a new API for non-kube resource in maestro
2. expose GRPC broker via openshift route
3. Integration maestro client in flightctl server(flightctl worker)
4. Integration maestro client in flightctl agent(flightctl agent)
5. connect flightctl with maestro via gRPC.

6. authenticate against grpc broker with flightctl agent certificate created by device enrollment.

Why is this important?

It can extend maestro into a broad area, including edge.

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.