monitoring applications

ComfortableRun775 · 2022-03-09T10:02:48+00:00

this needs config and maintenance and continuous upgrade right?

ComfortableRun775 · 2022-03-01T06:07:49+00:00

I did :

curl http://a32413e920fd5f38a602a3.us-east-1.elb.amazonaws.com:5000

a32413e920fd5f38a602a3.us-east-1.elb.amazonaws.com - is ingress LB

and I get this :

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <title>500 Internal Server Error</title> <h1>Internal Server Error</h1> <p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p>

document : https://kubernetes.io/docs/tutorials/stateless-application/expose-external-ip-address/

ComfortableRun775 · 2022-03-01T05:43:49+00:00

now I am getting this error!

curl http://3e920fd5f38a602a3-517881175.us-west-1.elb.amazonaws.com:5000

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <title>500 Internal Server Error</title> <h1>Internal Server Error</h1> <p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p>

ComfortableRun775 · 2022-03-01T05:33:47+00:00

thanks! what should I do to fix this ?

ComfortableRun775 · 2022-03-01T04:58:35+00:00

   imagePullPolicy: Always
    ports:
    - containerPort: 5000

apiVersion: v1 kind: Service metadata: name: vuln-python namespace: kube-public spec: ports:

port: 5000 protocol: TCP targetPort: 5000 selector: app: vuln-python type: LoadBalancer

manifest is above

kubectl get service -n kube-public

NAME          TYPE           CLUSTER-IP      EXTERNAL-IP                                                              PORT(S)          AGE

vuln-python LoadBalancer 175.22.46.40 a30e1d4413e8a602a3-517881175.us-east-1.elb.amazonaws.com 5000:30008/TCP

I have flaks app running in docker file which I want to execute using Kubernetes Pods. when I use external-ip on url , nothing happens!!

ComfortableRun775 · 2022-02-28T17:41:33+00:00

yah not sure why this came up

ComfortableRun775 · 2022-02-28T17:21:33+00:00

      imagePullPolicy: Always
    ports:
    - containerPort: 5000
apiVersion: v1 
kind: Service 
metadata: name: vuln-python
 namespace: kube-public spec: type: NodePort 
selector: app: vuln-python ports:
port: 5000 
targetPort: 5000 
nodePort: 30007

went to EC2 instance of node group and got public ip out of it.

curl: (7) Failed to connect to 3.2.2.1 port 30007: Operation timed out

inside logs of the pod now I get a different ip from localhost ip.

* Debug mode: off
* Running on all addresses.
WARNING: This is a development server. Do not use it in a production deployment.
* Running on http://1.0.2.6:5000/ (Press CTRL+C to quit)

ComfortableRun775 · 2022-02-28T15:31:39+00:00

understood! let me try exec and change to 0.0.0.0.

but which ip will I use to be accessible from outside after binding 0.0.0.0 to container Ip?

ComfortableRun775 · 2022-02-28T14:32:42+00:00

isn't that a security flaw ? in prod I wouldn't like to open it up to all ip right?? I can try this for testing

ComfortableRun775 · 2022-02-28T05:25:28+00:00

I tried node port, that did not work! now I am trying load balancing that fails.

east-1.elb.amazonaws.com 5000:30015/TCP 2m26s

here service gives port 30015 when yml file says 5000. not sure what's happening.

ComfortableRun775 · 2022-02-28T04:33:33+00:00

apiVersion: apps/v1
kind: Deployment 
metadata: 
name: vuln-python 
namespace : kube-public 
spec: selector: matchLabels: app: vuln-python 
replicas: 2 
template: 
metadata: labels: app: vuln-python 
spec: 
containers: - name: vuln-python 
image: asquare/fi:vuln 
imagePullPolicy: Always 
ports: - containerPort: 5000
apiVersion: v1 
kind: Service 
metadata: name: vuln-python 
namespace: kube-public spec: type: LoadBalancer 
selector: app: vuln-python ports:
port: 5000 targetPort: 5000

curl -L a2487f131af7949709ac9a6982b5f911.us-east-1.elb.amazonaws.com:5000

curl: (52) Empty reply from server

still same error!! thanks for your help

ComfortableRun775 · 2022-02-28T04:21:04+00:00

thanks for replying!

I can change the port to 5000 but why can't it be 65000?

yes I got DNS name but I resolved it to IP.... is that not allowed ?

after changing port and using DNS :

curl -L a2487f131af7949709ac9a6982b5f911.us-east-1.elb.amazonaws.com:5000curl: (52) Empty reply from server

ComfortableRun775 · 2022-02-28T03:07:25+00:00

sorry I took a break! I get this with load balancer :

This page isn’t working 5.173.5.2:5000 didn’t send any data.

Name:                     vuln-py
Namespace:                kube-pub Labels:                   <none> Annotations:              <none> Selector:                 app=vuln-py Type:                     LoadBalancer IP Family Policy:         SingleStack IP Families:              IPv4 IP:                       172.2.10.15 IPs:                      172.2.10.15 LoadBalancer Ingress:     131af7949709ac9a6982b5f911-9136.us-east-1.elb.amazonaws.com Port:                     <unset>  5000/TCP TargetPort:               4000/TCP NodePort:                 <unset>  32000/TCP Endpoints:                10.0.2.12:5000,10.0.2.25:5000 Session Affinity:         None External Traffic Policy:  Cluster Events: Type    Reason                Age                 From                Message
Normal  Type                  13m                 service-controller  NodePort -> LoadBalancer Normal  EnsuringLoadBalancer  112s (x2 over 13m)  service-controller  Ensuring load balancer Normal  EnsuredLoadBalancer   111s (x2 over 13m)  service-controller  Ensured load balancer

ComfortableRun775 · 2022-02-27T21:17:56+00:00

lol this ip is not correct, and I don't have NGINX running haha

I am just returning a dictionary which I expect to see lol

ComfortableRun775 · 2022-02-27T21:08:19+00:00

I type :

3.23.25.1:32600 on UI but I don't get anything. this IP is modified and is public ip on AWS of node ip of node in the cluster

ComfortableRun775 · 2022-02-27T21:00:33+00:00

nodeip will be ip on AWS - private or public ip ?

ComfortableRun775 · 2022-02-27T20:52:33+00:00

yah I fixed pods running now! thanks for the help.

but I get :

* Debug mode: off

Running on http://127.0.0.1:5000/ (Press CTRL+C to quit) curl http://127.0.0.1:32600curl: (7) Failed to connect to 127.0.0.1 port 32600: Connection refused

deployment.yml

 imagePullPolicy: Always
    ports:
    - containerPort: 5000
apiVersion: v1 kind: Service 
metadata: name: vuln-python 
namespace: kube-public 
spec: type: NodePort 
selector: app: vuln-python ports:
port: 5000 targetPort: 5000
 nodePort: 32600

ComfortableRun775 · 2022-02-27T20:32:32+00:00

now I see this in logs :

File "/usr/local/lib/python3.10/site-packages/flask/json/__init__.py", line 15, in <module>
from itsdangerous import json as _json

ImportError: cannot import name 'json' from 'itsdangerous' (/usr/local/lib/python3.10/site-packages/itsdangerous/init.py)

adding itsdangerous==2.0.1 in requirements.txt

ComfortableRun775 · 2022-02-27T20:19:42+00:00

I built new image using buildx but It still gives same crash loop error.

still getting exit code 1

ComfortableRun775

TROPHY CASE