Can we integrate both Kubernetes 1.0 and Kubernetes 2.0?

No. You cannot integrate both at the same time since they perform the same job.

  • Kubernetes 1.0 will be deprecated soon.
  • Kubernetes 2.0 includes all existing features plus additional improvements that make cluster monitoring easier.

What types of Kubernetes resources are supported in Kubernetes 2.0?

K8s 2.0 supports the following resource types:

  • Node
  • Pod
  • Namespace
  • Service
  • Deployment, DaemonSet, ReplicaSet, StatefulSet
  • PersistentVolume (PV)
  • PersistentVolumeClaim (PVC)

Can we auto-update from Kubernetes 1.0 to Kubernetes 2.0 via the portal?

No. Migration is not automated.

  • Customers must reinstall or upgrade manually.
  • Data already collected is retained in OpsRamp; however, live monitoring resumes only after the K8s 2.0 agent is installed and running.

How can we retain previous values during a Helm upgrade?

Use the --reuse-values flag when running the Helm upgrade.

👉 See Installation for step-by-step instructions.

What happens if Kubernetes 2.0 is uninstalled?

  • Uninstalled only from the OpsRamp portal → The integration disappears from the OpsRamp UI, but the agent may still run on the cluster.
  • Uninstalled only from the cluster → The agent is removed, but the integration still shows in the portal until manually deleted.

If a few nodes in the cluster restart, will customers lose data?

No historical data is lost. However:

  • While nodes are offline, the agent cannot monitor their node-level components (logs, traces, metrics).
  • Once the node comes back online, monitoring automatically resumes.