Master node in schedulingDisabled state after updating "timeoutSeconds" for calico

Problem

  • Master node in Scheduling disabled state after updating "timeoutSeconds" for calico.

  • Nodelet phases failing with below error:

{"L":"INFO","T":"2023-02-01T03:57:35.894Z","C":"command/command.go:120","M":"[2023-02-01 03:57:35] F0201 03:57:35.303556 14263 helpers.go:115] error: error validating \"/opt/pf9/pf9-kube/conf/networkapps/calico-v1.20.11-configured.yaml\": error validating data: ValidationError(Deployment.spec.template.spec.containers[0].readinessProbe.exec): unknown field \"timeoutSeconds\" in io.k8s.api.core.v1.ExecAction; if you choose to ignore these errors, turn validation off with --validate=false"}

Environment

  • Platform9 Managed Kubernetes - v5.4 and Higher

Cause

  • timeSeconds value was updated at incorrect place in opt/pf9/pf9-kube/conf/networkapps/calico-v1.20.11-configured.yaml

Resolution

  • On ALL master nodes part of the cluster, add parameter timeoutSeconds: 10in files /opt/pf9/pf9-kube/conf/networkapps/calico-v1.20.11.yaml & /opt/pf9/pf9-kube/conf/networkapps/calico-v1.20.11-configured.yaml respectively at 2 sections i.e in Probes for calico-kube-controllers Deployment & calico-node DaemonSet Spec.

Additional Information


© 2025 Platform9. All Rights Reserved

On This Page
Master node in schedulingDisabled state after updating "timeoutSeconds" for calicoProblemEnvironmentCauseResolutionAdditional Information