observe-k8s / observe-k8s-demo Goto Github PK

To provide value we need to create different type of disruptions.

1. on the Application level by generating memroy hog or cpu hog on specific container.
2. introduce latency between the redis database on the carservice
3. inject memory hog on the ingress
4. introduce network latency between the frontend service and the produccatalog

provide chaos worklow for kubernetes:

• node drain
• node cpu hog
• node memory hog
• kill kubelet-

Upgrade the current version of the demo with the latest version of the otel-demo

to let the end user the ability to analyze a given problem, it would require to simulate fake problems.
For this, we would need to use an existing Chaos engineering solution that would schedule regular disruptions.

I would suggest using a lightweight chaos engineering solution for our demo.

To make the deployment of the environment easier, we should consider to create a helm chart deploying most of the components of the demo

The objective is to create a set of dashboards useful for platform owners.
We can rely on existing dashboard built by the community to report the health of the cluster, namespace, workload...and more.

To provide a good experience to the end user, we need to provide a dashboard to will be application focus with :

• few SLO reporting availability, latency, and more
• health dashboard helping the user to look at a metric , get the related traces and logs

we need to build dashboard that will be aligned with the whitepaper.

I cant seem to get the loki installation to work

https://github.com/observe-k8s/Observe-k8s-demo/tree/gke?tab=readme-ov-file#deploy-loki

I do not see any installation with the helm upgrade

 kubectl get svc -n loki -l app=loki
No resources found in loki namespace.

kubectl get pods -n loki
NAME                                          READY   STATUS    RESTARTS   AGE
loki-backend-0                                2/2     Running   0          11h
loki-backend-1                                2/2     Running   0          11h
loki-backend-2                                2/2     Running   0          11h
loki-canary-29rpr                             1/1     Running   0          11h
loki-canary-8plhf                             1/1     Running   0          11h
loki-canary-mnlp9                             1/1     Running   0          11h
loki-gateway-6945457dd5-rqf9v                 1/1     Running   0          11h
loki-grafana-agent-operator-d7c684bf9-fw5wj   1/1     Running   0          11h
loki-logs-2xjwt                               2/2     Running   0          11h
loki-logs-lrdqt                               2/2     Running   0          11h
loki-logs-wj8jx                               2/2     Running   0          11h
loki-read-76f88b756f-8m42s                    1/1     Running   0          11h
loki-read-76f88b756f-hvhm6                    1/1     Running   0          11h
loki-read-76f88b756f-k9kfp                    1/1     Running   0          11h
loki-write-0                                  1/1     Running   0          11h
loki-write-1                                  1/1     Running   0          11h
loki-write-2                                  1/1     Running   0          11h

Any suggestions?

Similar to the otel demo we need to create a precise documentation to make sure our community is able to use the demo and understand the value of it.