v1

Documentation

Overview

This package has the automatically generated typed clients.

Index

• type CoordinationV1Client
  • func New(c rest.Interface) *CoordinationV1Client
  • func NewForConfig(c *rest.Config) (*CoordinationV1Client, error)
  • func NewForConfigAndClient(c *rest.Config, h *http.Client) (*CoordinationV1Client, error)
  • func NewForConfigOrDie(c *rest.Config) *CoordinationV1Client
  • func (c *CoordinationV1Client) Leases(namespace string) LeaseInterface
  • func (c *CoordinationV1Client) RESTClient() rest.Interface
• type CoordinationV1Interface
• type LeaseExpansion
• type LeaseInterface
• type LeasesGetter

Types

type CoordinationV1Client

type CoordinationV1Client struct {
	// contains filtered or unexported fields
}

CoordinationV1Client is used to interact with features provided by the coordination.k8s.io group.

func New

func New(c rest.Interface) *CoordinationV1Client

New creates a new CoordinationV1Client for the given RESTClient.

func NewForConfig

func NewForConfig(c *rest.Config) (*CoordinationV1Client, error)

NewForConfig creates a new CoordinationV1Client for the given config. NewForConfig is equivalent to NewForConfigAndClient(c, httpClient), where httpClient was generated with rest.HTTPClientFor(c).

func NewForConfigAndClient

func NewForConfigAndClient(c *rest.Config, h *http.Client) (*CoordinationV1Client, error)

NewForConfigAndClient creates a new CoordinationV1Client for the given config and http client. Note the http client provided takes precedence over the configured transport values.

func NewForConfigOrDie

func NewForConfigOrDie(c *rest.Config) *CoordinationV1Client

NewForConfigOrDie creates a new CoordinationV1Client for the given config and panics if there is an error in the config.

func (*CoordinationV1Client) Leases

func (c *CoordinationV1Client) Leases(namespace string) LeaseInterface

func (*CoordinationV1Client) RESTClient

func (c *CoordinationV1Client) RESTClient() rest.Interface

RESTClient returns a RESTClient that is used to communicate with API server by this client implementation.

type CoordinationV1Interface

type CoordinationV1Interface interface {
	RESTClient() rest.Interface
	LeasesGetter
}

type LeaseExpansion

type LeaseExpansion interface{}

type LeaseInterface

type LeaseInterface interface {
	Create(ctx context.Context, lease *v1.Lease, opts metav1.CreateOptions) (*v1.Lease, error)
	Update(ctx context.Context, lease *v1.Lease, opts metav1.UpdateOptions) (*v1.Lease, error)
	Delete(ctx context.Context, name string, opts metav1.DeleteOptions) error
	DeleteCollection(ctx context.Context, opts metav1.DeleteOptions, listOpts metav1.ListOptions) error
	Get(ctx context.Context, name string, opts metav1.GetOptions) (*v1.Lease, error)
	List(ctx context.Context, opts metav1.ListOptions) (*v1.LeaseList, error)
	Watch(ctx context.Context, opts metav1.ListOptions) (watch.Interface, error)
	Patch(ctx context.Context, name string, pt types.PatchType, data []byte, opts metav1.PatchOptions, subresources ...string) (result *v1.Lease, err error)
	Apply(ctx context.Context, lease *coordinationv1.LeaseApplyConfiguration, opts metav1.ApplyOptions) (result *v1.Lease, err error)
	LeaseExpansion
}

LeaseInterface has methods to work with Lease resources.

type LeasesGetter

type LeasesGetter interface {
	Leases(namespace string) LeaseInterface
}

LeasesGetter has a method to return a LeaseInterface. A group's client should implement this interface.