Status Update
No update yet.
Comments
ba...@google.com
ka...@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
dp...@gmail.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
ma...@google.com
dp...@gmail.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
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
While configuring the service in GKE, port additions or removals to Service type=LoadBalancer on GKE result in downtime of around 30 seconds approx.
What you expected to happen:
There should not be any downtime.
Steps to reproduce:
date; go run
-disable-keepalive \
-c 10 `# number of workers` \
-q 2 `# qps per worker` \
-z 1m `# duration ` \
"http://${LB_IP}"
Thu Apr 25 03:57:00 PM CEST 2024
Summary:
Total: 77.4545 secs
Slowest: 11.5095 secs
Fastest: 0.2409 secs
Average: 0.4358 secs
Requests/sec: 4.8157
Total data: 214812 bytes
Size/request: 612 bytes
Response time histogram:
0.241 [1] |
1.368 [342] |■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
2.495 [0] |
3.621 [0] |
4.748 [2] |
5.875 [0] |
7.002 [0] |
8.129 [2] |
9.256 [0] |
10.383 [0] |
11.510 [4] |
Latency distribution:
10% in 0.2418 secs
25% in 0.2424 secs
50% in 0.2432 secs
75% in 0.2443 secs
90% in 0.2457 secs
95% in 0.2495 secs
99% in 11.5056 secs
Details (average, fastest, slowest):
DNS+dialup: 0.3132 secs, 0.2409 secs, 11.5095 secs
DNS-lookup: 0.0000 secs, 0.0000 secs, 0.0000 secs
req write: 0.0000 secs, 0.0000 secs, 0.0002 secs
resp wait: 0.1222 secs, 0.1200 secs, 0.1303 secs
resp read: 0.0003 secs, 0.0000 secs, 0.0070 secs
Status code distribution:
[200] 351 responses
Error distribution:
[2] Get "
[20] Get "
Other information (workarounds you have tried, documentation consulted, etc):
N/A