Value Statement

Currently, the Maestro gRPC server and gRPC broker share the same certificate and key, which does not align with real-world practices. The gRPC broker typically needs to be exposed publicly to agents, often via an OpenShift route, while the gRPC server can either be exposed publicly or remain internal to the cluster. We should ensure that the gRPC server and broker use different hostnames (URLs) and separate certificates accordingly.

Definition of Done for Engineering Story Owner (Checklist)

• support grpc server and broker serve with separate host(URL) and certificate
• ensure e2e-test on github action can be set up with openshift serving cert.
• ensure grpc broker can be setup with customize certificate when exposed with openshift route.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.