Fixed
Status Update
Comments
da...@google.com <da...@google.com> #2
+1 to this feature request, came here seeking help at https://serverfault.com/questions/987908/custom-routes-rejected-by-gke-peer-configuration/988167#988167
We will to build CD pipelines with agents running in internal on-premise network, peered with GCP network. GKE private endpoint is not reachable in this case.
We will to build CD pipelines with agents running in internal on-premise network, peered with GCP network. GKE private endpoint is not reachable in this case.
ae...@gmail.com <ae...@gmail.com> #3
+1 Could be quite a useful feature for us.
Ideally, we don't want to have public IP for K8S API at all and manage it privately inside the org with a hybrid architecture site-2-site VPN etc.
Ideally, we don't want to have public IP for K8S API at all and manage it privately inside the org with a hybrid architecture site-2-site VPN etc.
da...@google.com <da...@google.com>
da...@google.com <da...@google.com>
ap...@google.com <ap...@google.com> #4
I thought this would be resolved now that the VPC Peerings of private GKE will accept routes exported from the VPC. But it still doesn't seem to work for me.
Description
In this block :
After wrapped in here , data flow couldn't receive any change, neither any invalidation observer.
immediateTransaction
, which mentionedIn pure Room without KMP, multiple DAO operations normally wrapped in
database.withTransaction
block. How to do in KMP?