Status Update
No update yet.
Comments
dh...@google.com
dh...@google.com
Hello,
Thanks for reaching out to us!
The Product Engineering Team has been made aware of your feature request, and will address it in due course. Though we can't provide an ETA on feature requests nor guarantee their implementation, rest assured that your feedback is always taken very seriously, as it allows us to improve our products. Thank you for your trust and continued support to improve Google Cloud Platform products.
In case you want to report a new issue, please do not hesitate to create a new
Thanks & Regards,
Manish Bavireddy.
Google Cloud Support
df...@ncr.com
We are stuck with the same problem.
We have an open case with Google Support about this and, among others, they have redirected us here.
We have tried the following workaround:
START THE WORKARROUND
As per temporary fix the recommended way to match on port would be at the Gateway level.In the following example, the Route will only match incoming traffic on port 80 because it's attaching to the "http" Gateway listener.
apiVersion:
kind: Gateway
metadata:
name: my-gateway
spec:
gatewayClassName: gke-l7-global-external-managed
listeners:
- name: http
protocol: HTTP
port: 80
- name: https
protocol: HTTPS
port: 443
---
apiVersion:
kind: HTTPRoute
metadata:
name: http-store-80
spec:
parentRefs:
- name: my-gateway
sectionName: http
hostnames:
- "
rules:
backendRefs:
- name: my-service
port: 8080
END THE WORKARROUND
But the workarround has not worked, the problem persists.
We post this comment to see what the status of the Issue is and to see if there are other workarrounds available.
Thanks & Regards,
Joan Cholvi.
Mercadona
ba...@google.com
Hi,
Thanks for your response.
The information has been shared with the Product Team and further updates will be provided in this thread.
According to the
Please note that the Issue Tracker is primarily meant for reporting bugs and requesting new features. If you have any additional issues or concerns, please don’t hesitate to create a new thread on the
Thanks
vb...@ncr.com
ma...@google.com Restricted+
de...@ncr.com
Experiencing the same issue after upgrading gateway class from gke-l7-gxlb to gke-l7-global-external-managed.
ka...@google.com
ka...@google.com
ka...@google.com
Hello,
According to the
Further updates regarding this issue will be communicated here in this thread.
Please note that the Issue Tracker is primarily meant for reporting bugs and requesting new features. For individual support issues, it is best to utilize the support ticketing system. If you have any additional issues or concerns, please don’t hesitate to create a new thread on the
vb...@ncr.com
As stated by you, our "feedback is always taken very seriously.", but I have not seen any update on this for months.
We are using ASM and GCM, but we do not a path forward to integrate them both.
Please provide an update as soon as possible.
Description
This is a major piece of our infrastructure, and we would hope that since ASM and GCM are both Google's products, Google would provide a solid integration process for using our certificates in GCM for SIMPLE TLS connections into the istio gateway.
This is very important to customers.