-
Story
-
Resolution: Won't Do
-
Major
-
0.13.0
-
None
-
2020 Week 34-36 (from Aug 17)
Goal
Have an endpoint on Kogito services that can be fetched by third party actors to know about the infrastructure needed by the service.
Description
As an user, I wish to deploy a custom Kogito service on a Kubernetes cluster that can be configured automatically by operators without manual intervention, or having to describe the infrastructure details on Kubernetes resources.
Implementation
Design docs is in the way, but we basically need an endpoint being on Kogito services (being custom or support services) that describes what it needs to run like:
1. Kafka Topics
2. Knative Resouces
3. Persistence implementation
4. Graphana Dashboards
5. Prometheus metrics (on/off)
... and so on
That way Kogito Operator can fetch this endpoint and provision the needed infrastructure requirements for the Kogito service being deployed.
- blocks
-
KOGITO-1061 Provision Grafana dashboard using operator
- Closed
-
KOGITO-2562 Serverless Workflow support on Operator
- Resolved
- is blocked by
-
KOGITO-3136 Create a design doc and PoC to validate infrastructure metadata endpoint story
- Closed
-
KOGITO-3204 Generate Monitoring, Persistence and Events infrastructure information as a static file in build time
- Closed
-
KOGITO-3206 Provide a lightweight HTTP endpoint on Kogito base images to serve infrastructure details
- Closed
-
KOGITO-3207 Consume infrastructure metadata information from Kogito service being deployed
- Closed
- is related to
-
KOGITO-2760 Review Data Index image and operator to handle switching persistence type
- Closed
-
KOGITO-2762 Review support for runtime configuration using MongoDB persistence
- Closed
-
KOGITO-3039 Agnostic infrastructure layer configuration on Operator
- Resolved