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

[bug] Cannot install kube-prometheus-stack via https://*.kubernetes.omni.siderolabs.io #40

Closed
1 task done
gerhard opened this issue Apr 29, 2023 · 4 comments
Closed
1 task done
Assignees
Labels
bug Something isn't working

Comments

@gerhard
Copy link

gerhard commented Apr 29, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Installing kube-prometheus-stack Helm chart fails with Error: create: failed to create: the server responded with the status code 413 but did not return more information (post secrets).

Here is the full error (when running with --debug):

history.go:56: [debug] getting history for release kube-prometheus-stack
Release "kube-prometheus-stack" does not exist. Installing it now.
install.go:200: [debug] Original chart version: ""
install.go:217: [debug] CHART PATH: /Users/gerhard/Library/Caches/helm/repository/kube-prometheus-stack-45.23.0.tgz

client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD alertmanagerconfigs.monitoring.coreos.com is already present. Skipping.
client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD alertmanagers.monitoring.coreos.com is already present. Skipping.
client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD podmonitors.monitoring.coreos.com is already present. Skipping.
client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD probes.monitoring.coreos.com is already present. Skipping.
client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD prometheuses.monitoring.coreos.com is already present. Skipping.
client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD prometheusrules.monitoring.coreos.com is already present. Skipping.
client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD servicemonitors.monitoring.coreos.com is already present. Skipping.
client.go:134: [debug] creating 1 resource(s)
install.go:160: [debug] CRD thanosrulers.monitoring.coreos.com is already present. Skipping.
client.go:134: [debug] creating 1 resource(s)
Error: create: failed to create: the server responded with the status code 413 but did not return more information (post secrets)
helm.go:84: [debug] the server responded with the status code 413 but did not return more information (post secrets)
create: failed to create
helm.sh/helm/v3/pkg/storage/driver.(*Secrets).Create
	helm.sh/helm/v3/pkg/storage/driver/secrets.go:164
helm.sh/helm/v3/pkg/storage.(*Storage).Create
	helm.sh/helm/v3/pkg/storage/storage.go:69
helm.sh/helm/v3/pkg/action.(*Install).RunWithContext
	helm.sh/helm/v3/pkg/action/install.go:365
main.runInstall
	helm.sh/helm/v3/cmd/helm/install.go:286
main.newUpgradeCmd.func2
	helm.sh/helm/v3/cmd/helm/upgrade.go:130
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra@v1.6.1/command.go:916
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra@v1.6.1/command.go:1044
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra@v1.6.1/command.go:968
main.main
	helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
	runtime/proc.go:250
runtime.goexit
	runtime/asm_amd64.s:1598

I suspect that this is the proxy serving https://*.kubernetes.omni.siderolabs.io which is limiting uploads. FWIW prometheus-community/helm-charts#3205

Expected Behavior

Installing kube-prometheus-stack Helm chart via https://*.kubernetes.omni.siderolabs.io should just work.

Steps To Reproduce

helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo update

helm upgrade kube-prometheus-stack prometheus-community/kube-prometheus-stack \
  --install --debug \
  --namespace kube-prometheus-stack --create-namespace

What browsers are you seeing the problem on?

No response

Anything else?

No response

@gerhard gerhard added the bug Something isn't working label Apr 29, 2023
@smira
Copy link
Member

smira commented May 1, 2023

Thanks for reporting this, the fix is coming.

@smira smira self-assigned this May 1, 2023
@smira
Copy link
Member

smira commented May 1, 2023

This problem should be resolved now.

@gerhard
Copy link
Author

gerhard commented May 2, 2023

OK! I have updated the node to Talos v1.4.1. Will report back when I have tested the new behaviour.

@gerhard
Copy link
Author

gerhard commented May 7, 2023

This now worked as expected on both clusters, one running Talos v1.4.0 & the other one running v1.4.1.

Both clusters managed by Omni v0.8.1.

Closing - thank you! 💪

@gerhard gerhard closed this as completed May 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants