package
99.0.0+incompatible
Repository: https://github.com/poy/knative-pkg.git
Documentation: pkg.go.dev

# README

What are these files?

These are Go structs for Istio CRD. We translated them from proto files in https://github.com/istio/api/tree/master/networking/v1alpha3 .

Why do we hand-translate from proto? i.e Why can't we vendor these?

Istio needs to run on many platforms and as a reason they represent their objects internally as proto. On Kubernetes, their API take in JSON objects and convert to proto before processing them.

So they have nothing we can vendor, except for the Go files that are generated by the proto compiler, which is not compatible with K8s API code-generator at all.

We may be able to donate our translation so they can maintain it themselves. See https://github.com/istio/istio/issues/6084.

# Functions

Kind takes an unqualified kind and returns back a Group qualified GroupKind.
Resource takes an unqualified resource and returns a Group qualified GroupResource.

# Constants

No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
The least request load balancer uses an O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests.
This option will forward the connection to the original IP address requested by the caller without doing any form of load balancing.
The random load balancer selects a random healthy host.
Round Robin policy.
Do not setup a TLS connection to the upstream endpoint.
Secure connections to the upstream using mutual TLS by presenting client certificates for authentication.
Secure connections to the upstream using mutual TLS by presenting client certificates for authentication.
If set to "MUTUAL", the proxy will secure connections to the upstream using mutual TLS by presenting client certificates for authentication.
If set to "PASSTHROUGH", the proxy will forward the connection to the upstream server selected based on the SNI string presented by the client.
Originate a TLS connection to the upstream endpoint.
If set to "SIMPLE", the proxy will secure connections with standard TLS semantics.

# Variables

No description provided by the author
No description provided by the author
SchemeGroupVersion is group version used to register these objects.

# Structs

Connection pool settings for an upstream host.
Consistent Hash-based load balancing can be used to provide soft session affinity based on HTTP headers, cookies or other properties.
Describes the Cross-Origin Resource Sharing (CORS) policy, for a given service.
Destination indicates the network addressable service to which the request/connection will be sent after processing a routing rule.
+genclient +k8s:deepcopy-gen:interfaces=k8s.io/apimachinery/pkg/runtime.Object DestinationRule.
+k8s:deepcopy-gen:interfaces=k8s.io/apimachinery/pkg/runtime.Object DestinationRuleList is a list of DestinationRule resources.
DestinationRule defines policies that apply to traffic intended for a service after routing has occurred.
Gateway describes a load balancer operating at the edge of the mesh receiving incoming or outgoing HTTP/TCP connections.
GatewayList is a list of Gateway resources.
No description provided by the author
HeaderOperations Describes the header manipulations to apply.
Headers describes header manipulation rules.
Describes a HTTP cookie that will be used as the hash key for the Consistent Hash load balancer.
HTTPFaultInjection can be used to specify one or more faults to inject while forwarding http requests to the destination specified in a route.
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 302 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.
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.
No description provided by the author
Settings applicable to HTTP1.1/HTTP2/GRPC connections.
Abort specification is used to prematurely abort a request with a pre-specified error code.
Delay specification is used to inject latency into the request forwarding path.
L4 connection match attributes.
Load balancing policies to apply for a specific destination.
A Circuit breaker implementation that tracks the status of each individual host in the upstream service.
Port describes the properties of a specific port of a service.
PortSelector specifies the number of a port to be used for matching or selection for final routing.
Traffic policies that apply to specific ports of the service.
Server describes the properties of the proxy on a given load balancer port.
A subset of endpoints of a service.
Describes match conditions and actions for routing TCP traffic.
Settings common to both HTTP and TCP upstream connections.
TLS connection match attributes.
No description provided by the author
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.
SSL/TLS related settings for upstream connections.
Traffic policies to apply for a specific destination, across all destination ports.
VirtualService.
VirtualServiceList is a list of VirtualService resources.
A VirtualService defines a set of traffic routing rules to apply when a host is addressed.

# Type aliases

No description provided by the author
Standard load balancing algorithms that require no tuning.
TLS connection mode.
TLS modes enforced by the proxy.