connectivitycheck

package
v0.0.0-...-de93ea6 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Dec 12, 2024 License: Apache-2.0 Imports: 34 Imported by: 0

Documentation

Index

Constants

This section is empty.

Variables

This section is empty.

Functions

func NewPodNetworkConnectivityCheckTemplate

func NewPodNetworkConnectivityCheckTemplate(address, namespace string, options ...func(*applyconfigv1alpha1.PodNetworkConnectivityCheckApplyConfiguration)) *applyconfigv1alpha1.PodNetworkConnectivityCheckApplyConfiguration

new PodNetworkConnectivityCheck whose name is '$(SOURCE)-to-$(TARGET)'. Use the WithSource and WithTarget option funcs to replace the '$(SOURCE)' and '$(TARGET)' tokens.

func Start

func Start(ctx context.Context, kubeConfig *rest.Config) error

func WithSource

WithSource option replaces the $(SOURCE) token in the name.

func WithTLSClientCert

WithTLSClientCert option specifies the name of the secret in the check namespace that contains a tls client certificate (and key) to use when performing the check.

func WithTarget

WithTarget option replaces the $(TARGET) token in the name.

Types

type NetworkConnectivityCheckController

type NetworkConnectivityCheckController interface {
	connectivitycheckcontroller.ConnectivityCheckController
}

func NewNetworkConnectivityCheckController

func NewNetworkConnectivityCheckController(
	operatorClient v1helpers.OperatorClient,
	configClient *configv1client.Clientset,
	operatorcontrolplaneClient *operatorcontrolplaneclient.Clientset,
	apiextensionsClient *apiextensionsclient.Clientset,
	kubeInformersForNamespaces v1helpers.KubeInformersForNamespaces,
	configInformers configinformers.SharedInformerFactory,
	apiextensionsInformers apiextensionsinformers.SharedInformerFactory,
	operatorcontrolplaneInformers operatorcontrolplaneinformers.SharedInformerFactory,
	recorder events.Recorder,
) NetworkConnectivityCheckController

NetworkConnectivyCheckController consumes a series of clients, informers and a recorders. With those objects it generates a series of templates for creating PodNetworkConnectivityChecks CRs, in particular: Checks between network-check-source pod and every kube apiserver service and endpoints Checks between network-check-source pod and every openshift apiserver service and endpoints Checks between network-check-source pod and every LB Checks between network-check-source pod and network-check-target service and endpoints this being managed by a Daemonset

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL