Question

How can I get managed Kubernetes nodes with DO monitoring agent? I'd like to see RAM graphs...

I can’t figure out a way to SSH on to those nodes (which makes sense); is there any way to get them provisioned with the monitoring agent enabled?

Show comments
Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Michelle Peot • February 13, 2019

We’re currently working on implementing Kubernetes monitoring in the DigitalOcean dashboard, including node performance metrics plus a handful of optional deployment-related kube-state-metrics. The do-agent will run on the nodes by default. We expect monitoring to be out by next month.

daniel258fc95706129a77b165 • February 3, 2019

For others who come here from Google, this is the yaml I’m using to run the DO monitoring agent under DigitalOcean Kubernetes:

apiVersion: v1
kind: Namespace
metadata:
  name: do-agent
---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: do-agent
  namespace: do-agent
spec:
  selector:
    matchLabels:
      name: do-agent
  template:
    metadata:
      labels:
        name: do-agent
    spec:
      volumes:
      - name: proc
        hostPath:
          path: /proc
      - name: sys
        hostPath:
          path: /proc
      containers:
      - name: do-agent
        image: digitalocean/do-agent:1.0.16-rc
        ports:
        - containerPort: 10253
          hostPort: 10253
          protocol: TCP
          name: metrics
        volumeMounts:
        - name: proc
          readOnly: true
          mountPath: /host/proc
        - name: sys
          readOnly: true
          mountPath: /host/sys
        imagePullPolicy: IfNotPresent
        securityContext:
          privileged: true
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      hostNetwork: true
      hostPID: true
  updateStrategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 1