conduit wellknown service not reachable #184

Closed
opened 2024-10-05 15:15:55 +00:00 by tectux · 6 comments
tectux commented 2024-10-05 15:15:55 +00:00 (Migrated from codeberg.org)

Hello, I have ingress off and wellknown enabled. I can't curl conduit-release-wellknown:8080 within the namespace, altough the liveness probe is ok, pod is running, etc.
Creating my own nginx deployment to fill in for it works. Might create a PR for the alternative config later, but I'm not sure why the default one isn't working...

wellknown:
  enabled: true
  image:
    registry: docker.io
    repository: library/nginx
    pullPolicy: IfNotPresent
    tag: "1.27.1"
  
  replicaCount: 1
  podLabels: {}
  podAnnotations: []
  podSecurityContext: {}
  securityContext: {}
  containerPort: 80
  env: [] 
  resources: {}
  nodeSelector: {}
  tolerations: []
  affinity: {}
 
  service:
    type: ClusterIP
    port: 8080 # according to default values
    annotations: {}
 
  # TO EDIT:

Hello, I have ingress off and wellknown enabled. I can't curl `conduit-release-wellknown:8080` within the namespace, altough the liveness probe is ok, pod is running, etc. Creating my own nginx deployment to fill in for it works. Might create a PR for the alternative config later, but I'm not sure why the default one isn't working... ``` wellknown: enabled: true image: registry: docker.io repository: library/nginx pullPolicy: IfNotPresent tag: "1.27.1" replicaCount: 1 podLabels: {} podAnnotations: [] podSecurityContext: {} securityContext: {} containerPort: 80 env: [] resources: {} nodeSelector: {} tolerations: [] affinity: {} service: type: ClusterIP port: 8080 # according to default values annotations: {} # TO EDIT: ```
wrenix commented 2024-10-05 16:43:46 +00:00 (Migrated from codeberg.org)

First, why you disable the ingress?

First, why you disable the ingress?
tectux commented 2024-10-05 17:30:53 +00:00 (Migrated from codeberg.org)

why: custom traefik setup (routing)
It shouldn't affect the availability of the svc within the namspace.
curl conduit-release:6167 works just fine as it should btw

why: custom traefik setup (routing) It shouldn't affect the availability of the svc within the namspace. `curl conduit-release:6167` works just fine as it should btw
tectux commented 2024-10-05 18:44:26 +00:00 (Migrated from codeberg.org)

Finally found the issue, it was a lot easier than I thought: the pod doesn't have the label specified in the service (type: wellknown).
This fixes that: 4d2589e86b.
I don't think ingress would make any difference.

Finally found the issue, it was a lot easier than I thought: the pod doesn't have the label specified in the service (`type: wellknown`). This fixes that: https://codeberg.org/tectux/helm-charts/commit/4d2589e86b03dd0907a57c64899da9cabcf3ca0e. I don't think ingress would make any difference.
wrenix commented 2024-10-05 19:37:55 +00:00 (Migrated from codeberg.org)

Oh okay, i Oversee that - thanks i will merge it tomorroe

Oh okay, i Oversee that - thanks i will merge it tomorroe
wrenix commented 2024-10-05 19:38:57 +00:00 (Migrated from codeberg.org)

No, i was just irritated, why you do not use it.
Sorry

No, i was just irritated, why you do not use it. Sorry
tectux commented 2024-10-05 19:56:09 +00:00 (Migrated from codeberg.org)

I see, thanks!
No worries. Im just using traefik kubernetes crd

I see, thanks! No worries. Im just using [traefik kubernetes crd](https://doc.traefik.io/traefik/routing/providers/kubernetes-crd/)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: wrenix/helm-charts#184
No description provided.