所有类和接口
类
说明
AbstractConnection maintains the life cycle of the connection.
The aggregated mesh configuration services allow a single
management server, via a single gRPC stream, to deliver all API
updates.
A stub to allow clients to do synchronous rpc calls to service AggregatedMeshConfigService.
A stub to allow clients to do ListenableFuture-style rpc calls to service AggregatedMeshConfigService.
Base class for the server implementation of the service AggregatedMeshConfigService.
A stub to allow clients to do asynchronous rpc calls to service AggregatedMeshConfigService.
The aggregated mesh configuration services allow a single
management server, via a single gRPC stream, to deliver all API
updates.
`Any` contains an arbitrary serialized protocol buffer message along with a
URL that describes the type of the serialized message.
`Any` contains an arbitrary serialized protocol buffer message along with a
URL that describes the type of the serialized message.
This interface is used to generator mcp resources or xds data.
SSL/TLS related settings for upstream connections.
SSL/TLS related settings for upstream connections.
TLS connection mode
Connection pool settings for an upstream host.
Connection pool settings for an upstream host.
Settings applicable to HTTP1.1/HTTP2/GRPC connections.
Settings applicable to HTTP1.1/HTTP2/GRPC connections.
Policy for upgrading http1.1 connections to http2.
Settings common to both HTTP and TCP upstream connections.
Settings common to both HTTP and TCP upstream connections.
TCP keepalive.
TCP keepalive.
DestinationRule defines policies that apply to traffic intended for a service
after routing has occurred.
DestinationRule defines policies that apply to traffic intended for a service
after routing has occurred.
Load balancing policies to apply for a specific destination.
Load balancing policies to apply for a specific destination.
Consistent Hash-based load balancing can be used to provide soft
session affinity based on HTTP headers, cookies or other
properties.
Consistent Hash-based load balancing can be used to provide soft
session affinity based on HTTP headers, cookies or other
properties.
Describes a HTTP cookie that will be used as the hash key for the
Consistent Hash load balancer.
Describes a HTTP cookie that will be used as the hash key for the
Consistent Hash load balancer.
Standard load balancing algorithms that require no tuning.
Locality-weighted load balancing allows administrators to control the
distribution of traffic to endpoints based on the localities of where the
traffic originates and where it will terminate.
Locality-weighted load balancing allows administrators to control the
distribution of traffic to endpoints based on the localities of where the
traffic originates and where it will terminate.
Describes how traffic originating in the 'from' zone or sub-zone is
distributed over a set of 'to' zones.
Describes how traffic originating in the 'from' zone or sub-zone is
distributed over a set of 'to' zones.
Specify the traffic failover policy across regions.
Specify the traffic failover policy across regions.
A Circuit breaker implementation that tracks the status of each
individual host in the upstream service.
A Circuit breaker implementation that tracks the status of each
individual host in the upstream service.
A subset of endpoints of a service.
A subset of endpoints of a service.
Traffic policies to apply for a specific destination, across all
destination ports.
Traffic policies to apply for a specific destination, across all
destination ports.
Traffic policies that apply to specific ports of the service
Traffic policies that apply to specific ports of the service
EnvoyFilter provides a mechanism to customize the Envoy configuration
generated by Istio Pilot.
`ApplyTo` specifies where in the Envoy configuration, the given patch should be applied.
EnvoyFilter provides a mechanism to customize the Envoy configuration
generated by Istio Pilot.
Conditions specified in `ClusterMatch` must be met for the patch
to be applied to a cluster.
Conditions specified in `ClusterMatch` must be met for the patch
to be applied to a cluster.
One or more match conditions to be met before a patch is applied
to the generated configuration for a given proxy.
One or more match conditions to be met before a patch is applied
to the generated configuration for a given proxy.
Changes to be made to various envoy config objects.
Changes to be made to various envoy config objects.
Conditions specified in a listener match must be met for the
patch to be applied to a specific listener across all filter
chains, or a specific filter chain inside the listener.
Conditions specified in a listener match must be met for the
patch to be applied to a specific listener across all filter
chains, or a specific filter chain inside the listener.
For listeners with multiple filter chains (e.g., inbound
listeners on sidecars with permissive mTLS, gateway listeners
with multiple SNI matches), the filter chain match can be used
to select a specific filter chain to patch.
For listeners with multiple filter chains (e.g., inbound
listeners on sidecars with permissive mTLS, gateway listeners
with multiple SNI matches), the filter chain match can be used
to select a specific filter chain to patch.
Conditions to match a specific filter within a filter chain.
Conditions to match a specific filter within a filter chain.
Conditions to match a specific filter within another
filter.
Conditions to match a specific filter within another
filter.
Patch specifies how the selected object should be modified.
Patch specifies how the selected object should be modified.
FilterClass determines the filter insertion point in the filter chain
relative to the filters implicitly inserted by the control plane.
Operation denotes how the patch should be applied to the selected
configuration.
PatchContext selects a class of configurations based on the
traffic flow direction and workload type.
One or more properties of the proxy to match on.
One or more properties of the proxy to match on.
Conditions specified in RouteConfigurationMatch must be met for
the patch to be applied to a route configuration object or a
specific virtual host within the route configuration.
Conditions specified in RouteConfigurationMatch must be met for
the patch to be applied to a route configuration object or a
specific virtual host within the route configuration.
Match a specific route inside a virtual host in a route configuration.
Action refers to the route action taken by Envoy when a http route matches.
Match a specific route inside a virtual host in a route configuration.
Match a specific virtual host inside a route configuration.
Match a specific virtual host inside a route configuration.
EventProcessor.
Gateway describes a load balancer operating at the edge of the mesh
receiving incoming or outgoing HTTP/TCP connections.
Gateway describes a load balancer operating at the edge of the mesh
receiving incoming or outgoing HTTP/TCP connections.
Port describes the properties of a specific port of a service.
Port describes the properties of a specific port of a service.
`Server` describes the properties of the proxy on a given load balancer
port.
`Server` describes the properties of the proxy on a given load balancer
port.
Protobuf type
istio.networking.v1alpha3.ServerTLSSettingsProtobuf type
istio.networking.v1alpha3.ServerTLSSettings
TLS modes enforced by the proxy
TLS protocol versions.
Istio starter.
Stores some configurations for Istio integration.
Istio module enabled filter by spring packages scan.
Loggers Holder.
IncrementalMeshConfigRequest are be sent in 2 situations:
1.
IncrementalMeshConfigRequest are be sent in 2 situations:
1.
IncrementalMeshConfigResponses do not need to include a full
snapshot of the tracked resources.
IncrementalMeshConfigResponses do not need to include a full
snapshot of the tracked resources.
A MeshConfigRequest requests a set of versioned resources of the
same type for a given client.
A MeshConfigRequest requests a set of versioned resources of the
same type for a given client.
A MeshConfigResponse delivers a set of versioned resources of the
same type in response to a MeshConfigRequest.
A MeshConfigResponse delivers a set of versioned resources of the
same type in response to a MeshConfigRequest.
A RequestResource can be sent in two situations:
Initial message in an MCP bidirectional change stream
as an ACK or NACK response to a previous Resources.
A RequestResource can be sent in two situations:
Initial message in an MCP bidirectional change stream
as an ACK or NACK response to a previous Resources.
Resources do not need to include a full snapshot of the tracked
resources.
Resources do not need to include a full snapshot of the tracked
resources.
Identifies a specific MCP sink node instance.
Identifies a specific MCP sink node instance.
Metadata information that all resources within the Mesh Configuration Protocol must have.
Metadata information that all resources within the Mesh Configuration Protocol must have.
nacos mcp service.
Resource as transferred via the Mesh Configuration Protocol.
Resource as transferred via the Mesh Configuration Protocol.
Service where the source is the gRPC client.
Service where the source is the gRPC client.
A stub to allow clients to do synchronous rpc calls to service ResourceSink.
A stub to allow clients to do ListenableFuture-style rpc calls to service ResourceSink.
Base class for the server implementation of the service ResourceSink.
A stub to allow clients to do asynchronous rpc calls to service ResourceSink.
Service where the sink is the gRPC client.
Service where the sink is the gRPC client.
A stub to allow clients to do synchronous rpc calls to service ResourceSource.
A stub to allow clients to do ListenableFuture-style rpc calls to service ResourceSource.
Base class for the server implementation of the service ResourceSource.
A stub to allow clients to do asynchronous rpc calls to service ResourceSource.
ServiceEntry enables adding additional entries into Istio's internal
service registry.
ServiceEntry enables adding additional entries into Istio's internal
service registry.
Location specifies whether the service is part of Istio mesh or
outside the mesh.
Resolution determines how the proxy will resolve the IP addresses of
the network endpoints associated with the service, so that it can
route to one of them.
`CaptureMode` describes how traffic to a listener is expected to be
captured.
`IstioEgressListener` specifies the properties of an outbound traffic
listener on the sidecar proxy attached to a workload instance.
`IstioEgressListener` specifies the properties of an outbound traffic
listener on the sidecar proxy attached to a workload instance.
`IstioIngressListener` specifies the properties of an inbound
traffic listener on the sidecar proxy attached to a workload instance.
`IstioIngressListener` specifies the properties of an inbound
traffic listener on the sidecar proxy attached to a workload instance.
`OutboundTrafficPolicy` sets the default behavior of the sidecar for
handling outbound traffic from the application.
`OutboundTrafficPolicy` sets the default behavior of the sidecar for
handling outbound traffic from the application.
Protobuf enum
istio.networking.v1alpha3.OutboundTrafficPolicy.Mode
`Sidecar` describes the configuration of the sidecar proxy that mediates
inbound and outbound communication of the workload instance to which it is
attached.
`Sidecar` describes the configuration of the sidecar proxy that mediates
inbound and outbound communication of the workload instance to which it is
attached.
`WorkloadSelector` specifies the criteria used to determine if the
`Gateway`, `Sidecar`, or `EnvoyFilter` or `ServiceEntry`
configuration can be applied to a proxy.
`WorkloadSelector` specifies the criteria used to determine if the
`Gateway`, `Sidecar`, or `EnvoyFilter` or `ServiceEntry`
configuration can be applied to a proxy.
Describes the Cross-Origin Resource Sharing (CORS) policy, for a given
service.
Describes the Cross-Origin Resource Sharing (CORS) policy, for a given
service.
Describes the delegate VirtualService.
Describes the delegate VirtualService.
Destination indicates the network addressable service to which the
request/connection will be sent after processing a routing rule.
Destination indicates the network addressable service to which the
request/connection will be sent after processing a routing rule.
Message headers can be manipulated when Envoy forwards requests to,
or responses from, a destination service.
Message headers can be manipulated when Envoy forwards requests to,
or responses from, a destination service.
HeaderOperations Describes the header manipulations to apply
HeaderOperations Describes the header manipulations to apply
HTTPFaultInjection can be used to specify one or more faults to inject
while forwarding HTTP requests to the destination specified in a route.
Abort specification is used to prematurely abort a request with a
pre-specified error code.
Abort specification is used to prematurely abort a request with a
pre-specified error code.
HTTPFaultInjection can be used to specify one or more faults to inject
while forwarding HTTP requests to the destination specified in a route.
Delay specification is used to inject latency into the request
forwarding path.
Delay specification is used to inject latency into the request
forwarding path.
HttpMatchRequest specifies a set of criterion to be met in order for the
rule to be applied to the HTTP request.
HttpMatchRequest specifies a set of criterion to be met in order for the
rule to be applied to the HTTP request.
HTTPRedirect can be used to send a 301 redirect response to the caller,
where the Authority/Host and the URI in the response can be swapped with
the specified values.
HTTPRedirect can be used to send a 301 redirect response to the caller,
where the Authority/Host and the URI in the response can be swapped with
the specified values.
Describes the retry policy to use when a HTTP request fails.
Describes the retry policy to use when a HTTP request fails.
HTTPRewrite can be used to rewrite specific parts of a HTTP request
before forwarding the request to the destination.
HTTPRewrite can be used to rewrite specific parts of a HTTP request
before forwarding the request to the destination.
Describes match conditions and actions for routing HTTP/1.1, HTTP2, and
gRPC traffic.
Describes match conditions and actions for routing HTTP/1.1, HTTP2, and
gRPC traffic.
Each routing rule is associated with one or more service versions (see
glossary in beginning of document).
Each routing rule is associated with one or more service versions (see
glossary in beginning of document).
L4 connection match attributes.
L4 connection match attributes.
Percent specifies a percentage in the range of [0.0, 100.0].
Percent specifies a percentage in the range of [0.0, 100.0].
PortSelector specifies the number of a port to be used for
matching or selection for final routing.
PortSelector specifies the number of a port to be used for
matching or selection for final routing.
L4 routing rule weighted destination.
L4 routing rule weighted destination.
Describes how to match a given string in HTTP headers.
Describes how to match a given string in HTTP headers.
Describes match conditions and actions for routing TCP traffic.
Describes match conditions and actions for routing TCP traffic.
TLS connection match attributes.
TLS connection match attributes.
Describes match conditions and actions for routing unterminated TLS
traffic (TLS/HTTPS) The following routing rule forwards unterminated TLS
traffic arriving at port 443 of gateway called "mygateway" to internal
services in the mesh based on the SNI value
Describes match conditions and actions for routing unterminated TLS
traffic (TLS/HTTPS) The following routing rule forwards unterminated TLS
traffic arriving at port 443 of gateway called "mygateway" to internal
services in the mesh based on the SNI value
Configuration affecting traffic routing.
Configuration affecting traffic routing.
WorkloadEntry enables specifying the properties of a single non-Kubernetes workload such a VM or a bare metal services that can be referred to by service entries.
WorkloadEntry enables specifying the properties of a single non-Kubernetes workload such a VM or a bare metal services that can be referred to by service entries.
Protobuf type
istio.networking.v1alpha3.ExecHealthCheckConfigProtobuf type
istio.networking.v1alpha3.ExecHealthCheckConfigProtobuf type
istio.networking.v1alpha3.HTTPHeaderProtobuf type
istio.networking.v1alpha3.HTTPHeaderProtobuf type
istio.networking.v1alpha3.HTTPHealthCheckConfigProtobuf type
istio.networking.v1alpha3.HTTPHealthCheckConfigProtobuf type
istio.networking.v1alpha3.ReadinessProbeProtobuf type
istio.networking.v1alpha3.ReadinessProbeProtobuf type
istio.networking.v1alpha3.TCPHealthCheckConfigProtobuf type
istio.networking.v1alpha3.TCPHealthCheckConfig
`WorkloadGroup` enables specifying the properties of a single workload for bootstrap and
provides a template for `WorkloadEntry`, similar to how `Deployment` specifies properties
of workloads via `Pod` templates.
`WorkloadGroup` enables specifying the properties of a single workload for bootstrap and
provides a template for `WorkloadEntry`, similar to how `Deployment` specifies properties
of workloads via `Pod` templates.
`ObjectMeta` describes metadata that will be attached to a `WorkloadEntry`.
`ObjectMeta` describes metadata that will be attached to a `WorkloadEntry`.