程序包 istio.networking.v1alpha3

接口 VirtualServiceOuterClass.VirtualServiceOrBuilder

所有超级接口:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
所有已知实现类:
VirtualServiceOuterClass.VirtualService, VirtualServiceOuterClass.VirtualService.Builder
封闭类:
VirtualServiceOuterClass
public static interface VirtualServiceOuterClass.VirtualServiceOrBuilder extends com.google.protobuf.MessageOrBuilder

  • 方法详细资料

    • getHostsList

      List<String> 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;
      返回:
      A list containing the hosts.

    • getHostsCount

      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;
      返回:
      The count of hosts.

    • getHosts

      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;
      参数:
      index - The index of the element to return.
      返回:
      The hosts at the given index.

    • getHostsBytes

      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;
      参数:
      index - The index of the value to return.
      返回:
      The bytes of the hosts at the given index.

    • getGatewaysList

      List<String> 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;
      返回:
      A list containing the gateways.

    • getGatewaysCount

      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;
      返回:
      The count of gateways.

    • getGateways

      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;
      参数:
      index - The index of the element to return.
      返回:
      The gateways at the given index.

    • getGatewaysBytes

      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;
      参数:
      index - The index of the value to return.
      返回:
      The bytes of the gateways at the given index.

    • getHttpList

      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;

    • getHttp

      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;

    • getHttpCount

      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;

    • getHttpOrBuilderList

      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;

    • getHttpOrBuilder

      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;

    • getTlsList

      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;

    • getTls

      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;

    • getTlsCount

      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;

    • getTlsOrBuilderList

      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;

    • getTlsOrBuilder

      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;

    • getTcpList

      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;

    • getTcp

      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;

    • getTcpCount

      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;

    • getTcpOrBuilderList

      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;

    • getTcpOrBuilder

      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;

    • getExportToList

      List<String> 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;
      返回:
      A list containing the exportTo.

    • getExportToCount

      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;
      返回:
      The count of exportTo.

    • getExportTo

      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;
      参数:
      index - The index of the element to return.
      返回:
      The exportTo at the given index.

    • getExportToBytes

      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;
      参数:
      index - The index of the value to return.
      返回:
      The bytes of the exportTo at the given index.