Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Last image version not working with helm #3469

Closed
Lord-Y opened this Issue Nov 14, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@Lord-Y
Copy link

Lord-Y commented Nov 14, 2017

Hi guys, I'm not sure that is the right area to create this issue but the 2.0.0 version of prometheus is not working with helm charts stable/prometheus version 4.6.12.

Here is my values.yaml:

# https://kubeapps.com/charts/stable/prometheus
# helm install stable/prometheus --name prometheus --namespace prometheus -f ~/prometheus.values.yaml
# helm upgrade -i prometheus stable/prometheus --namespace prometheus -f ~/prometheus.values.yaml

server:
  # name: server
  # nameOverride: server
  terminationGracePeriodSeconds: 360
  service:
    type: LoadBalancer
    annotations:
      cloud.google.com/load-balancer-type: "Internal"
  image:
    tag: v2.0.0

configmapReload:
  name: prometheus-server

alertmanager:
  image:
    tag: v0.10.0

nodeExporter:
  image:
    tag: v0.15.1

pushgateway:
  image:
    tag: v0.4.0

kubeStateMetrics:
  image:
    tag: v1.1.0

Here is the output log of the pod:

kubectl logs -n prometheus po/prometheus-prometheus-server-358407101-kk3x3
Error from server (BadRequest): a container name must be specified for pod prometheus-prometheus-server-358407101-kk3x3, choose one of: [prometheus-server-prometheus-server prometheus-server]

Here is the description log of the pod:

  4m		4m		1	kubelet, gke-cluster-test-pool-default-14ead1d6-jf0l	spec.containers{prometheus-server-prometheus-server}	Normal		Pulled			Container image "jimmidyson/configmap-reload:v0.1" already present on machine
  4m		4m		1	kubelet, gke-cluster-test-pool-default-14ead1d6-jf0l	spec.containers{prometheus-server-prometheus-server}	Normal		Started			Started container
  4m		4m		1	kubelet, gke-cluster-test-pool-default-14ead1d6-jf0l	spec.containers{prometheus-server-prometheus-server}	Normal		Created			Created container
  4m		4m		3	kubelet, gke-cluster-test-pool-default-14ead1d6-jf0l	spec.containers{prometheus-server}			Normal		Pulled			Container image "prom/prometheus:v2.0.0" already present on machine
  4m		4m		3	kubelet, gke-cluster-test-pool-default-14ead1d6-jf0l	spec.containers{prometheus-server}			Normal		Created			Created container
  4m		4m		3	kubelet, gke-cluster-test-pool-default-14ead1d6-jf0l	spec.containers{prometheus-server}			Normal		Started			Started container
  4m		4m		3	kubelet, gke-cluster-test-pool-default-14ead1d6-jf0l	spec.containers{prometheus-server}			Warning		BackOff			Back-off restarting failed container
  4m		4m		3	kubelet, gke-cluster-test-pool-default-14ead1d6-jf0l				Warning		FailedSync		Error syncing pod

No matter what I do, the pod is not working at all but everything is fine with version 1.8.2
What else? While execute docker run, the container works perfectly:

docker run -d -ti prom/prometheus:v2.0.0
@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Nov 14, 2017

This sounds like a Helm issue, that you should take up with them.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.