this post was submitted on 21 Jun 2024
9 points (84.6% liked)

Selfhosted

40394 readers
212 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hello, Im setting up a k3s cluster with cilium as cni and ingress.

I wanna setup teleport-proxy on my cluster but when trying to access it i get: upstream connect error or disconnect/reset before headers. reset reason: connection termination

I have other services running on the same cluster and these do work. My cluster only exists of 1 node.

This is my values file for helm: https://pastebin.com/sfYEKuHM

And the certificates from cert-manager and related secrets and stuff are all healthy and ready.

Im unable to find any logs in the teleport & cilium pods. Does someone know how i can solve this? Thanks for your time!!!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 5 months ago

The cilium install command i used is:

cilium install –set hostFirewall.enabled=true –set devices=‘eno1’ –set enable-endpoint-routes=true –set kubeProxyReplacement=true –set l7Proxy=true –set ingressController.default=true –set ingressController.enabled=true –set ingressController.loadbalancerMode=shared –set prometheus.enabled=true –set operator.prometheus.enabled=true –set hubble.enabled=true –set hubble.metrics.enabled=“{dns,drop,tcp,flow,port-distribution,icmp,httpV2:exemplars=true;labelsContext=source_ip,source_namespace,source_workload,destination_ip,destination_namespace,destination_workload,traffic_direction}”