Second LIfe

docker run -it -d --name prometheus -p 9090:9090  -v /home/prometheus/prometheus.yml:/etc/prometheus/prometheus.yml -v /home/prometheus:/prometheus dockertest2.io:12000/prometheus:latest --config.file=/etc/prometheus/prometheus.yml --web.listen-address="0.0.0.0:9090" --web.enable-lifecycle

prometheus.yml

# my global config
global:
  scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
  evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
  # scrape_timeout is set to the global default (10s).

  # Attach these labels to any time series or alerts when communicating with
  # external systems (federation, remote storage, Alertmanager).
  external_labels:
      monitor: 'codelab-monitor'

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  # - "first.rules"
  # - "second.rules"

# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
  # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
  - job_name: 'prometheus'

    # metrics_path defaults to '/metrics'
    # scheme defaults to 'http'.

    static_configs:
      - targets: ['localhost:9090']

  - job_name: 'docker'
         # metrics_path defaults to '/metrics'
         # scheme defaults to 'http'.

    static_configs:
      - targets: ['localhost:9323']

[참고용]

docker run -d -p 42047:9090 --name=prometheus -v /home/test/prometheus.yml:/etc/prometheus/prometheus.yml --link cadvisor:cadvisor prom/prometheus -config.file=/etc/prometheus/prometheus.yml -log.level=debug -storage.local.path=/prometheus -storage.local.memory-chunks=10000

[root@hadoopm KUBE]# more deployment-definition2.yml

apiVersion: apps/v1beta1

kind: Deployment

metadata:

  name: myapp-deployment

  labels:

    app: myapp

    type: front-end

spec:

  template:

    metadata:

      name: myapp-pod

      labels:

        app: myapp

    spec:

      containers:

        - name: nginx-container

          image: dockertest2.io:12000/nginx:latest

  replicas: 3

  selector:

    matchLabels:

      app: myapp

Algorithm: Random

SessionAffinity: Yes

minikube일 경우 minikube ip를 통해 ip를 알아내고 

해당 ip:30008로 통신한다

연결이 안되면 service-definition.yml에서  type: front-end를 삭제해보자... pod쪽에서 찾지를 못해  조건에 맞는 pod를 못찾아서 생긴 문제

Deployment create or apply -f 파일이름 실행시 아래와 같이 에러 메세지 출력 (참고 apiVersion: apps/v1)

[root@hadoopm KUBE]# kubectl apply -f deployment-definition.yml

Error from server (BadRequest): error when creating "deployment-definition.yml": Deployment in version "v1" cannot be handled as a Deployment: no kind "Deployment" is registered for version "apps/v1"

root@hadoopm KUBE]# kubectl  version

Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.0", GitCommit:"d3ada0119e776222f11ec7945e6d

뭐 이렇게 하는게 맞는진 모르지만

암튼..

K8S가 1.9 밑에 버젼 1.8 이나 1.7 버젼이면 apiVersion: apps/v1beta1   <=요렇게 변경해준다 1.9이상이면 에러가 안나겠죵(apps/v1)

그럼 된다..

-----------------deployment-definition.yml ------------------------------

apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp-deployment
  labels:
    app: myapp
    type: front-end
spec:
  template:
    metadata:
      name: myapp-pod
      labels:
        app: myapp
        type: front-end
    spec:
       containers:
         - name: nginx-container
           image: dockertest2.io:12000/nginx:latest
  replicas: 3
  selector:
    matchLabels:
      type: front-end

[root@hadoopm KUBE]# kubectl get deployments

NAME               DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE

myapp-deployment   3         3         3            3           6m

nginx              1         1         1            1           5d

[root@hadoopm KUBE]# kubectl get replicaset

NAME                          DESIRED   CURRENT   READY     AGE

myapp-deployment-3571195553   3         3         3         6m

nginx-2496978322              1         1         1         5d

[root@hadoopm KUBE]# kubectl get pods

NAME                                READY     STATUS    RESTARTS   AGE

myapp-deployment-3571195553-27hgj   1/1       Running   0          7m

myapp-deployment-3571195553-7hzvr   1/1       Running   0          7m

myapp-deployment-3571195553-gw4xn   1/1       Running   0          7m

[1]+  Stopped                 ./prometheus --web.listen-address="0.0.0.0:9090" --web.enable-lifecycle

root@workstation:/home/edu3/prometheus-2.3.2.linux-amd64# bg

[1]+ ./prometheus --web.listen-address="0.0.0.0:9093" --web.enable-lifecycle &

root@workstation:/home/edu3/prometheus-2.3.2.linux-amd64# curl -X POST http://localhost:9093/-/reload

level=info ts=2018-07-13T05:25:49.600841981Z caller=main.go:603 msg="Loading configuration file" filename=prometheus.yml

level=info ts=2018-07-13T05:25:49.601703886Z caller=main.go:629 msg="Completed loading of configuration file" filename=prometheus.yml

위치 :

/etc/systemd/system/kubelet.service.d/10-kubeadm.conf

root@nevido home]# more 10-kubeadm.conf
# Note: This dropin only works with kubeadm and kubelet v1.11+
[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf"
Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml"
Environment="KUBELET_CGROUP_ARGS=--cgroup-driver=cgroupfs"
# This is a file that "kubeadm init" and "kubeadm join" generates at runtime, populating the KUBELET_KUBEADM_ARGS variable dynamically
EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env
# This is a file that the user can use for overrides of the kubelet args as a last resort. Preferably, the user should use
# the .NodeRegistration.KubeletExtraArgs object in the configuration files instead. KUBELET_EXTRA_ARGS should be sourced from this file.
EnvironmentFile=-/etc/sysconfig/kubelet
ExecStart=
ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS $KUBELET_CGROUP_ARGS

systemctl daemon-reload
systemctl restart kubele