udacity / cnand_nd064_c4_observability_starter_files Goto Github PK

@SudKul - the yaml is actually a cat to kubectl pipe. This file has been introduced in https://github.com/udacity/CNAND_nd064_C4_Observability_Starter_Files/blob/850f0c23867ce391c32b101aa00dd35ef0065abf/Exercise_Starter_Files/hotrod.yaml

curl-ing localhost:30048 issues 500 Internal Server Error due an exception on trial/app.py, missing the main.html template.

Running pods

Error encountered

Issues with deploying trial due to undefined imports.

Running flake8 revealed.

Ran: kubectl apply -Rf manifests/app/

Status of pods: CrashLoopBackOff

Due to missing dependency/

Then, I tried running the app.py inside the container.

The verified if prometheus submodule is available on jaeger_client==4.3.0, which isn't

The Fix

Add prometheus_client==0.9.0 into the requirements.txt

Theres a IP Table bug in OpenSUSE that can be resolved by pinning k3s version.

https://github.com/k3s-io/k3s/releases/tag/v1.19.5+k3s1

https://knowledge.udacity.com/questions/500205

Not sure if this is by design or a copy and paste gone wrong

Hi, @thejaysmith cc: @SudKul

See the knowledge question below, I have submitted multiple Mentor Content Escalation forms wrt to the inconsistencies in this project and lesson. As a mentor, I am in the firing line!

Not sure if this is related to the content under this repo, but it's related to the lessons or project setup

Please note that version 0.7 of "prometheus-community/kube-prometheus-stack" is not available.

The only available versions of "prometheus-community/kube-prometheus-stack" are as follows
helm search repo prometheus -l | grep "prometheus-community/kube-prometheus-stack"

At the moment when you deploy the cluster, the backend service can not get port assigned. This is the project

apiVersion: apps/v1
kind: Deployment
metadata:
  name: backend-app
  annotations:
    "sidecar.jaegertracing.io/inject": "true"
spec:
  replicas: 1
  selector:
    matchLabels:
      app: backend
  template:
    metadata:
      labels:
        app: backend
    spec:
      containers:
      - name: backend
        image: martinezi/metrics-backend
        ports:
        - containerPort: 8080
---
apiVersion: v1
kind: Service
metadata:
  name: backend-service
spec:
  selector:
    app: backend
  ports:
    - port: 80
      targetPort: 8080
  type: LoadBalancer

➜  Project_Starter_Files-Building_a_Metrics_Dashboard git:(main) ✗ kubectl describe pod svclb-backend-service-zjnx4
Name:           svclb-backend-service-zjnx4
Namespace:      default
Priority:       0
Node:           <none>
Labels:         app=svclb-backend-service
                controller-revision-hash=9fcfcdcf5
                pod-template-generation=1
                svccontroller.k3s.cattle.io/svcname=backend-service
Annotations:    <none>
Status:         Pending
IP:             
IPs:            <none>
Controlled By:  DaemonSet/svclb-backend-service
Containers:
  lb-port-80:
    Image:      rancher/klipper-lb:v0.1.2
    Port:       80/TCP
    Host Port:  80/TCP
    Environment:
      SRC_PORT:    80
      DEST_PROTO:  TCP
      DEST_PORT:   80
      DEST_IP:     10.43.116.140
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-dq4k4 (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  default-token-dq4k4:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-dq4k4
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     CriticalAddonsOnly op=Exists
                 node-role.kubernetes.io/master:NoSchedule op=Exists
                 node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                 node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                 node.kubernetes.io/not-ready:NoExecute op=Exists
                 node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                 node.kubernetes.io/unreachable:NoExecute op=Exists
                 node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  6h6m  default-scheduler  0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports.

I have done some research, and it seems traefik is already is using the port. I am not sure how to proceed, to get the backend to work.

Requirement lacking redis-opentracing. Please add this: redis-opentracing==1.0.0

For the manifests in app folder, image referred is ghcr.io/thejaysmith/mybackend:v1
I am able to pull myfrontend but for mybackend and mytrial, it says denied

docker pull ghcr.io/thejaysmith/mytrial:v1
Error response from daemon: Get https://ghcr.io/v2/thejaysmith/mytrial/manifests/v1: denied

Url -
https://github.com/udacity/CNAND_nd064_Building_a_Metrics_Dashboard_Starter_Files/blob/master/manifests/app/backend.yaml#L17

Issue regarding OpenSuse image version constraint.

System Info

Note: redis-opentracing depends on opentracing >=2.0,<2.1': https://github.com/opentracing-contrib/python-redis/blob/master/setup.py#L16+L19
This becomes an issue when trying to install jaeger-client All versions

$ cat tracing-extra/app/requirements.txt

certifi==2020.12.5
chardet==4.0.0
click==7.1.2
Flask-OpenTracing==1.1.0
Flask==1.1.2
gunicorn==20.0.4
idna==2.10
itsdangerous==1.1.0
jaeger-client==4.4.0
Jinja2==2.11.2
MarkupSafe==1.1.1
opentracing==2.4.0
redis-opentracing==1.0.0
redis==3.5.3
requests==2.25.1
six==1.15.0
threadloop==1.0.2
thrift==0.13.0
tornado==6.1
urllib3==1.26.2
Werkzeug==1.0.1

The first setup for completing the project is start the virtual machine using:

vagrant up

Nevertheless, the Vagrantfile states:

config.vm.provision "k3s shell script", type: "shell", path: "scripts/k3s.sh", args: args

For consistency, it should be:

config.vm.provision "k3s shell script", type: "shell", path: "k3s.sh", args: args

Another option is ask the student to create the scripts folder and move/copy the bash script there.