Mariana Ramos Franco

Any update on this? I'm trying to migrate from Ambassador 1.14 to Emissary-ingress 2.3.2 and having the same error when setting `spec.include_body.allow_partial` to false. I noticed that `allow_partial` attribute is...

I'm seeing the same problem with Emissary 2.3.2. This is happening for me when creating Host and TLSContext with the `ambassador_id`. Looks like this `--apiVersion-v3alpha1-only--` prefix was introduced on https://github.com/emissary-ingress/emissary/commit/d86cbba211c7e9dd91d857f47f3971d162b721e9....

Ok, I was finally able to make things work using `ambassador_id` with `v3alpha1` resources. I ended up creating new resources instead of updating existing ones to include a new `ambassador_id`.

+1 Could we have an option to pass our own certificate to `apiext`? I'm also concerned about the CA expiration: https://github.com/emissary-ingress/emissary/issues/4442

EKS recommends the usage of [node-problem-detector](https://github.com/kubernetes/node-problem-detector) with some remedy system to drain and terminate the bad node: https://aws.github.io/aws-eks-best-practices/reliability/docs/dataplane/#run-node-problem-detector Would be great if the `node-problem-detector` could be provided out of box.....

I noticed that no error is returned on v3.4.1 and v3.7.2 when setting `include_body.allow_partial: false`. However, the false value is not getting passed to envoy. Example: my auth.yaml config: ```...

Thanks @cindymullins-dw for the update. We have more than 100s clusters so we want to avoid to have to manually delete secrets on those. Do you have an estimate for...

@cindymullins-dw Any update on the software patch?