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

[helm] Deploying loki-stack with prometheus & grafana fails in k8s 1.16 #1080

Closed
OJFord opened this issue Sep 28, 2019 · 3 comments · Fixed by #1238
Closed

[helm] Deploying loki-stack with prometheus & grafana fails in k8s 1.16 #1080

OJFord opened this issue Sep 28, 2019 · 3 comments · Fixed by #1238
Labels
component/packaging good first issue These are great first issues. If you are looking for a place to start, start here! help wanted We would love help on these issues. Please come help us! keepalive An issue or PR that will be kept alive and never marked as stale.

Comments

@OJFord
Copy link

OJFord commented Sep 28, 2019

Describe the bug
Due to deprecated apiVersions removed in 1.16, the prometheus & grafana dependencies fail to install.

stable/grafana is fixed (currently 3.8.15) but stable/prometheus remains broken, pending helm/charts#17268.

To Reproduce

  1. helm install loki/loki-stack --set=grafana.enabled=true,prometheus.enabled=true

Expected behavior
Loki, grafana, and prometheus installed.

Environment:

  • Infrastructure: kubernetes 1.16
  • Deployment tool: helm

Screenshots, promtail config, or terminal output

Above repro fails:

Error: apiVersion "apps/v1beta2" in loki-stack/charts/grafana/templates/deployment.yaml is not available

Full errors (from helm template | kubectl apply -f -):

unable to recognize "STDIN": no matches for kind "DaemonSet" in version "extensions/v1beta1"
unable to recognize "STDIN": no matches for kind "Deployment" in version "apps/v1beta2"
unable to recognize "STDIN": no matches for kind "Deployment" in version "extensions/v1beta1"
unable to recognize "STDIN": no matches for kind "Deployment" in version "extensions/v1beta1"
unable to recognize "STDIN": no matches for kind "Deployment" in version "extensions/v1beta1"
unable to recognize "STDIN": no matches for kind "Deployment" in version "extensions/v1beta1"
unable to recognize "STDIN": no matches for kind "PodSecurityPolicy" in version "extensions/v1beta1"
unable to recognize "STDIN": no matches for kind "PodSecurityPolicy" in version "extensions/v1beta1"

The two policies are fixed by using grafana==3.8.15, but the remaining issues will require helm/charts#17268.

@OJFord OJFord changed the title [helm] Deploying loki-stack with prometheus & grafana fails in k8s 1.16 Deploying loki-stack with prometheus & grafana fails in k8s 1.16 Sep 28, 2019
@OJFord OJFord changed the title Deploying loki-stack with prometheus & grafana fails in k8s 1.16 [helm] Deploying loki-stack with prometheus & grafana fails in k8s 1.16 Sep 28, 2019
@daixiang0
Copy link
Contributor

daixiang0 commented Sep 29, 2019

Since in 1.16, extensions/v1beta1 has been abondoned.
Need wait for upstream fix.

@OJFord
Copy link
Author

OJFord commented Sep 29, 2019

What upstream fix? As I said grafana==3.8.15 is using policy/v1, so those last two are fixed, and the remainder are from prometheus and being addressed in helm/charts#17268.

@cyriltovena cyriltovena added component/packaging good first issue These are great first issues. If you are looking for a place to start, start here! hacktoberfest help wanted We would love help on these issues. Please come help us! keepalive An issue or PR that will be kept alive and never marked as stale. labels Sep 30, 2019
@oke-py
Copy link
Contributor

oke-py commented Nov 7, 2019

helm/charts#17268 merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/packaging good first issue These are great first issues. If you are looking for a place to start, start here! help wanted We would love help on these issues. Please come help us! keepalive An issue or PR that will be kept alive and never marked as stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants