Wade Xu
Wade Xu
Fixed via this ``` apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: ingress.kubernetes.io/force-ssl-redirect: "true" ingress.kubernetes.io/ssl-redirect: "true" kubernetes.io/ingress.class: nginx # If you encounter a redirect loop or are getting a 307 response code...
+1. Currently my workaround is install two Emissary in one cluster. one Emissary facing to internet. another one facing to ip_allow list. (need set another `ambassador_id` in second Emissary to...
> I'd also like to have an opportunity to block or allow IP sources at the mapping level. Or attach module to path Totally agree.
looking for this feature too...
Same issue here, I need terraform apply `-target` to apply `CRDs Resource` first, then apply the remaining resources. suggest to remove CRDs check in provider >= 2.7.0.
@bangupoc Not fix. disable it currently. `verifyDeployments: false `
Same issue with us