-
Notifications
You must be signed in to change notification settings - Fork 558
Heapster nanny container fails to start with Kubernetes 1.9.3 #2430
Comments
@adelina-t Which image version are you using with heapster-nanny? e.g. you could get by kubectl -n kube-system get pod heapster-7cd8dd888b-4556z -o yaml |
@feiskyer Seems like it's: k8s-gcrio.azureedge.net/addon-resizer:1.8.1 Full pod spec:
|
@adelina-t Current config only applies to add-resizer v1.7, e.g. replace image with Or if addon-resizer 1.8.1 is required, apiVersion: v1
kind: ServiceAccount
metadata:
name: heapster
namespace: kube-system
labels:
kubernetes.io/cluster-service: "true"
addonmanager.kubernetes.io/mode: Reconcile
---
apiVersion: v1
kind: ConfigMap
metadata:
name: heapster-config
namespace: kube-system
labels:
kubernetes.io/cluster-service: "true"
addonmanager.kubernetes.io/mode: EnsureExists
data:
NannyConfiguration: |-
apiVersion: nannyconfig/v1alpha1
kind: NannyConfiguration
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: heapster
namespace: kube-system
labels:
k8s-app: heapster
kubernetes.io/cluster-service: "true"
addonmanager.kubernetes.io/mode: Reconcile
addonmanager.kubernetes.io/mode: EnsureExists
spec:
replicas: 1
selector:
matchLabels:
k8s-app: heapster
template:
metadata:
labels:
k8s-app: heapster
annotations:
scheduler.alpha.kubernetes.io/critical-pod: ''
spec:
priorityClassName: system-cluster-critical
containers:
- image: k8s.gcr.io/heapster-amd64:v1.5.0
name: heapster
resources:
limits:
cpu: 88m
memory: 204Mi
requests:
cpu: 88m
memory: 204Mi
livenessProbe:
httpGet:
path: /healthz
port: 8082
scheme: HTTP
initialDelaySeconds: 180
timeoutSeconds: 5
command:
- /heapster
- --source=kubernetes.summary_api:''
- image: k8s.gcr.io/addon-resizer:1.8.1
name: heapster-nanny
resources:
limits:
cpu: 88m
memory: 204Mi
requests:
cpu: 88m
memory: 204Mi
env:
- name: MY_POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: MY_POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
volumeMounts:
- name: heapster-config-volume
mountPath: /etc/config
command:
- /pod_nanny
- --config-dir=/etc/config
- --cpu=80m
- --extra-cpu=0.5m
- --memory=140Mi
- --extra-memory=4Mi
- --threshold=5
- --deployment=heapster
- --container=heapster
- --poll-period=300000
- --estimator=exponential
volumes:
- name: heapster-config-volume
configMap:
name: heapster-config
serviceAccountName: heapster
tolerations:
- key: "CriticalAddonsOnly"
operator: "Exists" |
@jackfrancis I see addon-resizer version has been rolled back in #2090. You can refer above manifests to fix addon-resizer:1.8.1 |
@feiskyer I interpret your comments as a suggestion to add a new version of this spec to pair w/ addon-resizer v1.8.1: Which versions of Kubernetes do you recommend that we deliver a modified heapster addon spec + addon-resizer v1.8.1 with? Thanks so much! |
@jackfrancis Yep, I suggest we add addon-resizer:v1.8.1 with kubernetes v1.9.x and above versions. Addons in Kubernetes repo are also using resizer v1.8.1 from v1.9.x |
Looks like 1.9.6 works |
ISSUE:
v0.13.1:
Kubernetes 1.9.3
What happened:
Cluster deployed with Kubernetes 1.9.3 has failed heapster pod.
How to reproduce it (as minimally and precisely as possible):
Deploy basic cluster from template with orchestrator Kubernetes 1.9.3
Anything else we need to know:
Logs from inside the heapster nanny pod:
The text was updated successfully, but these errors were encountered: