Webhook connects to a third party API server to handle the secrets generation configuration parameters in spec. You can specify the server, the token, and additional body parameters. See documentation for the full API specification for requests and responses.
4 top-level fields · last changed in External Secrets Operator v0.16.2
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
WebhookSpec controls the behavior of the external generator. Any body parameters should be passed to the server through the parameters field.
Auth specifies a authorization protocol. Only one protocol may be set.
NTLMProtocol configures the store to use NTLM for auth
A reference to a specific 'key' within a Secret resource. In some instances, `key` is a required field.
A key in the referenced Secret. Some instances of this field may be defaulted, in others it may be required.
The name of the Secret resource being referred to.
The namespace of the Secret resource being referred to. Ignored if referent is not cluster-scoped, otherwise defaults to the namespace of the referent.
A reference to a specific 'key' within a Secret resource. In some instances, `key` is a required field.
A key in the referenced Secret. Some instances of this field may be defaulted, in others it may be required.
The name of the Secret resource being referred to.
The namespace of the Secret resource being referred to. Ignored if referent is not cluster-scoped, otherwise defaults to the namespace of the referent.
Body
PEM encoded CA bundle used to validate webhook server certificate. Only used if the Server URL is using HTTPS protocol. This parameter is ignored for plain HTTP protocol connection. If not set the system root certificates are used to validate the TLS connection.
The provider for the CA bundle to use to validate webhook server certificate.
The key where the CA certificate can be found in the Secret or ConfigMap.
The name of the object located at the provider type.
The namespace the Provider type is in.
The type of provider to use such as "Secret", or "ConfigMap".
Headers
Webhook Method
Result formatting
Json path of return value
Secrets to fill in templates These secrets will be passed to the templating function as key value pairs under the given name
Name of this secret in templates
Secret ref to fill in credentials
The key where the token is found.
The name of the Secret resource being referred to.
Timeout
Webhook url to call
Source: bundle.yaml
Changes to Webhook (generators.external-secrets.io/v1alpha1) in each External Secrets Operator version, compared to the version before it.
1 property has been added
Released · View Webhook in v0.16.2
1 property has changed the description
Released · View Webhook in v0.11.0
Webhook was first seen on this version of External Secrets Operator
Released · View Webhook in v0.9.13
No examples of Webhook yet. Contribute one on GitHub.
kubespec.dev