Steven Miller
Steven Miller
@thomasjungblut are you using this module? https://github.com/terraform-aws-modules/terraform-aws-eks the cluster aws_eks_cluster.this resource wants to be replaced?
I haven't got it working yet. Just a simply replacement of the pod (for example change from image: nginx to image: httpd) still causes some connections to drop. ``` ---...
Thanks, I think this is what I'm missing. I will give this a shot right now!
I'm giving this a go, but i'm not sure it's quite right because I think you are saying the workload should continue serving regular traffic, just not the readiness probe...
Since I will have to work out details in the workload, I will replace my demo service by my actual ingress controller and then report back.
I think the intended order of events is: - New pods launched - Update policy allows all to be launched at the same time - Readiness gate applicable to new...
Not shown: - Install Istio Operator The below manifests were working in my test to run the monitoring script and do a "kubectl rollout restart deployments -n istio-system". I think...
Update, this configuration has been working perfectly for a few weeks: ``` apiVersion: v1 kind: Namespace metadata: name: istio-config --- apiVersion: v1 kind: Namespace metadata: labels: elbv2.k8s.aws/pod-readiness-gate-inject: enabled name: istio-system...
Also relevant - a gcloud CLI feature to list all resources. https://cloud.google.com/sdk/gcloud/reference/alpha/resources/list
This is also valid for the use case if you want to do a peering but only route a subset of the subnets within each VPC