Istio EnvoyFilter enable auto_sni

1

Hello community,
I have to enable the the auto_sni Envoy property to automatically send the sni based on the Host Header.
The current configuration looks like this:

apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: enable-auto-sni
  namespace: istio-system
spec:
  configPatches:
  - applyTo: CLUSTER
    match:
      cluster:
        name: "*.foobar.com"
    patch:
      operation: MERGE
      value:
        typed_extension_protocol_options:
          envoy.extensions.upstreams.http.v3.HttpProtocolOptions:
            "@type": type.googleapis.com/envoy.extensions.upstreams.http.v3.HttpProtocolOptions
            upstream_http_protocol_options:
              auto_sni: true

When applying the resource the sidecar proxies have the following error log:

2021-06-28T07:31:45.124694Z	warning	envoy config	gRPC config for type.googleapis.com/envoy.config.cluster.v3.Cluster rejected: Proto constraint validation failed (ClusterValidationError.Name: value length must be at least 1 characters): typed_extension_protocol_options {
  key: "envoy.extensions.upstreams.http.v3.HttpProtocolOptions"
  value {
    [type.googleapis.com/envoy.extensions.upstreams.http.v3.HttpProtocolOptions] {
      upstream_http_protocol_options {
        auto_sni: true
      }
    }
  }
}

Can someone help me with correctly configuring this EnvoyFilter? Highly appreciating any comments or tips. :slight_smile:

2

same problem ,anyone can help me?

3 
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: enable-auto-sni-san-validation
  namespace: istio-system
spec:
  configPatches:
  - applyTo: CLUSTER
    match:
      cluster:
        name: "*.google.com"
    patch:
      operation: MERGE
      value:
        upstream_http_protocol_options:
          auto_sni: true
4

While the above EnvoyFilter works, you might be also interested in the latest istio which supports auto_sni configuration without the need for an explicit EnvoyFilter.