-
Notifications
You must be signed in to change notification settings - Fork 925
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
We decided to test the new option of using HTTPRoute. When exposing Jenkins using the Helm chart with Gateway API HTTPRoute (Envoy Gateway) instead of only Ingress, Jenkins shows the warning: "It appears that your reverse proxy set up is broken."
However, the installation appears to function correctly:
- UI works
- redirects work
- Jenkins URL is correctly configured
- authentication via Microsoft Entra ID works
- no incorrect redirects to internal URLs or HTTP
This suggests that the reverse proxy monitor may not correctly recognize Gateway API based setups.
Version of Helm and Kubernetes
- Helm: v3.18.6
- Kubernetes:
Client Version: v1.34.1
Server Version: v1.33.8+rke2r1Chart version
5.9.4
What happened?
1. Configure HTTPRoute:
ingress:
enabled: true
apiVersion: "networking.k8s.io/v1"
labels: {}
annotations:
ingress.kubernetes.io/ssl-redirect: "true"
cert-manager.io/cluster-issuer: letsencrypt
ingressClassName: nginx
hostName: 'our-url-redacted'
tls:
- secretName: test-env-jenkins-tls
hosts:
- 'our-url-redacted'
# Gateway API HTTPRoute
httpRoute:
enabled: true
apiVersion: "gateway.networking.k8s.io/v1"
kind: HTTPRoute
parentRefs:
- name: shared-gateway
namespace: envoy-gateway-system
sectionName: https-public
reuseIngressConfiguration: false
hostnames:
- 'our-url-redacted'
extraRules: []
# -- HTTPRoute annotations
annotations: {}
2. Update helm chart with version 5.9.4
3. Browse Manage Jenkins, warning appearsWhat you expected to happen?
No warning present.
How to reproduce it
Anything else we need to know?
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.