Skip to main content
NetApp Knowledge Base

Trident Controller Pod scales up and down constantly

  1. Last updated
  2. Save as PDF
Views:
15
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • Trident
  • Kubernetes
  • Redhat OpenShift

Issue

Describing the events on the Trident-Controller shows 2 distinct controller pods competing for resources
 

Events:
Type    Reason             Age                       From                   Message
----    ------ ----                      ----                   -------
Normal  ScalingReplicaSet  26m (x15011 over 6d5h)    deployment-controller  Scaled down replica set trident-controller-b795u8122 to 0 from 1
Normal  ScalingReplicaSet  11m (x14929 over 6d5h) deployment-controller  Scaled up replica set trident-controller-aa134u8123 to 1 from 0
Normal  ScalingReplicaSet  6m45s (x15046 over 6d5h)  deployment-controller  Scaled up replica set trident-controller-b795u8122 to 1 from 0
Normal  ScalingReplicaSet  106s (x14948 over 6d5h)   deployment-controller  Scaled down replica set trident-controller-aa134u8123 to 0 from 1
 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.