程序包 istio.networking.v1alpha3

类 VirtualServiceOuterClass.VirtualService.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<VirtualServiceOuterClass.VirtualService.Builder>
com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>
istio.networking.v1alpha3.VirtualServiceOuterClass.VirtualService.Builder
所有已实现的接口:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, VirtualServiceOuterClass.VirtualServiceOrBuilder, Cloneable
封闭类:
VirtualServiceOuterClass.VirtualService
public static final class VirtualServiceOuterClass.VirtualService.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder> implements VirtualServiceOuterClass.VirtualServiceOrBuilder
 Configuration affecting traffic routing.

 <!-- crd generation tags
 +cue-gen:VirtualService:groupName:networking.istio.io
 +cue-gen:VirtualService:version:v1alpha3
 +cue-gen:VirtualService:storageVersion
 +cue-gen:VirtualService:annotations:helm.sh/resource-policy=keep
 +cue-gen:VirtualService:labels:app=istio-pilot,chart=istio,heritage=Tiller,release=istio
 +cue-gen:VirtualService:subresource:status
 +cue-gen:VirtualService:scope:Namespaced
 +cue-gen:VirtualService:resource:categories=istio-io,networking-istio-io,shortNames=vs
 +cue-gen:VirtualService:printerColumn:name=Gateways,type=string,JSONPath=.spec.gateways,description="The names of gateways and sidecars 
 that should apply these routes"
 +cue-gen:VirtualService:printerColumn:name=Hosts,type=string,JSONPath=.spec.hosts,description="The destination hosts to which traffic is being sent"
 +cue-gen:VirtualService:printerColumn:name=Age,type=date,JSONPath=.metadata.creationTimestamp,description="CreationTimestamp is a timestamp 
 representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. 
 Clients may not set this value. It is represented in RFC3339 form and is in UTC.
 Populated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata"
 +cue-gen:VirtualService:preserveUnknownFields:false
 -->

 <!-- go code generation tags
 +kubetype-gen
 +kubetype-gen:groupVersion=networking.istio.io/v1alpha3
 +genclient
 +k8s:deepcopy-gen=true
 -->
Protobuf type istio.networking.v1alpha3.VirtualService

  • 方法详细资料

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
      指定者:
      internalGetFieldAccessorTable 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • clear

      public VirtualServiceOuterClass.VirtualService.Builder clear()
      指定者:
      clear 在接口中 com.google.protobuf.Message.Builder
      指定者:
      clear 在接口中 com.google.protobuf.MessageLite.Builder
      覆盖:
      clear 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      指定者:
      getDescriptorForType 在接口中 com.google.protobuf.Message.Builder
      指定者:
      getDescriptorForType 在接口中 com.google.protobuf.MessageOrBuilder
      覆盖:
      getDescriptorForType 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • getDefaultInstanceForType

      public VirtualServiceOuterClass.VirtualService getDefaultInstanceForType()
      指定者:
      getDefaultInstanceForType 在接口中 com.google.protobuf.MessageLiteOrBuilder
      指定者:
      getDefaultInstanceForType 在接口中 com.google.protobuf.MessageOrBuilder

    • build

      public VirtualServiceOuterClass.VirtualService build()
      指定者:
      build 在接口中 com.google.protobuf.Message.Builder
      指定者:
      build 在接口中 com.google.protobuf.MessageLite.Builder

    • buildPartial

      public VirtualServiceOuterClass.VirtualService buildPartial()
      指定者:
      buildPartial 在接口中 com.google.protobuf.Message.Builder
      指定者:
      buildPartial 在接口中 com.google.protobuf.MessageLite.Builder

    • clone

      public VirtualServiceOuterClass.VirtualService.Builder clone()
      指定者:
      clone 在接口中 com.google.protobuf.Message.Builder
      指定者:
      clone 在接口中 com.google.protobuf.MessageLite.Builder
      覆盖:
      clone 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • setField

      public VirtualServiceOuterClass.VirtualService.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      指定者:
      setField 在接口中 com.google.protobuf.Message.Builder
      覆盖:
      setField 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • clearField

      public VirtualServiceOuterClass.VirtualService.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
      指定者:
      clearField 在接口中 com.google.protobuf.Message.Builder
      覆盖:
      clearField 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • clearOneof

      public VirtualServiceOuterClass.VirtualService.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
      指定者:
      clearOneof 在接口中 com.google.protobuf.Message.Builder
      覆盖:
      clearOneof 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • setRepeatedField

      public VirtualServiceOuterClass.VirtualService.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
      指定者:
      setRepeatedField 在接口中 com.google.protobuf.Message.Builder
      覆盖:
      setRepeatedField 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • addRepeatedField

      public VirtualServiceOuterClass.VirtualService.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      指定者:
      addRepeatedField 在接口中 com.google.protobuf.Message.Builder
      覆盖:
      addRepeatedField 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • mergeFrom

      public VirtualServiceOuterClass.VirtualService.Builder mergeFrom(com.google.protobuf.Message other)
      指定者:
      mergeFrom 在接口中 com.google.protobuf.Message.Builder
      覆盖:
      mergeFrom 在类中 com.google.protobuf.AbstractMessage.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • mergeFrom

      public VirtualServiceOuterClass.VirtualService.Builder mergeFrom(VirtualServiceOuterClass.VirtualService other)

    • isInitialized

      public final boolean isInitialized()
      指定者:
      isInitialized 在接口中 com.google.protobuf.MessageLiteOrBuilder
      覆盖:
      isInitialized 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • mergeFrom

      public VirtualServiceOuterClass.VirtualService.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      指定者:
      mergeFrom 在接口中 com.google.protobuf.Message.Builder
      指定者:
      mergeFrom 在接口中 com.google.protobuf.MessageLite.Builder
      覆盖:
      mergeFrom 在类中 com.google.protobuf.AbstractMessage.Builder<VirtualServiceOuterClass.VirtualService.Builder>
      抛出:
      IOException

    • getHostsList

      public com.google.protobuf.ProtocolStringList getHostsList()
       The destination hosts to which traffic is being sent. Could
 be a DNS name with wildcard prefix or an IP address.  Depending on the
 platform, short-names can also be used instead of a FQDN (i.e. has no
 dots in the name). In such a scenario, the FQDN of the host would be
 derived based on the underlying platform.

 A single VirtualService can be used to describe all the traffic
 properties of the corresponding hosts, including those for multiple
 HTTP and TCP ports. Alternatively, the traffic properties of a host
 can be defined using more than one VirtualService, with certain
 caveats. Refer to the
 [Operations Guide](https://istio.io/docs/ops/best-practices/traffic-management/#split-virtual-services)
 for details.

 *Note for Kubernetes users*: When short names are used (e.g. "reviews"
 instead of "reviews.default.svc.cluster.local"), Istio will interpret
 the short name based on the namespace of the rule, not the service. A
 rule in the "default" namespace containing a host "reviews" will be
 interpreted as "reviews.default.svc.cluster.local", irrespective of
 the actual namespace associated with the reviews service. _To avoid
 potential misconfigurations, it is recommended to always use fully
 qualified domain names over short names._

 The hosts field applies to both HTTP and TCP services. Service inside
 the mesh, i.e., those found in the service registry, must always be
 referred to using their alphanumeric names. IP addresses are allowed
 only for services defined via the Gateway.

 *Note*: It must be empty for a delegate VirtualService.
      repeated string hosts = 1;
      指定者:
      getHostsList 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      返回:
      A list containing the hosts.

    • getHostsCount

      public int getHostsCount()
       The destination hosts to which traffic is being sent. Could
 be a DNS name with wildcard prefix or an IP address.  Depending on the
 platform, short-names can also be used instead of a FQDN (i.e. has no
 dots in the name). In such a scenario, the FQDN of the host would be
 derived based on the underlying platform.

 A single VirtualService can be used to describe all the traffic
 properties of the corresponding hosts, including those for multiple
 HTTP and TCP ports. Alternatively, the traffic properties of a host
 can be defined using more than one VirtualService, with certain
 caveats. Refer to the
 [Operations Guide](https://istio.io/docs/ops/best-practices/traffic-management/#split-virtual-services)
 for details.

 *Note for Kubernetes users*: When short names are used (e.g. "reviews"
 instead of "reviews.default.svc.cluster.local"), Istio will interpret
 the short name based on the namespace of the rule, not the service. A
 rule in the "default" namespace containing a host "reviews" will be
 interpreted as "reviews.default.svc.cluster.local", irrespective of
 the actual namespace associated with the reviews service. _To avoid
 potential misconfigurations, it is recommended to always use fully
 qualified domain names over short names._

 The hosts field applies to both HTTP and TCP services. Service inside
 the mesh, i.e., those found in the service registry, must always be
 referred to using their alphanumeric names. IP addresses are allowed
 only for services defined via the Gateway.

 *Note*: It must be empty for a delegate VirtualService.
      repeated string hosts = 1;
      指定者:
      getHostsCount 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      返回:
      The count of hosts.

    • getHosts

      public String getHosts(int index)
       The destination hosts to which traffic is being sent. Could
 be a DNS name with wildcard prefix or an IP address.  Depending on the
 platform, short-names can also be used instead of a FQDN (i.e. has no
 dots in the name). In such a scenario, the FQDN of the host would be
 derived based on the underlying platform.

 A single VirtualService can be used to describe all the traffic
 properties of the corresponding hosts, including those for multiple
 HTTP and TCP ports. Alternatively, the traffic properties of a host
 can be defined using more than one VirtualService, with certain
 caveats. Refer to the
 [Operations Guide](https://istio.io/docs/ops/best-practices/traffic-management/#split-virtual-services)
 for details.

 *Note for Kubernetes users*: When short names are used (e.g. "reviews"
 instead of "reviews.default.svc.cluster.local"), Istio will interpret
 the short name based on the namespace of the rule, not the service. A
 rule in the "default" namespace containing a host "reviews" will be
 interpreted as "reviews.default.svc.cluster.local", irrespective of
 the actual namespace associated with the reviews service. _To avoid
 potential misconfigurations, it is recommended to always use fully
 qualified domain names over short names._

 The hosts field applies to both HTTP and TCP services. Service inside
 the mesh, i.e., those found in the service registry, must always be
 referred to using their alphanumeric names. IP addresses are allowed
 only for services defined via the Gateway.

 *Note*: It must be empty for a delegate VirtualService.
      repeated string hosts = 1;
      指定者:
      getHosts 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      参数:
      index - The index of the element to return.
      返回:
      The hosts at the given index.

    • getHostsBytes

      public com.google.protobuf.ByteString getHostsBytes(int index)
       The destination hosts to which traffic is being sent. Could
 be a DNS name with wildcard prefix or an IP address.  Depending on the
 platform, short-names can also be used instead of a FQDN (i.e. has no
 dots in the name). In such a scenario, the FQDN of the host would be
 derived based on the underlying platform.

 A single VirtualService can be used to describe all the traffic
 properties of the corresponding hosts, including those for multiple
 HTTP and TCP ports. Alternatively, the traffic properties of a host
 can be defined using more than one VirtualService, with certain
 caveats. Refer to the
 [Operations Guide](https://istio.io/docs/ops/best-practices/traffic-management/#split-virtual-services)
 for details.

 *Note for Kubernetes users*: When short names are used (e.g. "reviews"
 instead of "reviews.default.svc.cluster.local"), Istio will interpret
 the short name based on the namespace of the rule, not the service. A
 rule in the "default" namespace containing a host "reviews" will be
 interpreted as "reviews.default.svc.cluster.local", irrespective of
 the actual namespace associated with the reviews service. _To avoid
 potential misconfigurations, it is recommended to always use fully
 qualified domain names over short names._

 The hosts field applies to both HTTP and TCP services. Service inside
 the mesh, i.e., those found in the service registry, must always be
 referred to using their alphanumeric names. IP addresses are allowed
 only for services defined via the Gateway.

 *Note*: It must be empty for a delegate VirtualService.
      repeated string hosts = 1;
      指定者:
      getHostsBytes 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      参数:
      index - The index of the value to return.
      返回:
      The bytes of the hosts at the given index.

    • setHosts

      public VirtualServiceOuterClass.VirtualService.Builder setHosts(int index, String value)
       The destination hosts to which traffic is being sent. Could
 be a DNS name with wildcard prefix or an IP address.  Depending on the
 platform, short-names can also be used instead of a FQDN (i.e. has no
 dots in the name). In such a scenario, the FQDN of the host would be
 derived based on the underlying platform.

 A single VirtualService can be used to describe all the traffic
 properties of the corresponding hosts, including those for multiple
 HTTP and TCP ports. Alternatively, the traffic properties of a host
 can be defined using more than one VirtualService, with certain
 caveats. Refer to the
 [Operations Guide](https://istio.io/docs/ops/best-practices/traffic-management/#split-virtual-services)
 for details.

 *Note for Kubernetes users*: When short names are used (e.g. "reviews"
 instead of "reviews.default.svc.cluster.local"), Istio will interpret
 the short name based on the namespace of the rule, not the service. A
 rule in the "default" namespace containing a host "reviews" will be
 interpreted as "reviews.default.svc.cluster.local", irrespective of
 the actual namespace associated with the reviews service. _To avoid
 potential misconfigurations, it is recommended to always use fully
 qualified domain names over short names._

 The hosts field applies to both HTTP and TCP services. Service inside
 the mesh, i.e., those found in the service registry, must always be
 referred to using their alphanumeric names. IP addresses are allowed
 only for services defined via the Gateway.

 *Note*: It must be empty for a delegate VirtualService.
      repeated string hosts = 1;
      参数:
      index - The index to set the value at.
      value - The hosts to set.
      返回:
      This builder for chaining.

    • addHosts

      public VirtualServiceOuterClass.VirtualService.Builder addHosts(String value)
       The destination hosts to which traffic is being sent. Could
 be a DNS name with wildcard prefix or an IP address.  Depending on the
 platform, short-names can also be used instead of a FQDN (i.e. has no
 dots in the name). In such a scenario, the FQDN of the host would be
 derived based on the underlying platform.

 A single VirtualService can be used to describe all the traffic
 properties of the corresponding hosts, including those for multiple
 HTTP and TCP ports. Alternatively, the traffic properties of a host
 can be defined using more than one VirtualService, with certain
 caveats. Refer to the
 [Operations Guide](https://istio.io/docs/ops/best-practices/traffic-management/#split-virtual-services)
 for details.

 *Note for Kubernetes users*: When short names are used (e.g. "reviews"
 instead of "reviews.default.svc.cluster.local"), Istio will interpret
 the short name based on the namespace of the rule, not the service. A
 rule in the "default" namespace containing a host "reviews" will be
 interpreted as "reviews.default.svc.cluster.local", irrespective of
 the actual namespace associated with the reviews service. _To avoid
 potential misconfigurations, it is recommended to always use fully
 qualified domain names over short names._

 The hosts field applies to both HTTP and TCP services. Service inside
 the mesh, i.e., those found in the service registry, must always be
 referred to using their alphanumeric names. IP addresses are allowed
 only for services defined via the Gateway.

 *Note*: It must be empty for a delegate VirtualService.
      repeated string hosts = 1;
      参数:
      value - The hosts to add.
      返回:
      This builder for chaining.

    • addAllHosts

      public VirtualServiceOuterClass.VirtualService.Builder addAllHosts(Iterable<String> values)
       The destination hosts to which traffic is being sent. Could
 be a DNS name with wildcard prefix or an IP address.  Depending on the
 platform, short-names can also be used instead of a FQDN (i.e. has no
 dots in the name). In such a scenario, the FQDN of the host would be
 derived based on the underlying platform.

 A single VirtualService can be used to describe all the traffic
 properties of the corresponding hosts, including those for multiple
 HTTP and TCP ports. Alternatively, the traffic properties of a host
 can be defined using more than one VirtualService, with certain
 caveats. Refer to the
 [Operations Guide](https://istio.io/docs/ops/best-practices/traffic-management/#split-virtual-services)
 for details.

 *Note for Kubernetes users*: When short names are used (e.g. "reviews"
 instead of "reviews.default.svc.cluster.local"), Istio will interpret
 the short name based on the namespace of the rule, not the service. A
 rule in the "default" namespace containing a host "reviews" will be
 interpreted as "reviews.default.svc.cluster.local", irrespective of
 the actual namespace associated with the reviews service. _To avoid
 potential misconfigurations, it is recommended to always use fully
 qualified domain names over short names._

 The hosts field applies to both HTTP and TCP services. Service inside
 the mesh, i.e., those found in the service registry, must always be
 referred to using their alphanumeric names. IP addresses are allowed
 only for services defined via the Gateway.

 *Note*: It must be empty for a delegate VirtualService.
      repeated string hosts = 1;
      参数:
      values - The hosts to add.
      返回:
      This builder for chaining.

    • clearHosts

      public VirtualServiceOuterClass.VirtualService.Builder clearHosts()
       The destination hosts to which traffic is being sent. Could
 be a DNS name with wildcard prefix or an IP address.  Depending on the
 platform, short-names can also be used instead of a FQDN (i.e. has no
 dots in the name). In such a scenario, the FQDN of the host would be
 derived based on the underlying platform.

 A single VirtualService can be used to describe all the traffic
 properties of the corresponding hosts, including those for multiple
 HTTP and TCP ports. Alternatively, the traffic properties of a host
 can be defined using more than one VirtualService, with certain
 caveats. Refer to the
 [Operations Guide](https://istio.io/docs/ops/best-practices/traffic-management/#split-virtual-services)
 for details.

 *Note for Kubernetes users*: When short names are used (e.g. "reviews"
 instead of "reviews.default.svc.cluster.local"), Istio will interpret
 the short name based on the namespace of the rule, not the service. A
 rule in the "default" namespace containing a host "reviews" will be
 interpreted as "reviews.default.svc.cluster.local", irrespective of
 the actual namespace associated with the reviews service. _To avoid
 potential misconfigurations, it is recommended to always use fully
 qualified domain names over short names._

 The hosts field applies to both HTTP and TCP services. Service inside
 the mesh, i.e., those found in the service registry, must always be
 referred to using their alphanumeric names. IP addresses are allowed
 only for services defined via the Gateway.

 *Note*: It must be empty for a delegate VirtualService.
      repeated string hosts = 1;
      返回:
      This builder for chaining.

    • addHostsBytes

      public VirtualServiceOuterClass.VirtualService.Builder addHostsBytes(com.google.protobuf.ByteString value)
       The destination hosts to which traffic is being sent. Could
 be a DNS name with wildcard prefix or an IP address.  Depending on the
 platform, short-names can also be used instead of a FQDN (i.e. has no
 dots in the name). In such a scenario, the FQDN of the host would be
 derived based on the underlying platform.

 A single VirtualService can be used to describe all the traffic
 properties of the corresponding hosts, including those for multiple
 HTTP and TCP ports. Alternatively, the traffic properties of a host
 can be defined using more than one VirtualService, with certain
 caveats. Refer to the
 [Operations Guide](https://istio.io/docs/ops/best-practices/traffic-management/#split-virtual-services)
 for details.

 *Note for Kubernetes users*: When short names are used (e.g. "reviews"
 instead of "reviews.default.svc.cluster.local"), Istio will interpret
 the short name based on the namespace of the rule, not the service. A
 rule in the "default" namespace containing a host "reviews" will be
 interpreted as "reviews.default.svc.cluster.local", irrespective of
 the actual namespace associated with the reviews service. _To avoid
 potential misconfigurations, it is recommended to always use fully
 qualified domain names over short names._

 The hosts field applies to both HTTP and TCP services. Service inside
 the mesh, i.e., those found in the service registry, must always be
 referred to using their alphanumeric names. IP addresses are allowed
 only for services defined via the Gateway.

 *Note*: It must be empty for a delegate VirtualService.
      repeated string hosts = 1;
      参数:
      value - The bytes of the hosts to add.
      返回:
      This builder for chaining.

    • getGatewaysList

      public com.google.protobuf.ProtocolStringList getGatewaysList()
       The names of gateways and sidecars that should apply these routes.
 Gateways in other namespaces may be referred to by
 `<gateway namespace>/<gateway name>`; specifying a gateway with no
 namespace qualifier is the same as specifying the VirtualService's
 namespace. A single VirtualService is used for sidecars inside the mesh as
 well as for one or more gateways. The selection condition imposed by this
 field can be overridden using the source field in the match conditions
 of protocol-specific routes. The reserved word `mesh` is used to imply
 all the sidecars in the mesh. When this field is omitted, the default
 gateway (`mesh`) will be used, which would apply the rule to all
 sidecars in the mesh. If a list of gateway names is provided, the
 rules will apply only to the gateways. To apply the rules to both
 gateways and sidecars, specify `mesh` as one of the gateway names.
      repeated string gateways = 2;
      指定者:
      getGatewaysList 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      返回:
      A list containing the gateways.

    • getGatewaysCount

      public int getGatewaysCount()
       The names of gateways and sidecars that should apply these routes.
 Gateways in other namespaces may be referred to by
 `<gateway namespace>/<gateway name>`; specifying a gateway with no
 namespace qualifier is the same as specifying the VirtualService's
 namespace. A single VirtualService is used for sidecars inside the mesh as
 well as for one or more gateways. The selection condition imposed by this
 field can be overridden using the source field in the match conditions
 of protocol-specific routes. The reserved word `mesh` is used to imply
 all the sidecars in the mesh. When this field is omitted, the default
 gateway (`mesh`) will be used, which would apply the rule to all
 sidecars in the mesh. If a list of gateway names is provided, the
 rules will apply only to the gateways. To apply the rules to both
 gateways and sidecars, specify `mesh` as one of the gateway names.
      repeated string gateways = 2;
      指定者:
      getGatewaysCount 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      返回:
      The count of gateways.

    • getGateways

      public String getGateways(int index)
       The names of gateways and sidecars that should apply these routes.
 Gateways in other namespaces may be referred to by
 `<gateway namespace>/<gateway name>`; specifying a gateway with no
 namespace qualifier is the same as specifying the VirtualService's
 namespace. A single VirtualService is used for sidecars inside the mesh as
 well as for one or more gateways. The selection condition imposed by this
 field can be overridden using the source field in the match conditions
 of protocol-specific routes. The reserved word `mesh` is used to imply
 all the sidecars in the mesh. When this field is omitted, the default
 gateway (`mesh`) will be used, which would apply the rule to all
 sidecars in the mesh. If a list of gateway names is provided, the
 rules will apply only to the gateways. To apply the rules to both
 gateways and sidecars, specify `mesh` as one of the gateway names.
      repeated string gateways = 2;
      指定者:
      getGateways 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      参数:
      index - The index of the element to return.
      返回:
      The gateways at the given index.

    • getGatewaysBytes

      public com.google.protobuf.ByteString getGatewaysBytes(int index)
       The names of gateways and sidecars that should apply these routes.
 Gateways in other namespaces may be referred to by
 `<gateway namespace>/<gateway name>`; specifying a gateway with no
 namespace qualifier is the same as specifying the VirtualService's
 namespace. A single VirtualService is used for sidecars inside the mesh as
 well as for one or more gateways. The selection condition imposed by this
 field can be overridden using the source field in the match conditions
 of protocol-specific routes. The reserved word `mesh` is used to imply
 all the sidecars in the mesh. When this field is omitted, the default
 gateway (`mesh`) will be used, which would apply the rule to all
 sidecars in the mesh. If a list of gateway names is provided, the
 rules will apply only to the gateways. To apply the rules to both
 gateways and sidecars, specify `mesh` as one of the gateway names.
      repeated string gateways = 2;
      指定者:
      getGatewaysBytes 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      参数:
      index - The index of the value to return.
      返回:
      The bytes of the gateways at the given index.

    • setGateways

      public VirtualServiceOuterClass.VirtualService.Builder setGateways(int index, String value)
       The names of gateways and sidecars that should apply these routes.
 Gateways in other namespaces may be referred to by
 `<gateway namespace>/<gateway name>`; specifying a gateway with no
 namespace qualifier is the same as specifying the VirtualService's
 namespace. A single VirtualService is used for sidecars inside the mesh as
 well as for one or more gateways. The selection condition imposed by this
 field can be overridden using the source field in the match conditions
 of protocol-specific routes. The reserved word `mesh` is used to imply
 all the sidecars in the mesh. When this field is omitted, the default
 gateway (`mesh`) will be used, which would apply the rule to all
 sidecars in the mesh. If a list of gateway names is provided, the
 rules will apply only to the gateways. To apply the rules to both
 gateways and sidecars, specify `mesh` as one of the gateway names.
      repeated string gateways = 2;
      参数:
      index - The index to set the value at.
      value - The gateways to set.
      返回:
      This builder for chaining.

    • addGateways

      public VirtualServiceOuterClass.VirtualService.Builder addGateways(String value)
       The names of gateways and sidecars that should apply these routes.
 Gateways in other namespaces may be referred to by
 `<gateway namespace>/<gateway name>`; specifying a gateway with no
 namespace qualifier is the same as specifying the VirtualService's
 namespace. A single VirtualService is used for sidecars inside the mesh as
 well as for one or more gateways. The selection condition imposed by this
 field can be overridden using the source field in the match conditions
 of protocol-specific routes. The reserved word `mesh` is used to imply
 all the sidecars in the mesh. When this field is omitted, the default
 gateway (`mesh`) will be used, which would apply the rule to all
 sidecars in the mesh. If a list of gateway names is provided, the
 rules will apply only to the gateways. To apply the rules to both
 gateways and sidecars, specify `mesh` as one of the gateway names.
      repeated string gateways = 2;
      参数:
      value - The gateways to add.
      返回:
      This builder for chaining.

    • addAllGateways

      public VirtualServiceOuterClass.VirtualService.Builder addAllGateways(Iterable<String> values)
       The names of gateways and sidecars that should apply these routes.
 Gateways in other namespaces may be referred to by
 `<gateway namespace>/<gateway name>`; specifying a gateway with no
 namespace qualifier is the same as specifying the VirtualService's
 namespace. A single VirtualService is used for sidecars inside the mesh as
 well as for one or more gateways. The selection condition imposed by this
 field can be overridden using the source field in the match conditions
 of protocol-specific routes. The reserved word `mesh` is used to imply
 all the sidecars in the mesh. When this field is omitted, the default
 gateway (`mesh`) will be used, which would apply the rule to all
 sidecars in the mesh. If a list of gateway names is provided, the
 rules will apply only to the gateways. To apply the rules to both
 gateways and sidecars, specify `mesh` as one of the gateway names.
      repeated string gateways = 2;
      参数:
      values - The gateways to add.
      返回:
      This builder for chaining.

    • clearGateways

      public VirtualServiceOuterClass.VirtualService.Builder clearGateways()
       The names of gateways and sidecars that should apply these routes.
 Gateways in other namespaces may be referred to by
 `<gateway namespace>/<gateway name>`; specifying a gateway with no
 namespace qualifier is the same as specifying the VirtualService's
 namespace. A single VirtualService is used for sidecars inside the mesh as
 well as for one or more gateways. The selection condition imposed by this
 field can be overridden using the source field in the match conditions
 of protocol-specific routes. The reserved word `mesh` is used to imply
 all the sidecars in the mesh. When this field is omitted, the default
 gateway (`mesh`) will be used, which would apply the rule to all
 sidecars in the mesh. If a list of gateway names is provided, the
 rules will apply only to the gateways. To apply the rules to both
 gateways and sidecars, specify `mesh` as one of the gateway names.
      repeated string gateways = 2;
      返回:
      This builder for chaining.

    • addGatewaysBytes

      public VirtualServiceOuterClass.VirtualService.Builder addGatewaysBytes(com.google.protobuf.ByteString value)
       The names of gateways and sidecars that should apply these routes.
 Gateways in other namespaces may be referred to by
 `<gateway namespace>/<gateway name>`; specifying a gateway with no
 namespace qualifier is the same as specifying the VirtualService's
 namespace. A single VirtualService is used for sidecars inside the mesh as
 well as for one or more gateways. The selection condition imposed by this
 field can be overridden using the source field in the match conditions
 of protocol-specific routes. The reserved word `mesh` is used to imply
 all the sidecars in the mesh. When this field is omitted, the default
 gateway (`mesh`) will be used, which would apply the rule to all
 sidecars in the mesh. If a list of gateway names is provided, the
 rules will apply only to the gateways. To apply the rules to both
 gateways and sidecars, specify `mesh` as one of the gateway names.
      repeated string gateways = 2;
      参数:
      value - The bytes of the gateways to add.
      返回:
      This builder for chaining.

    • getHttpList

      public List<VirtualServiceOuterClass.HTTPRoute> getHttpList()
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;
      指定者:
      getHttpList 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • getHttpCount

      public int getHttpCount()
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;
      指定者:
      getHttpCount 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • getHttp

      public VirtualServiceOuterClass.HTTPRoute getHttp(int index)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;
      指定者:
      getHttp 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • setHttp

      public VirtualServiceOuterClass.VirtualService.Builder setHttp(int index, VirtualServiceOuterClass.HTTPRoute value)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • setHttp

      public VirtualServiceOuterClass.VirtualService.Builder setHttp(int index, VirtualServiceOuterClass.HTTPRoute.Builder builderForValue)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • addHttp

      public VirtualServiceOuterClass.VirtualService.Builder addHttp(VirtualServiceOuterClass.HTTPRoute value)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • addHttp

      public VirtualServiceOuterClass.VirtualService.Builder addHttp(int index, VirtualServiceOuterClass.HTTPRoute value)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • addHttp

      public VirtualServiceOuterClass.VirtualService.Builder addHttp(VirtualServiceOuterClass.HTTPRoute.Builder builderForValue)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • addHttp

      public VirtualServiceOuterClass.VirtualService.Builder addHttp(int index, VirtualServiceOuterClass.HTTPRoute.Builder builderForValue)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • addAllHttp

      public VirtualServiceOuterClass.VirtualService.Builder addAllHttp(Iterable<? extends VirtualServiceOuterClass.HTTPRoute> values)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • clearHttp

      public VirtualServiceOuterClass.VirtualService.Builder clearHttp()
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • removeHttp

      public VirtualServiceOuterClass.VirtualService.Builder removeHttp(int index)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • getHttpBuilder

      public VirtualServiceOuterClass.HTTPRoute.Builder getHttpBuilder(int index)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • getHttpOrBuilder

      public VirtualServiceOuterClass.HTTPRouteOrBuilder getHttpOrBuilder(int index)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;
      指定者:
      getHttpOrBuilder 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • getHttpOrBuilderList

      public List<? extends VirtualServiceOuterClass.HTTPRouteOrBuilder> getHttpOrBuilderList()
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;
      指定者:
      getHttpOrBuilderList 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • addHttpBuilder

      public VirtualServiceOuterClass.HTTPRoute.Builder addHttpBuilder()
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • addHttpBuilder

      public VirtualServiceOuterClass.HTTPRoute.Builder addHttpBuilder(int index)
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • getHttpBuilderList

      public List<VirtualServiceOuterClass.HTTPRoute.Builder> getHttpBuilderList()
       An ordered list of route rules for HTTP traffic. HTTP routes will be
 applied to platform service ports named 'http-*'/'http2-*'/'grpc-*', gateway
 ports with protocol HTTP/HTTP2/GRPC/ TLS-terminated-HTTPS and service
 entry ports using HTTP/HTTP2/GRPC protocols.  The first rule matching
 an incoming request is used.
      repeated .istio.networking.v1alpha3.HTTPRoute http = 3;

    • getTlsList

      public List<VirtualServiceOuterClass.TLSRoute> getTlsList()
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;
      指定者:
      getTlsList 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • getTlsCount

      public int getTlsCount()
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;
      指定者:
      getTlsCount 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • getTls

      public VirtualServiceOuterClass.TLSRoute getTls(int index)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;
      指定者:
      getTls 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • setTls

      public VirtualServiceOuterClass.VirtualService.Builder setTls(int index, VirtualServiceOuterClass.TLSRoute value)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • setTls

      public VirtualServiceOuterClass.VirtualService.Builder setTls(int index, VirtualServiceOuterClass.TLSRoute.Builder builderForValue)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • addTls

      public VirtualServiceOuterClass.VirtualService.Builder addTls(VirtualServiceOuterClass.TLSRoute value)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • addTls

      public VirtualServiceOuterClass.VirtualService.Builder addTls(int index, VirtualServiceOuterClass.TLSRoute value)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • addTls

      public VirtualServiceOuterClass.VirtualService.Builder addTls(VirtualServiceOuterClass.TLSRoute.Builder builderForValue)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • addTls

      public VirtualServiceOuterClass.VirtualService.Builder addTls(int index, VirtualServiceOuterClass.TLSRoute.Builder builderForValue)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • addAllTls

      public VirtualServiceOuterClass.VirtualService.Builder addAllTls(Iterable<? extends VirtualServiceOuterClass.TLSRoute> values)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • clearTls

      public VirtualServiceOuterClass.VirtualService.Builder clearTls()
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • removeTls

      public VirtualServiceOuterClass.VirtualService.Builder removeTls(int index)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • getTlsBuilder

      public VirtualServiceOuterClass.TLSRoute.Builder getTlsBuilder(int index)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • getTlsOrBuilder

      public VirtualServiceOuterClass.TLSRouteOrBuilder getTlsOrBuilder(int index)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;
      指定者:
      getTlsOrBuilder 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • getTlsOrBuilderList

      public List<? extends VirtualServiceOuterClass.TLSRouteOrBuilder> getTlsOrBuilderList()
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;
      指定者:
      getTlsOrBuilderList 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • addTlsBuilder

      public VirtualServiceOuterClass.TLSRoute.Builder addTlsBuilder()
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • addTlsBuilder

      public VirtualServiceOuterClass.TLSRoute.Builder addTlsBuilder(int index)
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • getTlsBuilderList

      public List<VirtualServiceOuterClass.TLSRoute.Builder> getTlsBuilderList()
       An ordered list of route rule for non-terminated TLS & HTTPS
 traffic. Routing is typically performed using the SNI value presented
 by the ClientHello message. TLS routes will be applied to platform
 service ports named 'https-*', 'tls-*', unterminated gateway ports using
 HTTPS/TLS protocols (i.e. with "passthrough" TLS mode) and service
 entry ports using HTTPS/TLS protocols.  The first rule matching an
 incoming request is used.  NOTE: Traffic 'https-*' or 'tls-*' ports
 without associated virtual service will be treated as opaque TCP
 traffic.
      repeated .istio.networking.v1alpha3.TLSRoute tls = 5;

    • getTcpList

      public List<VirtualServiceOuterClass.TCPRoute> getTcpList()
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;
      指定者:
      getTcpList 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • getTcpCount

      public int getTcpCount()
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;
      指定者:
      getTcpCount 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • getTcp

      public VirtualServiceOuterClass.TCPRoute getTcp(int index)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;
      指定者:
      getTcp 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • setTcp

      public VirtualServiceOuterClass.VirtualService.Builder setTcp(int index, VirtualServiceOuterClass.TCPRoute value)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • setTcp

      public VirtualServiceOuterClass.VirtualService.Builder setTcp(int index, VirtualServiceOuterClass.TCPRoute.Builder builderForValue)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • addTcp

      public VirtualServiceOuterClass.VirtualService.Builder addTcp(VirtualServiceOuterClass.TCPRoute value)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • addTcp

      public VirtualServiceOuterClass.VirtualService.Builder addTcp(int index, VirtualServiceOuterClass.TCPRoute value)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • addTcp

      public VirtualServiceOuterClass.VirtualService.Builder addTcp(VirtualServiceOuterClass.TCPRoute.Builder builderForValue)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • addTcp

      public VirtualServiceOuterClass.VirtualService.Builder addTcp(int index, VirtualServiceOuterClass.TCPRoute.Builder builderForValue)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • addAllTcp

      public VirtualServiceOuterClass.VirtualService.Builder addAllTcp(Iterable<? extends VirtualServiceOuterClass.TCPRoute> values)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • clearTcp

      public VirtualServiceOuterClass.VirtualService.Builder clearTcp()
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • removeTcp

      public VirtualServiceOuterClass.VirtualService.Builder removeTcp(int index)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • getTcpBuilder

      public VirtualServiceOuterClass.TCPRoute.Builder getTcpBuilder(int index)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • getTcpOrBuilder

      public VirtualServiceOuterClass.TCPRouteOrBuilder getTcpOrBuilder(int index)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;
      指定者:
      getTcpOrBuilder 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • getTcpOrBuilderList

      public List<? extends VirtualServiceOuterClass.TCPRouteOrBuilder> getTcpOrBuilderList()
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;
      指定者:
      getTcpOrBuilderList 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder

    • addTcpBuilder

      public VirtualServiceOuterClass.TCPRoute.Builder addTcpBuilder()
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • addTcpBuilder

      public VirtualServiceOuterClass.TCPRoute.Builder addTcpBuilder(int index)
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • getTcpBuilderList

      public List<VirtualServiceOuterClass.TCPRoute.Builder> getTcpBuilderList()
       An ordered list of route rules for opaque TCP traffic. TCP routes will
 be applied to any port that is not a HTTP or TLS port. The first rule
 matching an incoming request is used.
      repeated .istio.networking.v1alpha3.TCPRoute tcp = 4;

    • getExportToList

      public com.google.protobuf.ProtocolStringList getExportToList()
       A list of namespaces to which this virtual service is exported. Exporting a
 virtual service allows it to be used by sidecars and gateways defined in
 other namespaces. This feature provides a mechanism for service owners
 and mesh administrators to control the visibility of virtual services
 across namespace boundaries.

 If no namespaces are specified then the virtual service is exported to all
 namespaces by default.

 The value "." is reserved and defines an export to the same namespace that
 the virtual service is declared in. Similarly the value "*" is reserved and
 defines an export to all namespaces.

 NOTE: in the current release, the `exportTo` value is restricted to
 "." or "*" (i.e., the current namespace or all namespaces).
      repeated string export_to = 6;
      指定者:
      getExportToList 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      返回:
      A list containing the exportTo.

    • getExportToCount

      public int getExportToCount()
       A list of namespaces to which this virtual service is exported. Exporting a
 virtual service allows it to be used by sidecars and gateways defined in
 other namespaces. This feature provides a mechanism for service owners
 and mesh administrators to control the visibility of virtual services
 across namespace boundaries.

 If no namespaces are specified then the virtual service is exported to all
 namespaces by default.

 The value "." is reserved and defines an export to the same namespace that
 the virtual service is declared in. Similarly the value "*" is reserved and
 defines an export to all namespaces.

 NOTE: in the current release, the `exportTo` value is restricted to
 "." or "*" (i.e., the current namespace or all namespaces).
      repeated string export_to = 6;
      指定者:
      getExportToCount 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      返回:
      The count of exportTo.

    • getExportTo

      public String getExportTo(int index)
       A list of namespaces to which this virtual service is exported. Exporting a
 virtual service allows it to be used by sidecars and gateways defined in
 other namespaces. This feature provides a mechanism for service owners
 and mesh administrators to control the visibility of virtual services
 across namespace boundaries.

 If no namespaces are specified then the virtual service is exported to all
 namespaces by default.

 The value "." is reserved and defines an export to the same namespace that
 the virtual service is declared in. Similarly the value "*" is reserved and
 defines an export to all namespaces.

 NOTE: in the current release, the `exportTo` value is restricted to
 "." or "*" (i.e., the current namespace or all namespaces).
      repeated string export_to = 6;
      指定者:
      getExportTo 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      参数:
      index - The index of the element to return.
      返回:
      The exportTo at the given index.

    • getExportToBytes

      public com.google.protobuf.ByteString getExportToBytes(int index)
       A list of namespaces to which this virtual service is exported. Exporting a
 virtual service allows it to be used by sidecars and gateways defined in
 other namespaces. This feature provides a mechanism for service owners
 and mesh administrators to control the visibility of virtual services
 across namespace boundaries.

 If no namespaces are specified then the virtual service is exported to all
 namespaces by default.

 The value "." is reserved and defines an export to the same namespace that
 the virtual service is declared in. Similarly the value "*" is reserved and
 defines an export to all namespaces.

 NOTE: in the current release, the `exportTo` value is restricted to
 "." or "*" (i.e., the current namespace or all namespaces).
      repeated string export_to = 6;
      指定者:
      getExportToBytes 在接口中 VirtualServiceOuterClass.VirtualServiceOrBuilder
      参数:
      index - The index of the value to return.
      返回:
      The bytes of the exportTo at the given index.

    • setExportTo

      public VirtualServiceOuterClass.VirtualService.Builder setExportTo(int index, String value)
       A list of namespaces to which this virtual service is exported. Exporting a
 virtual service allows it to be used by sidecars and gateways defined in
 other namespaces. This feature provides a mechanism for service owners
 and mesh administrators to control the visibility of virtual services
 across namespace boundaries.

 If no namespaces are specified then the virtual service is exported to all
 namespaces by default.

 The value "." is reserved and defines an export to the same namespace that
 the virtual service is declared in. Similarly the value "*" is reserved and
 defines an export to all namespaces.

 NOTE: in the current release, the `exportTo` value is restricted to
 "." or "*" (i.e., the current namespace or all namespaces).
      repeated string export_to = 6;
      参数:
      index - The index to set the value at.
      value - The exportTo to set.
      返回:
      This builder for chaining.

    • addExportTo

      public VirtualServiceOuterClass.VirtualService.Builder addExportTo(String value)
       A list of namespaces to which this virtual service is exported. Exporting a
 virtual service allows it to be used by sidecars and gateways defined in
 other namespaces. This feature provides a mechanism for service owners
 and mesh administrators to control the visibility of virtual services
 across namespace boundaries.

 If no namespaces are specified then the virtual service is exported to all
 namespaces by default.

 The value "." is reserved and defines an export to the same namespace that
 the virtual service is declared in. Similarly the value "*" is reserved and
 defines an export to all namespaces.

 NOTE: in the current release, the `exportTo` value is restricted to
 "." or "*" (i.e., the current namespace or all namespaces).
      repeated string export_to = 6;
      参数:
      value - The exportTo to add.
      返回:
      This builder for chaining.

    • addAllExportTo

      public VirtualServiceOuterClass.VirtualService.Builder addAllExportTo(Iterable<String> values)
       A list of namespaces to which this virtual service is exported. Exporting a
 virtual service allows it to be used by sidecars and gateways defined in
 other namespaces. This feature provides a mechanism for service owners
 and mesh administrators to control the visibility of virtual services
 across namespace boundaries.

 If no namespaces are specified then the virtual service is exported to all
 namespaces by default.

 The value "." is reserved and defines an export to the same namespace that
 the virtual service is declared in. Similarly the value "*" is reserved and
 defines an export to all namespaces.

 NOTE: in the current release, the `exportTo` value is restricted to
 "." or "*" (i.e., the current namespace or all namespaces).
      repeated string export_to = 6;
      参数:
      values - The exportTo to add.
      返回:
      This builder for chaining.

    • clearExportTo

      public VirtualServiceOuterClass.VirtualService.Builder clearExportTo()
       A list of namespaces to which this virtual service is exported. Exporting a
 virtual service allows it to be used by sidecars and gateways defined in
 other namespaces. This feature provides a mechanism for service owners
 and mesh administrators to control the visibility of virtual services
 across namespace boundaries.

 If no namespaces are specified then the virtual service is exported to all
 namespaces by default.

 The value "." is reserved and defines an export to the same namespace that
 the virtual service is declared in. Similarly the value "*" is reserved and
 defines an export to all namespaces.

 NOTE: in the current release, the `exportTo` value is restricted to
 "." or "*" (i.e., the current namespace or all namespaces).
      repeated string export_to = 6;
      返回:
      This builder for chaining.

    • addExportToBytes

      public VirtualServiceOuterClass.VirtualService.Builder addExportToBytes(com.google.protobuf.ByteString value)
       A list of namespaces to which this virtual service is exported. Exporting a
 virtual service allows it to be used by sidecars and gateways defined in
 other namespaces. This feature provides a mechanism for service owners
 and mesh administrators to control the visibility of virtual services
 across namespace boundaries.

 If no namespaces are specified then the virtual service is exported to all
 namespaces by default.

 The value "." is reserved and defines an export to the same namespace that
 the virtual service is declared in. Similarly the value "*" is reserved and
 defines an export to all namespaces.

 NOTE: in the current release, the `exportTo` value is restricted to
 "." or "*" (i.e., the current namespace or all namespaces).
      repeated string export_to = 6;
      参数:
      value - The bytes of the exportTo to add.
      返回:
      This builder for chaining.

    • setUnknownFields

      public final VirtualServiceOuterClass.VirtualService.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      指定者:
      setUnknownFields 在接口中 com.google.protobuf.Message.Builder
      覆盖:
      setUnknownFields 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>

    • mergeUnknownFields

      public final VirtualServiceOuterClass.VirtualService.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      指定者:
      mergeUnknownFields 在接口中 com.google.protobuf.Message.Builder
      覆盖:
      mergeUnknownFields 在类中 com.google.protobuf.GeneratedMessageV3.Builder<VirtualServiceOuterClass.VirtualService.Builder>