cmwylie19

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  annotations:
  name: monitoring-operators
  namespace: openshift-marketplace
spec:
  displayName: Monitoring Test Operator
  icon:
    base64data: ""

cmwylie19

apiVersion: monitoring.rhobs/v1alpha1
kind: MonitoringStack
metadata:
  name: starburst
  namespace: <installation_namespace>
spec:
  logLevel: debug
  prometheusConfig:
    remoteWrite:
    - bearerToken: redacted

cmwylie19

apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  labels:
    app: starburst-enterprise
  name: starburst-monitor
  namespace: <installation_namespace>
spec:
  endpoints:
  - port: metrics

cmwylie19

apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule 
metadata:
  creationTimestamp: null
  labels:
    prometheus: starburst
  name: starburst-rules
  namespace: <installation_namespace>
spec:
  groups:

cmwylie19

apiVersion: monitoring.coreos.com/v1alpha1
kind: AlertmanagerConfig
metadata:
  name: starburst-pagerduty
  namespace: <installation_namespace>
  labels:
    alertmanagerConfig: starburst
spec:
  route:
    groupBy: [alertname,cluster,service,job]

cmwylie19

MSO Deployment with OLM

The steps have been tried on OpenShift 4.9 using MacOS.

• Clone the Monitoring Stack Operator repository
• Login into your quay repository
• Export environment variables
• Building images
• Deploy the operator

cmwylie19

Monitoring Stack Operator Demo

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.

• Install MSO
• Deploy Sample App
• Deploy MSO
• Deploy ServiceMonitor
• Deploy PrometheusRule
• Prometheus RemoteWrite Endpoints
• Deploy GrafanaDashboard

cmwylie19

Gateway Monetization

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

• 3scale Monetization Capabilities
• How 3scale Monetization Works
• HyperCurrent Monetization Capabilities
• How HyperCurrent Monetization Works
• Commonalities between 3scale and Kong Payments

cmwylie19

Test ExternalName Service across Namespaces

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.

Setup namespaces

kubectl create ns mesh 
kubectl create ns blue

cmwylie19

Prometheus Operator

To install, create the namespace, operatorgroup, and subscription.

oc apply -f -<<EOF
apiVersion: v1
kind: Namespace
metadata:
  creationTimestamp: null
 name: prometheus