This guide is meant to help the user understand how to get up and running with the Observability Operator locally with kind
TOC
This guide is meant to help the user understand how to get up and running with the Observability Operator locally with kind
TOC
TOC
This is the demo app that we will use for the remainder of the doc
Description For integration testing and samples to deploy operators, kind clusters are being used currently. We need a small factor OpenShift to perform evaluation and evaluate the constraints and benefits of using microshift. Ideally, we would need a gist about the good experience and pain point w.r.t to kind clusters.
TOC
We will federate the Kong Mesh Prometheus to the OpenShift Prometheus. We will then leverage OpenShift Monitoring to handle the aggregated metrics.
Pending
ServiceMonitor to dedupe metrics from KongTOC
We will create two namespaces, mesh, which is where the service mesh resides, and the blue namespace where our apps reside.
We will create a service in the mesh namespace called mesh, and a corresponding service of type ExternalName in the blue namespace called mesh-external, representing the mesh service in the mesh namespace.
kubectl create ns mesh
kubectl create ns blue
Definition of Done:
Payment Gateway is one of the aspects of the monetization. Setting up the plan and metering is other aspect. In 3scale we definitely have these 3 capabilities. So, the first ask is how are all these features work in hypercurrent.io? Does it provides complete monetization features and how? Then, in 3scale how are providing this feature, are we using some kind of plugin or is it in built in?
TOC
We are going to deploy an app called Blue which has a healthcheck endpoint, metrics endpoint, and a RemoteWrite endpoint that consumes prometheus metrics. We will scrape metrics from the application, create alerts, a GrafanaDashboard, and consume Prometheus data through an endpoint.
The steps have been tried on OpenShift 4.9 using MacOS.