WAI
Status Update
Comments
gu...@gmail.com <gu...@gmail.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.
sn...@google.com <sn...@google.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.
gu...@gmail.com <gu...@gmail.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.
sn...@google.com <sn...@google.com> #6
Does anyone has been able to make it works?
Description
This script checks current Java version with a simple `java -version` command but the regex recognize only the first single digit char.
For instance, if the output of `java -version` is something similar to "1.8._" it recognizes "version `1`", not 8.
I fixed this with fastly with an "if" statement, but I'm sure there's a more elegant way to do.
This is my source: