-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat: add support for ingress backed GlooEdge Gateway #5909
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
base: master
Are you sure you want to change the base?
feat: add support for ingress backed GlooEdge Gateway #5909
Conversation
|
Welcome @cucxabong! |
|
Hi @cucxabong. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
da56738 to
c996a08
Compare
|
lgtm |
c996a08 to
a8c674c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was it tested on real cluster? What was your kubernetes manifests and results?
|
/ok-to-test |
Pull Request Test Coverage Report for Build 18816420063Details
💛 - Coveralls |
a8c674c to
f9dec1c
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@ivankatliarchuk yes, I did a test on our sandbox env in |
f9dec1c to
3b2a8e7
Compare
3b2a8e7 to
1ffb257
Compare
1ffb257 to
02121fe
Compare
a6995f0 to
3045a8d
Compare
|
all tests are green, please help to review again. Thank you @ivankatliarchuk |
3045a8d to
3b4f28d
Compare
|
@cucxabong For the chart update, the Changelog has to be updated in the unreleased section |
3b4f28d to
2c49455
Compare
|
Could you share similar results for this PR #5085 (comment). Need to make sure it works before we merge, I'll try to smoke test right after as well. |
|
Please find more details below. I tried to run with
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
alb.ingress.kubernetes.io/healthcheck-path: /
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS": 443}]'
alb.ingress.kubernetes.io/scheme: internet-facing
alb.ingress.kubernetes.io/ssl-redirect: "443"
alb.ingress.kubernetes.io/success-codes: 200-499
alb.ingress.kubernetes.io/target-type: ip
meta.helm.sh/release-name: gloo-proxy
meta.helm.sh/release-namespace: gloo-system
finalizers:
- ingress.k8s.aws/resources
generation: 1
labels:
app: gloo
app.kubernetes.io/managed-by: Helm
gateway-proxy-id: external-dns-demo-proxy
gloo: gateway-proxy
name: external-dns-demo-proxy
namespace: gloo-system
spec:
ingressClassName: alb
....
status:
loadBalancer:
ingress:
- hostname: k8s-gloosyst-1ee31790ed-444154078.us-east-1.elb.amazonaws.com
---
apiVersion: gateway.solo.io/v1
kind: Gateway
metadata:
labels:
app: gloo
name: external-dns-demo-proxy
namespace: gloo-system
spec:
bindAddress: '::'
bindPort: 8080
httpGateway:
virtualServiceNamespaces:
- gloo-system
proxyNames:
- external-dns-demo-proxy
ssl: false
useProxyProto: false
---
apiVersion: gloo.solo.io/v1
kind: Proxy
metadata:
labels:
created_by: gloo-gateway
name: external-dns-demo-proxy
namespace: gloo-system
spec:
listeners:
- bindAddress: '::'
bindPort: 8080
httpListener:
virtualHosts:
- domains:
- example-api.external-dns-example.com
- example-api.excluded-dns-zone.com
metadataStatic:
sources:
- observedGeneration: "33"
resourceKind: '*v1.VirtualService'
resourceRef:
name: example-api
namespace: gloo-system
name: gloo-system.example-api
routes:
- matchers:
- prefix: /
metadataStatic:
sources:
- observedGeneration: "33"
resourceKind: '*v1.VirtualService'
resourceRef:
name: example-api
namespace: gloo-system
options:
extauth:
customAuth: {}
routeAction:
single:
upstream:
name: example-api
namespace: gloo-system
metadataStatic:
sources:
- observedGeneration: "103"
resourceKind: '*v1.Gateway'
resourceRef:
name: external-dns-demo-proxy
namespace: gloo-system
name: listener-::-8080
---
apiVersion: v1
kind: Service
metadata:
annotations:
meta.helm.sh/release-name: gloo-proxy
meta.helm.sh/release-namespace: gloo-system
labels:
app: gloo
app.kubernetes.io/managed-by: Helm
gateway-proxy-id: external-dns-demo-proxy
gloo: gateway-proxy
name: external-dns-demo-proxy
namespace: gloo-system
spec:
clusterIP: 172.20.190.44
clusterIPs:
- 172.20.190.44
internalTrafficPolicy: Cluster
ipFamilies:
- IPv4
ipFamilyPolicy: SingleStack
ports:
- name: http
port: 8080
protocol: TCP
targetPort: 8080
selector:
gateway-proxy: live
gateway-proxy-id: external-dns-demo-proxy
sessionAffinity: None
type: ClusterIP
status:
loadBalancer: {}
apiVersion: gateway.solo.io/v1
kind: Gateway
metadata:
annotations:
external-dns.alpha.kubernetes.io/ingress: external-dns-demo-proxy
....
|
docs/sources/gloo-proxy.md
Outdated
| ## Gateway Annotation | ||
| To support setups where an Ingress resource is used provision an external LB you can add the following annotation to your Gateway |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| To support setups where an Ingress resource is used provision an external LB you can add the following annotation to your Gateway | |
| To support setups where an Ingress resource is used to provision an external LB you can add the following annotation to your Gateway |
| github.com/prometheus/common v0.65.0 | ||
| github.com/scaleway/scaleway-sdk-go v1.0.0-beta.34 | ||
| github.com/sirupsen/logrus v1.9.3 | ||
| github.com/spf13/cobra v1.9.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤔 Why there are those changes on go.mod ? I see nothing related with changes in go source code.
Would you please explain or remove this change ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's the output after I run go mod tidy (in go version go1.25.3 darwin/arm64)? Should we keep that output?
2c49455 to
c71158d
Compare
What does it do ?
fix #5908
More