content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
## Bitwarden Secrets Manager Provider This section describes how to set up the Bitwarden Secrets Manager provider for External Secrets Operator (ESO). !!! note [Bitwarden Secrets Manager](https://bitwarden.com/products/secrets-manager/) enables developers, DevOps, and cybersecurity teams to centrally store, manage, and... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/bitwarden-secrets-manager.md | main | external-secrets | [
-0.10554347932338715,
-0.041133541613817215,
-0.054768066853284836,
-0.028559239581227303,
-0.013131656683981419,
-0.022112231701612473,
0.03299100324511528,
0.05289912968873978,
-0.04608473554253578,
-0.006181747652590275,
0.0029511828906834126,
0.011414135806262493,
0.055550020188093185,
... | 0.184807 |
projectID within the same organization we error ```yaml apiVersion: external-secrets.io/v1 kind: ExternalSecret metadata: name: bitwarden spec: refreshInterval: 1h0m0s secretStoreRef: # This name must match the metadata.name in the `SecretStore` name: bitwarden-secretsmanager kind: SecretStore data: - secretKey: test r... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/bitwarden-secrets-manager.md | main | external-secrets | [
-0.04182783141732216,
0.0010548339923843741,
-0.005513304378837347,
0.005026023369282484,
-0.025375565513968468,
-0.030674975365400314,
-0.04187754914164543,
-0.03039352409541607,
0.07574314624071121,
0.039196617901325226,
0.03462468832731247,
-0.09725847095251083,
0.008927568793296814,
-0... | 0.023484 |
## Yandex Certificate Manager External Secrets Operator integrates with [Yandex Certificate Manager](https://cloud.yandex.com/docs/certificate-manager/) for secret management. ### Prerequisites \* [External Secrets Operator installed](../introduction/getting-started.md#installing-with-helm) \* [Yandex.Cloud CLI install... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/yandex-certificate-manager.md | main | external-secrets | [
-0.08426864445209503,
-0.013801607303321362,
0.004209350794553757,
-0.02769615687429905,
0.010216801427304745,
-0.0016747876070439816,
0.07759695500135422,
-0.01338293869048357,
0.05711332708597183,
0.036254167556762695,
0.03640361130237579,
-0.030767470598220825,
0.08662194758653641,
0.05... | 0.042565 |
External Secrets Operator integrates with [Cloud.ru](https://cloud.ru) for secret management. Cloud.ru Secret Manager works in conjunction with the Key Manager cryptographic key management system to ensure secure encryption of secrets. ### Authentication \* Before you can use the Cloud.ru Secret Manager, you need to cr... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/cloudru.md | main | external-secrets | [
-0.06282803416252136,
-0.043332528322935104,
-0.0823478177189827,
0.049960918724536896,
-0.007124601863324642,
0.017924033105373383,
0.03458177670836449,
0.02746211551129818,
0.07706449180841446,
0.07461189478635788,
0.008086985908448696,
-0.014962909743189812,
0.04387852922081947,
-0.0004... | 0.088908 |
name: csm-ext-secret spec: refreshInterval: 10s secretStoreRef: name: csm kind: SecretStore target: name: my-awesome-secret creationPolicy: Owner data: - secretKey: target\_key remoteRef: key: my\_first\_secret # or you can use the secret.id (e.g. 50000000-4000-3000-2000-100000000001) property: cloudru.secret.key # is ... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/cloudru.md | main | external-secrets | [
-0.05505150929093361,
0.023349372670054436,
-0.034951772540807724,
0.053448326885700226,
0.01922697015106678,
-0.017212849110364914,
0.03591230511665344,
0.04845896735787392,
0.08113238215446472,
0.053385596722364426,
0.07022448629140854,
-0.114031583070755,
0.041236087679862976,
-0.030734... | -0.012475 |
## AWS Authentication ### Controller's Pod Identity  Note: If you are using Parameter Store replace `service: SecretsManager` with `service: ParameterStore` in all examples below. This is basically a zero-configuration authentication... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/aws-access.md | main | external-secrets | [
-0.024052122607827187,
0.03964386507868767,
-0.035123154520988464,
-0.002759370720013976,
-0.010259772650897503,
0.013808811083436012,
0.0275490153580904,
0.020857209339737892,
0.06913773715496063,
0.05535639822483063,
0.010437953285872936,
-0.046401575207710266,
0.08498277515172958,
-0.00... | 0.084667 |
using Terraform [here](https://containscloud.com/2024/03/24/integrating-aws-secrets-manager-to-eks-using-external-secrets/). ## Custom Endpoints You can define custom AWS endpoints if you want to use regional, vpc or custom endpoints. See List of endpoints for [Secrets Manager](https://docs.aws.amazon.com/general/lates... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/aws-access.md | main | external-secrets | [
-0.025385284796357155,
0.0278572179377079,
-0.05179740488529205,
0.04997868463397026,
-0.0120585598051548,
0.016157137230038643,
0.0028904613573104143,
-0.024588633328676224,
0.07054339349269867,
0.08794942498207092,
0.0028182112146168947,
-0.05843295902013779,
0.06789256632328033,
-0.0232... | 0.068281 |
} ``` | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/aws-access.md | main | external-secrets | [
-0.04058453440666199,
0.07735045999288559,
-0.007907853461802006,
-0.004965708591043949,
-0.08357016742229462,
0.014657886698842049,
0.12098146229982376,
0.03659338876605034,
0.04406508058309555,
-0.011904929764568806,
0.07253003865480423,
-0.010240702889859676,
0.0586114376783371,
-0.0140... | 0.176128 |
## Generic Webhook External Secrets Operator can integrate with simple web apis by specifying the endpoint ### Example First, create a SecretStore with a webhook backend. We'll use a static user/password `test`: ```yaml {% raw %} apiVersion: external-secrets.io/v1 kind: SecretStore metadata: name: webhook-backend spec:... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/webhook.md | main | external-secrets | [
-0.1160898208618164,
0.0851995199918747,
-0.09523461014032364,
0.01853214204311371,
-0.021119168028235435,
-0.06030756235122681,
-0.03728935122489929,
0.03334025293588638,
-0.029359200969338417,
0.010344692505896091,
0.012748458422720432,
-0.08080727607011795,
0.0143418675288558,
-0.008929... | 0.021534 |
secret has a `name` property which determines the name of the object in the templating engine. ### All Parameters ```yaml apiVersion: external-secrets.io/v1 kind: ClusterSecretStore metadata: name: statervault spec: provider: webhook: # Url to call. Use templating engine to fill in the request parameters url: # http me... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/webhook.md | main | external-secrets | [
-0.12162091583013535,
0.1170082539319992,
-0.045006245374679565,
0.03927777707576752,
0.035106196999549866,
-0.028924081474542618,
-0.061822935938835144,
0.027822447940707207,
0.06324336677789688,
-0.013076438568532467,
0.008654698729515076,
-0.10161659121513367,
-0.010669179260730743,
-0.... | 0.191346 |
 ## Parameter Store A `ParameterStore` points to AWS SSM Parameter Store in a certain account within a defined region. You should define Roles that define fine-grained access to individual secrets and pass them to ESO using `spec.provider.aws.role`. Th... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/aws-parameter-store.md | main | external-secrets | [
0.0177497286349535,
0.021423591300845146,
-0.07930678874254227,
0.08338481187820435,
0.01021943986415863,
0.01661115512251854,
-0.019177457317709923,
0.02932240627706051,
0.01705237850546837,
0.05951467528939247,
0.038990918546915054,
-0.06206902489066124,
0.11445032060146332,
-0.056193362... | 0.047114 |
`$ID` or `$ARN` (in case a key source is created in another account) as a string, where `alias/aws/ssm` is the \_default\_. This property is only used if `secretType` is set as `SecureString`. - tier & policies contains advanced policy configs such as `ExpirationNotification`. - encodeAsDecoded if set to true will get ... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/aws-parameter-store.md | main | external-secrets | [
-0.040175069123506546,
-0.02718471735715866,
-0.06567937880754471,
0.013958065770566463,
-0.027184344828128815,
0.03127492964267731,
-0.00471052760258317,
-0.06687068939208984,
0.09449493885040283,
0.03365827724337578,
0.0179661363363266,
-0.09586441516876221,
0.06905543804168701,
-0.07011... | 0.022429 |
## ngrok External Secrets Operator integrates with [ngrok](https://ngrok.com/) to sync Kubernetes secrets with [ngrok Secrets for Traffic Policy](https://ngrok.com/blog-post/secrets-for-traffic-policy). Currently, only pushing secrets is supported. ### Configuring ngrok Provider Verify that `ngrok` provider is listed i... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/ngrok.md | main | external-secrets | [
-0.1214267686009407,
-0.05310382694005966,
-0.010177615098655224,
-0.011452075093984604,
-0.07999242842197418,
0.0003709146403707564,
-0.04183947294950485,
0.03149007260799408,
-0.0016755257965996861,
0.06529826670885086,
0.03317353129386902,
-0.0648423284292221,
-0.03969559818506241,
0.01... | 0.068778 |
# Volcengine Provider ## Quick start This guide demonstrates how to use the Volcengine (BytePlus) provider. ### Step 1 Create a secret in the [Volcengine KMS](https://console.volcengine.com/kms). ### Step 2 Create a `SecretStore`. #### Case 1: IRSA is not enabled You need to provide a Kubernetes `Secret` containing the... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/volcengine.md | main | external-secrets | [
-0.07499253004789352,
0.03421299159526825,
-0.03534841164946556,
-0.04160809889435768,
-0.08876047283411026,
0.02635921537876129,
0.0036553330719470978,
0.040109939873218536,
0.04189452528953552,
0.041461821645498276,
0.0237723458558321,
-0.07037840783596039,
-0.021384062245488167,
-0.0185... | 0.096879 |
 ## Doppler SecretOps Platform Sync secrets from the [Doppler SecretOps Platform](https://www.doppler.com/) to Kubernetes using the External Secrets Operator. ## Authentication Doppler supports two authentication methods: > \*\*NOTE:\*\* When ... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/doppler.md | main | external-secrets | [
-0.08386103063821793,
-0.01849289983510971,
0.01001744531095028,
0.010533775202929974,
0.02090897411108017,
-0.06753453612327576,
0.023354392498731613,
0.02653856761753559,
0.09519979357719421,
0.0034074883442372084,
-0.0063089290633797646,
-0.03762917220592499,
0.028799166902899742,
-0.03... | 0.106038 |
We provide a `fake` implementation to help with testing. This provider returns static key/value pairs and nothing else. To use the `fake` provider simply create a `SecretStore` or `ClusterSecretStore` and configure it like in the following example: !!! note inline end The provider returns static data configured in `val... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/fake.md | main | external-secrets | [
-0.06514455378055573,
0.020827950909733772,
-0.01901692897081375,
0.05090521648526192,
-0.007570534944534302,
-0.061396729201078415,
-0.015857968479394913,
0.024833984673023224,
0.01599246822297573,
0.011894900351762772,
0.10326667129993439,
-0.04500363767147064,
0.07182924449443817,
0.001... | 0.069551 |
External Secrets Operator integrates with the [Google Cloud Secret Manager](https://cloud.google.com/secret-manager). ## Authentication The Google Secret Manager provider resolves credentials in this order: static service account JSON (`auth.secretRef`), [GKE Workload Identity](#workload-identity-gke) (`auth.workloadId... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.09090162813663483,
-0.013300659134984016,
0.034302014857530594,
-0.046139638870954514,
-0.0676649883389473,
-0.02835206687450409,
0.04110535979270935,
-0.002893578028306365,
0.023382600396871567,
0.041804179549217224,
-0.02947085350751877,
-0.09225037693977356,
0.029602739959955215,
-0.... | 0.037161 |
a secret `demo-secret`: ```shell gcloud secrets add-iam-policy-binding demo-secret \ --project=$PROJECT\_ID \ --role="roles/secretmanager.secretAccessor" \ --member="principal://iam.googleapis.com/projects/${PROJECT\_NUMBER}/locations/global/workloadIdentityPools/${PROJECT\_ID}.svc.id.goog/subject/ns/${K8S\_NAMESPACE}/... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.044525567442178726,
0.015356957912445068,
0.03042241372168064,
-0.042363252490758896,
-0.05410914495587349,
0.009624036960303783,
0.06660772114992142,
-0.05070884898304939,
0.0751456543803215,
0.09960554540157318,
-0.002692020731046796,
-0.11945698410272598,
0.04918405041098595,
-0.0020... | 0.003425 |
`ExternalSecret` for the `demo-secret` that references this `SecretStore`: ```yaml {% include 'gcpsm-wif-externalsecret.yaml' %} ``` #### Authorizing the Core Controller Pod Instead of managing authentication at the `SecretStore` and `ClusterSecretStore` level, you can give the [Core Controller](../api/components.md) P... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.04824511706829071,
-0.009686645120382309,
-0.0005282049532979727,
-0.010345987044274807,
0.04033656045794487,
-0.0034055926371365786,
0.022808775305747986,
0.0596056804060936,
0.08108261972665787,
0.09815675765275955,
0.011508464813232422,
-0.06728371232748032,
0.026502171531319618,
-0.... | 0.148119 |
the GKE cluster. It is \*\*only\*\* used by \*\*`auth.workloadIdentity`\*\* to build the identity pool and provider URL. When either field is omitted on GKE, the provider can query the [GCP metadata server](https://cloud.google.com/compute/docs/metadata/overview) for the project ID. This field does not apply to `auth.w... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.03956072777509689,
0.04441103711724281,
0.018133804202079773,
0.00828484632074833,
-0.008949275128543377,
-0.018599141389131546,
0.07351765036582947,
-0.06377211213111877,
0.02884499728679657,
0.019453655928373337,
-0.037308987230062485,
-0.11199531704187393,
0.07907500863075256,
-0.028... | 0.044471 |
`spec.provider.gcpsm.auth.workloadIdentityFederation.audience`, optionally appending entries from `serviceAccountRef.audiences`. That token is exchanged at Google STS for a Google access token. Grant access on the secret (or project) to the \*\*federated principal\*\* for that Kubernetes identity: ```shell gcloud secre... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.04839611425995827,
0.011325016617774963,
0.05870356038212776,
-0.027448328211903572,
-0.05605970323085785,
-0.010350239463150501,
0.12063809484243393,
-0.09681563079357147,
0.05951304733753204,
0.06742549687623978,
0.0017389707500115037,
-0.11307547241449356,
0.032876621931791306,
-0.00... | 0.034404 |
put \*\*`aws\_access\_key\_id`\*\*, \*\*`aws\_secret\_access\_key`\*\*, and optionally \*\*`aws\_session\_token`\*\* in a Kubernetes `Secret`, set \*\*`region`\*\*, and reference that secret from `awsSecurityCredentials.awsCredentialsSecretRef` (namespace may be set on `ClusterSecretStore`). On \*\*Amazon EKS\*\*, Goog... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.023198142647743225,
0.04606577381491661,
0.013760410249233246,
0.006838946603238583,
-0.020691342651844025,
0.012346387840807438,
0.09208223223686218,
-0.03855249658226967,
0.07850977033376694,
0.0767991691827774,
-0.018124332651495934,
-0.11841297149658203,
0.0677233338356018,
-0.01255... | 0.088759 |
PushSecret metadata: name: pushsecret-example namespace: default spec: updatePolicy: Replace deletionPolicy: None refreshInterval: 1h0m0s secretStoreRefs: - name: gcp-secretstore kind: SecretStore selector: secret: name: bestpokemon template: data: bestpokemon: "{{ .bestpokemon }}" data: - conversionStrategy: None meta... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.05023643746972084,
-0.06842969357967377,
0.021483125165104866,
-0.03237399831414223,
-0.02474144473671913,
0.020951420068740845,
-0.03924022614955902,
-0.0007733203819952905,
0.042192649096250534,
0.062338702380657196,
0.05636321008205414,
-0.05292293801903725,
0.0016681236447766423,
-0... | 0.02058 |
 ## Hashicorp Vault External Secrets Operator integrates with [HashiCorp Vault](https://www.vaultproject.io/) for secret management. The [KV Secrets Engine](https://www.vaultproject.io/docs/secrets/kv) is the only one supported by this provider. For other secrets eng... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/hashicorp-vault.md | main | external-secrets | [
-0.023246437311172485,
0.03989475592970848,
-0.06250884383916855,
-0.03164185583591461,
-0.027989989146590233,
-0.019236845895648003,
-0.10234123468399048,
0.04546911641955376,
0.00684089632704854,
-0.08694328367710114,
0.045122601091861725,
-0.03800669685006142,
0.07336878031492233,
0.001... | 0.028603 |
``` That results in a secret with these values: ``` bar=mysecret baz=bang ``` #### Getting multiple secrets You can extract multiple secrets from Hashicorp vault by using `dataFrom.Find` Currently, `dataFrom.Find` allows users to fetch secret names that match a given regexp pattern, or fetch secrets whose `custom\_meta... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/hashicorp-vault.md | main | external-secrets | [
-0.053414151072502136,
0.08658817410469055,
-0.024454448372125626,
0.021352756768465042,
0.005078715272247791,
-0.050533898174762726,
-0.021719591692090034,
0.004459581803530455,
0.05762151628732681,
-0.03379802033305168,
0.0426318496465683,
-0.036950379610061646,
0.07012946903705597,
-0.0... | -0.010646 |
to provide `namespace` in `serviceAccountRef` or in `secretRef`, if used. \*\*NOTE:\*\* Starting with Vault 1.20, roles without an audience will trigger warnings during authentication. In Vault 1.21 and later, roles must include an audience or authentication will fail. Update your role definitions to include an audienc... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/hashicorp-vault.md | main | external-secrets | [
0.011501826345920563,
-0.05341041088104248,
-0.028378695249557495,
0.0006706384010612965,
-0.04639419913291931,
-0.014423688873648643,
0.05383619666099548,
-0.04230264946818352,
0.06559620052576065,
-0.02649758569896221,
0.0002755938039626926,
-0.09291972219944,
0.10202416032552719,
0.0208... | 0.022221 |
case of a `ClusterSecretStore`, Be sure to provide `namespace` in `accessKeyIDSecretRef`, `secretAccessKeySecretRef` with the namespaces where the secrets reside. ### EKS Service Account credentials This feature lets you use short-lived service account tokens to authenticate with AWS. You must have [Service Account Vol... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/hashicorp-vault.md | main | external-secrets | [
-0.02067333459854126,
0.02809511497616768,
-0.014728306792676449,
0.009301319718360901,
-0.006014779210090637,
-0.012873123399913311,
0.02274506352841854,
-0.015692394226789474,
0.11103381216526031,
0.0862404853105545,
-0.012869900092482567,
-0.08026201277971268,
0.05253511667251587,
-0.00... | 0.158235 |
before updating - CAS helps prevent conflicts when multiple External Secrets instances manage the same secrets ### Vault Enterprise #### Eventual Consistency and Performance Standby Nodes When using Vault Enterprise with [performance standby nodes](https://www.vaultproject.io/docs/enterprise/consistency#performance-sta... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/hashicorp-vault.md | main | external-secrets | [
-0.003820476122200489,
-0.025351984426379204,
-0.006580613553524017,
-0.04172811657190323,
-0.061383429914712906,
-0.08645232766866684,
-0.09941541403532028,
-0.03440055251121521,
0.048834722489118576,
-0.008388534188270569,
0.03939182683825493,
0.03314734250307083,
0.06934860348701477,
0.... | -0.06691 |
to that returned with the last write. Obviously though, this has a performance hit because the read is blocked until the follower's local state has caught up. #### Forward Inconsistent Vault also supports proxying inconsistent requests to the current cluster leader for immediate read-after-write consistency. Vault 1.10... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/hashicorp-vault.md | main | external-secrets | [
0.05947062745690346,
-0.03154854103922844,
-0.025436975061893463,
0.050754934549331665,
-0.00914963148534298,
-0.08659713715314865,
-0.08665566891431808,
-0.0744512528181076,
0.06109616160392761,
0.004531622864305973,
0.004096484277397394,
0.10546135902404785,
0.07989822328090668,
-0.03555... | -0.057047 |
## Oracle Vault External Secrets Operator integrates with the [Oracle Cloud Infrastructure (OCI) REST API](https://docs.oracle.com/en-us/iaas/api/) to manage secrets in Oracle Vault. All secret operations exposed by External Secrets Operator are supported by the Oracle provider. For more information on managing OCI Vau... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/oracle-vault.md | main | external-secrets | [
-0.08091248571872711,
0.03045564331114292,
-0.05628644675016403,
-0.03588028997182846,
-0.033950939774513245,
-0.07309229671955109,
0.020871879532933235,
0.025722911581397057,
0.046736910939216614,
-0.011195330880582333,
0.02193441241979599,
-0.0034757170360535383,
0.03413587436079979,
0.0... | 0.066687 |
secrets](https://external-secrets.io/latest/guides/getallsecrets/) by tag or regex, only the compartment OCID must be specified. ```yaml {% include 'oracle-secret-store-pushsecret.yaml' %} ``` | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/oracle-vault.md | main | external-secrets | [
-0.0871983990073204,
0.025257280096411705,
-0.02483566291630268,
-0.006193792447447777,
0.030552946031093597,
-0.029730770736932755,
0.06828474253416061,
0.05685565993189812,
0.013216658495366573,
-0.016736140474677086,
0.08432240784168243,
-0.05868016928434372,
0.01707206293940544,
0.0053... | 0.028616 |
## 1Password Secrets with SDK 1Password released [developer SDKs](https://developer.1password.com/docs/sdks/) to ease the usage of the secret provider without the need for any external devices. This provides a much better user experience for automated processes without the need of the connect server. \_Note\_: In order... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/1password-sdk.md | main | external-secrets | [
-0.08490574359893799,
0.015242844820022583,
-0.06739155948162079,
-0.015063416212797165,
-0.01537329237908125,
-0.039435554295778275,
0.043679751455783844,
-0.004350487608462572,
0.06459695845842361,
-0.013331483118236065,
0.05255836248397827,
-0.025076065212488174,
0.09354478865861893,
-0... | 0.103061 |
External Secrets Operator integrates with [Passbolt API](https://www.passbolt.com/) to sync Passbolt to secrets held on the Kubernetes cluster. ### Creating a Passbolt secret store Be sure the `passbolt` provider is listed in the `Kind=SecretStore` and auth and host are set. The API requires a password and private key ... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/passbolt.md | main | external-secrets | [
-0.03787064179778099,
-0.01608324982225895,
0.04584135115146637,
0.008577238768339157,
0.009476680308580399,
-0.020796900615096092,
-0.003543900791555643,
0.026140589267015457,
0.07189575582742691,
0.017303233966231346,
-0.02624991163611412,
-0.07050319015979767,
0.004532787948846817,
0.00... | 0.1075 |
# Delinea Secret-Server/Platform For detailed information about configuring Kubernetes ESO with Secret Server and the Delinea Platform, see the https://docs.delinea.com/online-help/integrations/external-secrets/kubernetes-eso-secret-server.htm ### Creating a SecretStore You need a username, password and a fully qualifi... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/secretserver.md | main | external-secrets | [
-0.05798780918121338,
-0.03800790756940842,
-0.020641056820750237,
-0.09259956330060959,
-0.07898619025945663,
-0.005628624930977821,
0.02610335499048233,
0.01800725609064102,
0.12976372241973877,
0.051242753863334656,
-0.022318782284855843,
-0.0817699059844017,
0.010876324959099293,
-0.07... | 0.0945 |
secrets by ID or Name, the Secret-Server/Platform provider now supports fetching secrets by \*\*path\*\*. This allows you to specify a secret’s folder hierarchy and name in the format: >/FolderName/SecretName #### Example ```yaml apiVersion: external-secrets.io/v1beta1 kind: ExternalSecret metadata: name: secret-server... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/secretserver.md | main | external-secrets | [
-0.0821034237742424,
-0.010413069278001785,
0.02333962358534336,
0.014828262850642204,
-0.012028305791318417,
0.005575359798967838,
0.006253909319639206,
0.02682732418179512,
0.12938465178012848,
0.018327144905924797,
0.020612984895706177,
-0.04967791587114334,
0.005225945729762316,
-0.004... | 0.026158 |
[ { "ItemID": 0, "FieldID": 0, "FileAttachmentID": 0, "FieldName": "Username", "Slug": "username", "FieldDescription": "", "Filename": "", "ItemValue": "usernamevalue", "IsFile": false, "IsNotes": false, "IsPassword": false }, { "ItemID": 0, "FieldID": 0, "FileAttachmentID": 0, "FieldName": "Password", "Slug": "passwor... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/secretserver.md | main | external-secrets | [
-0.040738560259342194,
0.03997734189033508,
-0.05824347585439682,
-0.01260046474635601,
-0.06628585606813431,
-0.0008444933919236064,
-0.007134301587939262,
0.030826322734355927,
0.09717362374067307,
0.060937099158763885,
-0.014822633937001228,
-0.0742008164525032,
0.04966730624437332,
-0.... | 0.05556 |
Server API. #### Updating Existing Secrets When updating an existing secret, you do not strictly need the `folderId` or `secretTemplateId` metadata, as the provider will fetch the existing secret by its name or ID to update the corresponding fields. However, if multiple secrets share the same name across different fold... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/secretserver.md | main | external-secrets | [
-0.11694621294736862,
-0.06388931721448898,
-0.0011817337945103645,
0.028509076684713364,
-0.0028332562651485205,
-0.015864690765738487,
-0.014767751097679138,
-0.029094694182276726,
0.11792510002851486,
-0.0041366578079760075,
0.0688406378030777,
0.038251232355833054,
0.026117250323295593,
... | 0.028741 |
# OpenStack Barbican External Secrets Operator integrates with [OpenStack Barbican](https://docs.openstack.org/barbican/latest/) for secret management. Barbican is OpenStack's Key Manager service that provides secure storage, provisioning and management of secret data. This includes keys, passwords, certificates, and o... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/barbican.md | main | external-secrets | [
-0.006743426900357008,
-0.016418281942605972,
-0.05726850405335426,
0.0014325461816042662,
-0.07047241181135178,
-0.02837510220706463,
0.007018628064543009,
-0.010621536523103714,
0.059087369590997696,
0.038588736206293106,
0.02019454538822174,
-0.10832322388887405,
0.014417069964110851,
-... | 0.034214 |
either as a literal or reference to a Kubernetes secret: | Field | Type | Required | Description | |-------|------|----------|-------------| | `value` | string | No | Literal value (not recommended for sensitive data) | | `secretRef` | SecretKeySelector | No | Reference to a Kubernetes secret | ### BarbicanProviderPass... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/barbican.md | main | external-secrets | [
-0.06944756954908371,
-0.027511052787303925,
-0.029770739376544952,
-0.004231683909893036,
-0.07222668826580048,
0.03125007078051567,
0.046419862657785416,
-0.03752298280596733,
0.07122556865215302,
0.013921785168349743,
0.024503281340003014,
-0.13112621009349823,
0.08256369829177856,
-0.0... | 0.03306 |
## GitLab Variables External Secrets Operator integrates with GitLab to sync [GitLab Project Variables API](https://docs.gitlab.com/ee/api/project\_level\_variables.html) and/or [GitLab Group Variables API](https://docs.gitlab.com/ee/api/group\_level\_variables.html) to secrets held on the Kubernetes cluster. ### Confi... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/gitlab-variables.md | main | external-secrets | [
-0.07571767270565033,
-0.0354902483522892,
-0.002003950532525778,
0.06628520786762238,
-0.07911981642246246,
-0.04381893202662468,
0.012180798687040806,
-0.012773162685334682,
0.07989897578954697,
0.013750996440649033,
-0.020200179889798164,
-0.05165150761604309,
0.08644735813140869,
-0.01... | 0.058988 |
 ## Previder Secret Vault Manager External Secrets Operator integrates with [Previder Secrets Vault](https://vault.previder.io) for secure secret management. ### Authentication We support Access Token authentication using a Secrets Vault ReadWrite or ReadOnly t... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/previder.md | main | external-secrets | [
-0.05124303326010704,
0.020502930507063866,
-0.02131614275276661,
-0.018382349982857704,
-0.007361092139035463,
-0.009890582412481308,
-0.04813012108206749,
0.04080408811569214,
0.0875934362411499,
0.04048881679773331,
0.013143221847712994,
-0.02906690537929535,
0.01069750264286995,
0.0179... | 0.058682 |
 ## Cloak Sync secrets from the [Cloak Encrypted Secrets Platform](https://cloak.software) to Kubernetes using the External Secrets Operator. Cloak uses the webhook provider built into the External Secrets Operator but also required a proxy serv... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/cloak.md | main | external-secrets | [
-0.06053736060857773,
0.07714176177978516,
-0.02374560385942459,
0.012087980285286903,
0.012444738298654556,
-0.04069623351097107,
0.004531500861048698,
-0.0035823064390569925,
0.040560316294431686,
0.0007063740049488842,
0.02058122120797634,
-0.09927541017532349,
0.05442880466580391,
-0.0... | 0.110155 |
## Akeyless Secrets Management Platform External Secrets Operator integrates with the [Akeyless Secrets Management Platform](https://www.akeyless.io/). ### Create Secret Store SecretStore resource specifies how to access Akeyless. This resource is namespaced. \*\*NOTE:\*\* Make sure the Akeyless provider is listed in t... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/akeyless.md | main | external-secrets | [
-0.10358253866434097,
-0.000488156802020967,
-0.03691299632191658,
0.001503564533777535,
-0.0810425728559494,
0.0019145479891449213,
0.03781382367014885,
0.006121672224253416,
0.06669127941131592,
0.025353072211146355,
0.00694845337420702,
-0.01257121842354536,
0.034053005278110504,
-0.025... | 0.091294 |
value `{"cache-pass":"mypassword"}` | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/akeyless.md | main | external-secrets | [
-0.003289619693532586,
0.06804825365543365,
-0.05520779266953468,
-0.0062978737987577915,
-0.07690947502851486,
-0.0465351901948452,
0.07241528481245041,
-0.020514938980340958,
0.016656385734677315,
0.027580924332141876,
-0.06872738152742386,
-0.00687700929120183,
0.02731538750231266,
-0.0... | 0.020699 |
## CyberArk Secrets Manager Provider This section describes how to set up the CyberArk Secrets Manager provider for External Secrets Operator (ESO). For a working example, see the [Accelerator-K8s-External-Secrets repo](https://github.com/conjurdemos/Accelerator-K8s-External-Secrets). ### Prerequisites Before installin... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/conjur.md | main | external-secrets | [
-0.1359560489654541,
-0.01803586259484291,
-0.05695882812142372,
-0.004841904621571302,
-0.05784664675593376,
-0.0679401233792305,
-0.025182431563735008,
0.05154069885611534,
-0.03400499373674393,
-0.007099160924553871,
0.026173939928412437,
-0.057932622730731964,
0.007498173974454403,
0.0... | 0.142916 |
The name of the Secrets Manager account \* `serviceId` - The ID of the JWT Authenticator `WebService` configured in Secrets Manager that is used to authenticate the JWT token You can retrieve the JWT token from either a referenced service account or a Kubernetes secret. For example, to retrieve a JWT token from a refer... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/conjur.md | main | external-secrets | [
-0.07559900730848312,
0.014956430532038212,
0.027452468872070312,
-0.02169845625758171,
-0.004755516070872545,
-0.027616966515779495,
0.057642702013254166,
-0.0064376420341432095,
0.08443368226289749,
-0.010319816879928112,
-0.04082687571644783,
-0.07862426340579987,
0.047211114317178726,
... | 0.080572 |
[Configure Secrets Manager JWT authentication](https://docs.cyberark.com/conjur-open-source/Latest/en/Content/Operations/Services/cjr-authn-jwt-guidelines.htm) ### License Copyright (c) 2023-2024 CyberArk Software Ltd. All rights reserved. Licensed under the Apache License, Version 2.0 (the "License"); you may not use ... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/conjur.md | main | external-secrets | [
-0.17875006794929504,
0.004472642205655575,
-0.051279667764902115,
-0.0920523852109909,
-0.01597430743277073,
-0.035312823951244354,
-0.036850474774837494,
0.00047968648141250014,
-0.009666175581514835,
-0.06413164734840393,
0.05825534090399742,
-0.017894571647047997,
0.018997984007000923,
... | 0.104437 |
## Devolutions Server (DVLS) External Secrets Operator integrates with [Devolutions Server](https://devolutions.net/server/) (DVLS) for secret management. DVLS is a self-hosted privileged access management solution that provides secure password management, role-based access control, and credential injection for teams a... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/devolutions-server.md | main | external-secrets | [
-0.01338160689920187,
0.04267822951078415,
-0.060676608234643936,
-0.07429803907871246,
-0.08567935973405838,
-0.04757644608616829,
0.011339214630424976,
0.00018099079898092896,
0.08999573439359665,
0.016601350158452988,
-0.0467761754989624,
-0.0970359817147255,
0.053903978317976,
-0.00010... | 0.06544 |
| \*\*Azure Service Principal\*\* | Credential | `client-id`, `client-secret`, `tenant-id` | | \*\*Connection String\*\* | Credential | `connection-string` | | \*\*Private Key\*\* | Credential | `username`, `password`, `private-key`, `public-key`, `passphrase` | All entries also include `entry-id` and `entry-name` meta... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/devolutions-server.md | main | external-secrets | [
-0.06486652791500092,
0.03359728306531906,
-0.0694369450211525,
0.0013962583616375923,
-0.06530749052762985,
-0.0029029822908341885,
0.07012930512428284,
-0.04244499281048775,
0.10972976684570312,
0.08492180705070496,
-0.03771921992301941,
-0.06088612973690033,
0.08173096925020218,
-0.0067... | -0.084533 |
## Scaleway Secret Manager External Secrets Operator integrates with [Scaleway's Secret Manager](https://developers.scaleway.com/en/products/secret\_manager/api/v1alpha1/). ### Creating a SecretStore You need an api key (access key + secret key) to authenticate with the secret manager. Both access and secret keys can b... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/scaleway.md | main | external-secrets | [
-0.04819730296730995,
-0.0461166687309742,
-0.005697818472981453,
0.013765565119683743,
-0.05148005858063698,
0.013831368647515774,
-0.023064788430929184,
0.04970748350024223,
0.0631479024887085,
0.036765534430742264,
0.04258817061781883,
-0.08320979028940201,
0.018834182992577553,
0.00253... | 0.055938 |
## Fortanix DSM / SDKMS Populate kubernetes secrets from OPAQUE or SECRET security objects in Fortanix. ### Authentication SDKMS [Application API Key](https://support.fortanix.com/hc/en-us/articles/360015941132-Authentication) ### Creating a SecretStore ```yaml apiVersion: external-secrets.io/v1 kind: SecretStore metad... | https://github.com/external-secrets/external-secrets/blob/main/docs/provider/fortanix.md | main | external-secrets | [
-0.039407748728990555,
-0.02582106739282608,
-0.010955640114843845,
0.03751459717750549,
0.00623296620324254,
-0.01828470453619957,
0.015783945098519325,
0.023730656132102013,
0.04462156072258949,
0.02181491069495678,
0.005955431144684553,
-0.055304136127233505,
-0.01344214379787445,
-0.00... | 0.113935 |
# Decoding Strategies The External Secrets Operator has the feature to allow multiple decoding strategies during an object generation. The `decodingStrategy` field allows the user to set the following Decoding Strategies based on their needs. `decodingStrategy` can be placed under `spec.data.remoteRef`, `spec.dataFrom.... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/decoding-strategy.md | main | external-secrets | [
-0.09202493727207184,
-0.012120874598622322,
-0.06205359473824501,
0.034700486809015274,
0.053079769015312195,
-0.10273438692092896,
-0.0291459858417511,
0.012971686199307442,
0.002168691251426935,
0.036939457058906555,
-0.020509939640760422,
-0.010476484894752502,
0.0052686757408082485,
-... | 0.145633 |
# PushSecret dataTo The `dataTo` field in PushSecret enables bulk pushing of secrets without requiring explicit per-key configuration. Instead of listing every key manually in `data`, you point `dataTo` at a store and optionally filter or transform the keys that get pushed. ## Overview `dataTo` supports two distinct mo... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/pushsecret-datato.md | main | external-secrets | [
-0.04265429452061653,
-0.04442460089921951,
-0.03188866749405861,
0.03663809597492218,
-0.009547840803861618,
-0.06017526984214783,
0.03873017430305481,
0.018272247165441513,
0.0820450484752655,
0.09674306958913803,
0.0753401592373848,
-0.030774254351854324,
0.09713558852672577,
-0.0646169... | -0.014343 |
| Depends | Check your webhook implementation | ## Examples by provider ### AWS Secrets Manager !!! warning "Prefix + remoteKey = concatenated name" The AWS SecretStore `prefix` is \*\*prepended\*\* to every `remoteKey`. If your store has `prefix: myapp/` and your `dataTo` has `remoteKey: db-config`, the resulting AWS ... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/pushsecret-datato.md | main | external-secrets | [
-0.06611832976341248,
0.019412564113736153,
-0.055647265166044235,
0.01277112029492855,
-0.02773476205766201,
-0.07240869849920273,
-0.01732126623392105,
-0.011800577864050865,
0.0546567440032959,
0.08670317381620407,
0.05957949906587601,
-0.08757032454013824,
0.10918643325567245,
-0.12230... | -0.021617 |
.value | upper }}" # db-host → DB-HOST ``` {% endraw %} ### Chained rewrites Multiple rewrites are applied in order — each sees the output of the previous: ```yaml dataTo: - storeRef: name: github-store match: regexp: "^prod-db-" rewrite: - regexp: {source: "^prod-", target: ""} # prod-db-host → db-host - regexp: {sour... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/pushsecret-datato.md | main | external-secrets | [
-0.013762583024799824,
-0.011465766467154026,
0.008884183131158352,
0.014566024765372276,
-0.011128460988402367,
-0.009837918914854527,
-0.00555147510021925,
-0.03203482925891876,
0.04484187811613083,
0.11380745470523834,
0.017014965415000916,
-0.006776384077966213,
0.06353352218866348,
-0... | -0.077262 |
## Background The External Secrets Operator is a Kubernetes Operator that seamlessly incorporates external secret management systems into Kubernetes. This Operator retrieves data from the external API and generates Kubernetes Secret resources using the corresponding secret values. This process occurs continuously in th... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/threat-model.md | main | external-secrets | [
-0.07939690351486206,
0.03923686221241951,
-0.025603897869586945,
-0.016101937741041183,
0.046685248613357544,
-0.031649038195610046,
0.04017738997936249,
-0.006105168256908655,
0.106244295835495,
0.020488157868385315,
0.01301577128469944,
-0.050495974719524384,
0.022176316007971764,
-0.08... | 0.261819 |
to the webhook Pod, they can overload the webhook server and initiate a DoS attack. As a result, modifications to ESO resources may fail, and the ESO core controller may be impacted due to the unavailability of the conversion webhook. #### T03: Unauthorized access to cluster secrets An attacker can gain unauthorized ac... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/threat-model.md | main | external-secrets | [
-0.05408652126789093,
0.0593632347881794,
-0.0227653905749321,
-0.005508530419319868,
0.06207214295864105,
-0.06943707168102264,
0.021034767851233482,
0.017744433134794235,
0.044501569122076035,
0.05994637683033943,
0.010445131920278072,
-0.040510956197977066,
0.04049637168645859,
-0.09098... | 0.281414 |
The specific policies to be enforced depend on the environment. Here are a few suggestions: 1. (Cluster)SecretStore: Restrict the allowed secret providers, disallowing unused or undesired providers (e.g. Webhook). 2. (Cluster)SecretStore: Restrict the permitted authentication mechanisms (e.g. prevent usage of `secretRe... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/threat-model.md | main | external-secrets | [
-0.03292077034711838,
0.044546645134687424,
-0.01911715604364872,
-0.026857204735279083,
0.03140636906027794,
-0.004128616768866777,
-0.00822052638977766,
-0.036217864602804184,
-0.022863587364554405,
0.04443927854299545,
0.0007836852455511689,
-0.08044620603322983,
0.009168602526187897,
-... | 0.205128 |
# All Keys, One Secret To get multiple key-values from an external secret, not having to worry about how many, or what these keys are, we have to use the dataFrom field of the ExternalSecret resource, instead of the data field. We will give an example here with the gcp provider (should work with other providers in the ... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/all-keys-one-secret.md | main | external-secrets | [
-0.08205829560756683,
-0.008914200589060783,
0.03801571950316429,
0.015121657401323318,
-0.00714585417881608,
-0.01865348592400551,
0.08083992451429367,
0.018000485375523567,
0.03013431839644909,
0.01975097507238388,
0.05767908692359924,
-0.06529819220304489,
0.09690964221954346,
-0.026433... | -0.086017 |
Generators allow you to generate values. They are used through a ExternalSecret `spec.DataFrom`. They are referenced from a custom resource using `sourceRef.generatorRef`. If the External Secret should be refreshed via `spec.refreshInterval` the generator produces a map of values with the `generator.spec` as input. The... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/generator.md | main | external-secrets | [
-0.12767261266708374,
0.03861206769943237,
-0.05419516935944557,
0.08529989421367645,
0.0005723165813833475,
-0.039959121495485306,
0.023560067638754845,
-0.013019667007029057,
0.05831443890929222,
-0.012946182861924171,
0.0042348760180175304,
-0.09790930896997452,
0.06840328127145767,
-0.... | 0.069144 |
# Security Best Practices The purpose of this document is to outline a set of best practices for securing the External Secrets Operator (ESO). These practices aim to mitigate the risk of successful attacks against ESO and the Kubernetes cluster it integrates with. ## Security Functions and Features ### 1. Namespace Iso... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/security-best-practices.md | main | external-secrets | [
-0.06415113061666489,
-0.02929798699915409,
-0.04131433367729187,
0.02066008746623993,
0.019405649974942207,
-0.0004985828418284655,
0.04360244795680046,
0.006987522356212139,
0.030993565917015076,
0.0030112331733107567,
0.006801857613027096,
-0.058644071221351624,
0.0371038056910038,
-0.0... | 0.218893 |
chart: \* \*\*Scope RBAC Permissions\*\*: The default chart grants permissions to create service account tokens for any service account. You can disable this by setting `rbac.serviceAccountTokenCreate: false`. When disabled, you must grant ESO token creation for specific ServiceAccounts via dedicated Role/RoleBinding w... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/security-best-practices.md | main | external-secrets | [
0.016882242634892464,
0.056880444288253784,
-0.019672296941280365,
-0.01691427081823349,
0.0035524023696780205,
0.031108560040593147,
0.016252586618065834,
0.02187788300216198,
-0.07081303000450134,
0.035240091383457184,
0.03589252755045891,
-0.029709231108427048,
0.06226804107427597,
0.00... | 0.156695 |
this risk, you can set `rbac.serviceAccountTokenCreate: false` in the Helm chart values. This removes the blanket permission from ESO's Role/ClusterRole entirely. When this permission is disabled, you must explicitly delegate token creation to ESO on a per-ServiceAccount basis. For each ServiceAccount referenced in a S... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/security-best-practices.md | main | external-secrets | [
-0.03555654361844063,
-0.00401590159162879,
-0.03240966796875,
0.031014295294880867,
0.027174731716513634,
0.010724368505179882,
0.033368341624736786,
-0.01352446898818016,
-0.004778692964464426,
0.037638839334249496,
-0.005235765129327774,
-0.02876216545701027,
0.05727774277329445,
0.0470... | 0.124208 |
specific policies for External Secrets Operator (ESO) resources such as SecretStore and ExternalSecret, it is recommended to utilize a policy engine like [Kyverno](http://kyverno.io/) or [OPA Gatekeeper](https://github.com/open-policy-agent/gatekeeper). These policy engines provide a way to define and enforce custom po... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/security-best-practices.md | main | external-secrets | [
-0.033271290361881256,
0.011876480653882027,
0.012320548295974731,
0.017772801220417023,
0.0035378411412239075,
-0.015523041598498821,
0.05440273880958557,
-0.003881834913045168,
-0.033753637224435806,
0.030983541160821915,
0.005524864885956049,
-0.0060800956562161446,
0.024115774780511856,
... | 0.153782 |
}, "optional": { "1.3.6.1.4.1.57264.1.1": "https://token.actions.githubusercontent.com", "1.3.6.1.4.1.57264.1.2": "workflow\_dispatch", "1.3.6.1.4.1.57264.1.3": "a0d2aef2e35c259c9ee75d65f7587e6ed71ef2ad", "1.3.6.1.4.1.57264.1.4": "Create Release", "1.3.6.1.4.1.57264.1.5": "external-secrets/external-secrets", "1.3.6.1.4... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/security-best-practices.md | main | external-secrets | [
-0.08471968024969101,
-0.006066610105335712,
-0.018239842727780342,
0.011705314740538597,
0.05073664337396622,
0.005014472175389528,
0.026598678901791573,
0.02373834140598774,
0.06289391964673996,
0.020196402445435524,
0.06609009951353073,
-0.06607020646333694,
-0.023902274668216705,
0.013... | 0.121683 |
# Fetching information from multiple secrets In some use cases, it might be impractical to bundle all sensitive information into a single secret, or even it is not possible to fully know a given secret name. In such cases, it is possible that a user might need to sync multiple secrets from an external provider into a s... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/getallsecrets.md | main | external-secrets | [
-0.08251642435789108,
0.025293411687016487,
0.0463060699403286,
0.026189805939793587,
-0.045943692326545715,
-0.02341112121939659,
0.016720077022910118,
-0.047555290162563324,
0.11094679683446884,
0.00587824359536171,
0.012634806334972382,
-0.01582896150648594,
0.053219471126794815,
-0.023... | 0.050642 |
# A few common k8s secret types examples Here we will give some examples of how to work with a few common k8s secret types. We will give this examples here with the gcp provider (should work with other providers in the same way). Please also check the guides on [Advanced Templating](templating.md) to understand the det... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/common-k8s-secret-types.md | main | external-secrets | [
-0.0987536758184433,
0.05172717571258545,
0.07325775921344757,
-0.014285164885222912,
-0.03629830852150917,
0.02662549540400505,
0.05219968408346176,
0.01630488783121109,
-0.015369267202913761,
0.04920567199587822,
-0.020886771380901337,
-0.09488516300916672,
0.04372015967965126,
-0.022184... | -0.042859 |
External Secrets Operator provides different modes of operation to fulfill organizational needs. This guide outlines the flexibility of ESO and should give you a first impression of how you can employ this operator in your organization. For a multi-tenant deployment you should first examine your organizational structur... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/multi-tenancy.md | main | external-secrets | [
-0.015743067488074303,
-0.027930613607168198,
-0.010584323666989803,
-0.007584545761346817,
-0.053584024310112,
-0.024380797520279884,
0.023125674575567245,
-0.025270698592066765,
0.05975163355469704,
0.017843279987573624,
-0.01218346506357193,
-0.06576001644134521,
0.05546566843986511,
-0... | 0.136325 |
Contrary to what `ExternalSecret` does by pulling secrets from secret providers and creating `kind=Secret` in your cluster, `PushSecret` reads a local `kind=Secret` and pushes its content to a secret provider. The update behavior of `PushSecret` is controlled by `spec.updatePolicy`. The default policy is `Replace`, suc... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/pushsecrets.md | main | external-secrets | [
-0.0937834158539772,
-0.04664010554552078,
0.013233327306807041,
0.050961971282958984,
0.018891775980591774,
-0.03524467349052429,
0.04044267162680626,
0.005663218442350626,
0.026661165058612823,
0.021625038236379623,
0.06087304651737213,
-0.029401656240224838,
0.021966900676488876,
-0.035... | 0.017562 |
# Guides The following guides demonstrate use-cases and provide examples of how to use the API. Please pick one of the following guides: \* [Multi-Tenancy Design Considerations](multi-tenancy.md) \* [Find multiple secrets & Extract Secret values](getallsecrets.md) \* [Advanced Templating](templating.md) \* [Targeting C... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/introduction.md | main | external-secrets | [
-0.00009131057595368475,
0.033954281359910965,
-0.08692086488008499,
-0.04766193777322769,
0.025578292086720467,
-0.04180567339062691,
-0.04430156573653221,
0.01737564615905285,
-0.018193909898400307,
0.06366671621799469,
0.03388887271285057,
0.0027469350025057793,
0.13164153695106506,
-0.... | 0.001716 |
# Advanced Templating v1 !!! warning Templating Engine v1 is \*\*deprecated\*\* and will be removed in the future. Please migrate to engine v2 and take a look at our [upgrade guide](templating.md#migrating-from-v1) for changes. !!! note Templating Engine v1 does NOT support templating the `spec.target.template.metadata... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/templating-v1.md | main | external-secrets | [
-0.05117591470479965,
0.13296222686767578,
-0.02128717303276062,
0.03125239536166191,
0.007541590835899115,
0.028300510719418526,
0.035563986748456955,
0.049981776624917984,
-0.04918743669986725,
-0.06676949560642242,
0.05044948309659958,
-0.06956613063812256,
-0.02067110501229763,
-0.0025... | 0.041336 |
# Upgrading CRD versions From version v0.5.0, `v1alpha1` version is deprecated, and `v1beta1` is in place. This guide will cover the main differences between the two versions, and a procedure on how to safely upgrade it. ## Differences between versions Versions v1alpha1 and v1beta1 are fully-compatible for SecretStores... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/v1beta1.md | main | external-secrets | [
-0.0961495190858841,
0.004387669265270233,
0.03303522989153862,
-0.00831935741007328,
0.04582257941365242,
-0.010231352411210537,
-0.04281163960695267,
0.008248867467045784,
0.04128387197852135,
0.035465795546770096,
0.05256389454007149,
-0.05802526697516441,
0.022943168878555298,
-0.09388... | 0.053628 |
# AI Agent Guide: External Secrets Operator Setup AI agents: walk the user through each decision below before generating manifests. All decisions apply across providers and platforms. ## Decision Flow Ask these three questions in order. Each answer narrows the setup. \*\*1. "How many teams share this cluster?"\*\* - Mu... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/ai-setup-guide.md | main | external-secrets | [
-0.0412997230887413,
-0.03342042863368988,
-0.07042774558067322,
0.0021229730919003487,
0.04378923401236534,
0.002276618964970112,
-0.016996746882796288,
-0.0015468907076865435,
0.059955477714538574,
0.027019472792744637,
-0.009578525088727474,
-0.05778402090072632,
0.08431392908096313,
-0... | 0.12035 |
target: name: data: - secretKey: remoteRef: key: property: # omit if the secret is a plain string ``` ## How the Sync Loop Works The controller polls the external provider on the `refreshInterval` cadence and writes the result to the target K8s Secret. `refreshInterval: 1h` polls once per hour. `refreshInterval: 0` dis... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/ai-setup-guide.md | main | external-secrets | [
-0.045513805001974106,
-0.017447607591748238,
-0.017336660996079445,
0.03582801669836044,
0.015457476489245892,
0.022123103961348534,
-0.012491020374000072,
0.0027905970346182585,
0.0931684747338295,
0.03609506040811539,
0.04384445399045944,
-0.08509155362844467,
0.04570057988166809,
-0.12... | 0.107997 |
# Advanced Templating v2 With External Secrets Operator you can transform the data from the external secret provider before it is stored as `Kind=Secret`. You can do this with the `Spec.Target.Template`. Each data value is interpreted as a [Go template](https://golang.org/pkg/text/template/). Please note that referenci... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/templating.md | main | external-secrets | [
-0.03322519734501839,
0.12331589311361313,
0.005042236763983965,
0.03241507709026337,
0.0013043511426076293,
0.02424582839012146,
0.0370212160050869,
0.0779142752289772,
0.002954239258542657,
-0.010204663500189781,
0.018027285113930702,
-0.08808352798223495,
0.005212180782109499,
0.0135685... | -0.014346 |
JWK looks similar to this: ```json { "kty": "RSA", "kid": "cc34c0a0-bd5a-4a3c-a50d-a2a7db7643df", "use": "sig", "n": "pjdss...", "e": "AQAB" // ... } ``` And what you want may be a PEM-encoded public or private key portion of it. Take a look at this example on how to transform it into the desired format: ```yaml {% inc... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/templating.md | main | external-secrets | [
-0.09714951366186142,
0.13393709063529968,
-0.012326138094067574,
-0.02070070058107376,
-0.005149811040610075,
-0.02889103814959526,
-0.022974327206611633,
0.029846927151083946,
0.036763593554496765,
-0.012398087419569492,
0.013777327723801136,
-0.07332706451416016,
0.04673963040113449,
0.... | -0.046332 |
match the ciphertext, decryption will fail and reconciliation will retry. ## Templating with PushSecret `PushSecret` templating is much like `ExternalSecrets` templating. In-fact under the hood, it's using the same data structure. Which means, anything described in the above should be possible with push secret as well ... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/templating.md | main | external-secrets | [
-0.1428259313106537,
0.01408830750733614,
0.029388615861535072,
0.014802152290940285,
0.010900428518652916,
-0.04822825640439987,
-0.0064248088747262955,
0.021400311961770058,
0.030505497008562088,
-0.02737819217145443,
0.04057871922850609,
-0.044456835836172104,
-0.008413145318627357,
0.0... | -0.004123 |
you are still using `v1alpha1`, You have to opt-in to use the new engine version by specifying `template.engineVersion=v2`: ```yaml apiVersion: external-secrets.io/v1alpha1 kind: ExternalSecret metadata: name: secret spec: # ... target: template: engineVersion: v2 # ... ``` The biggest change was that basically all fun... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/templating.md | main | external-secrets | [
-0.02477640099823475,
0.027075573801994324,
0.030042309314012527,
-0.0061784833669662476,
0.02091803587973118,
0.009786865673959255,
-0.04630470648407936,
0.05971556529402733,
-0.0022337704431265593,
-0.044337198138237,
-0.012411732226610184,
-0.058870356529951096,
-0.09575996547937393,
-0... | -0.017123 |
You can test a feature that was not yet released using the following methods, use them at your own discretion: ### Helm 1. Create a `values.yaml` file with the following content: ```yaml replicaCount: 1 image: repository: ghcr.io/external-secrets/external-secrets pullPolicy: IfNotPresent # -- The image tag to use. The ... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/using-latest-image.md | main | external-secrets | [
-0.03685936704277992,
0.03472455218434334,
0.050463657826185226,
-0.03630765900015831,
0.048805031925439835,
-0.056963153183460236,
-0.11860793083906174,
0.02718427963554859,
0.034950755536556244,
0.03899887204170227,
0.02535879984498024,
-0.10879666358232498,
0.025560854002833366,
-0.0222... | 0.021945 |
# Using the esoctl tool The tool can be found under `cmd/esoctl`. ## Debugging templates The `template` command can be used to test templates for `PushSecret` and `ExternalSecret`. To run render simply execute `make build` in the `cmd/esoctl` folder. This will result in a binary under `cmd/esoctl/bin`. Once the build s... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/using-esoctl-tool.md | main | external-secrets | [
-0.11002561450004578,
-0.014819213189184666,
0.005214882083237171,
0.01795327290892601,
0.058521393686532974,
-0.060160212218761444,
-0.043161265552043915,
0.0478096641600132,
0.0052874889224767685,
0.005984734743833542,
0.035555336624383926,
-0.11394529044628143,
-0.024008870124816895,
-0... | 0.039354 |
GrafanaSpec \*GrafanaSpec `json:"grafanaSpec,omitempty"` MFASpec \*MFASpec `json:"mfaSpec,omitempty"` + MyAwesomeGeneratorSpec \*MyAwesomeGeneratorSpec `json:"myawesomegeneratorSpec,omitempty"` } // ClusterGenerator represents a cluster-wide generator which can be referenced as part of `generatorRef` fields. diff --git... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/using-esoctl-tool.md | main | external-secrets | [
-0.16615106165409088,
0.03637252748012543,
-0.08366533368825912,
0.016604870557785034,
0.03148878365755081,
-0.039433322846889496,
-0.03262367099523544,
0.005203960929065943,
-0.009096469730138779,
-0.05895347520709038,
0.086549773812294,
-0.07202927768230438,
-0.017822787165641785,
-0.030... | 0.14147 |
# Targeting Custom Resources !!! warning "Maturity" At the time of this writing (1.11.2025) this feature is in heavy alpha status. Please consider the following documentation with the limitations and guardrails described below. External Secrets Operator can create and manage resources beyond Kubernetes Secrets. When yo... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/targeting-custom-resources.md | main | external-secrets | [
-0.01492279302328825,
0.028787866234779358,
0.035351190716028214,
0.00982317328453064,
0.012105297297239304,
0.006830370519310236,
0.08313523977994919,
0.01651371829211712,
0.07243131846189499,
0.022160544991493225,
-0.02686925418674946,
-0.08120685815811157,
0.05984262004494667,
0.0241363... | 0.094883 |
resources using the template metadata: ```yaml {% include 'manifest-labeled-configmap.yaml' %} ``` The operator automatically adds the `externalsecrets.external-secrets.io/managed: "true"` label to track which resources it manages. ## RBAC Requirements When using custom resource targets, ensure the External Secrets Ope... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/targeting-custom-resources.md | main | external-secrets | [
-0.03395914286375046,
-0.02221611887216568,
-0.04626108333468437,
0.022790832445025444,
0.06799434870481491,
-0.019227074459195137,
0.014159864746034145,
0.01046162098646164,
0.019639289006590843,
0.042542532086372375,
0.013049387373030186,
-0.031988296657800674,
0.06363702565431595,
0.028... | 0.092247 |
# Rewriting Keys in DataFrom When calling out an ExternalSecret with `dataFrom.extract` or `dataFrom.find`, it is possible that you end up with a kubernetes secret that has conflicts in the key names, or that you simply want to remove a common path from the secret keys. In order to do so, it is possible to define a set... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/datafrom-rewrite.md | main | external-secrets | [
-0.05582069978117943,
0.06751065701246262,
0.06354149430990219,
-0.004706914070993662,
-0.02888891100883484,
-0.0021781031973659992,
-0.0064198230393230915,
-0.013299594633281231,
0.09988755732774734,
0.04777894169092178,
-0.02368718944489956,
-0.0601404570043087,
0.0013494588201865554,
-0... | 0.055691 |
key collisions The following ExternalSecret: ```yaml {% include 'datafrom-rewrite-conflict.yaml' %} ``` Will allow two secrets with the same JSON keys to be imported into a Kubernetes Secret without any conflict. In this example, if we had the following secrets available in the provider: ```json { "my-secrets-dev": { "... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/datafrom-rewrite.md | main | external-secrets | [
-0.0759800523519516,
0.008679581806063652,
0.07164355367422104,
-0.03402112424373627,
0.0038227990735322237,
-0.0356874018907547,
-0.008656799793243408,
-0.01718919165432453,
0.1065601333975792,
-0.011030670255422592,
0.07238984107971191,
0.0002076178352581337,
0.06641492247581482,
-0.0322... | -0.002929 |
# Deploying without ClusterSecretStore and ClusterExternalSecret and ClusterPushSecret When deploying External Secrets Operator via Helm chart, the default configuration will install `ClusterSecretStore` and `ClusterExternalSecret` and other CRDs and these objects will be processed by the operator. In order to disable ... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/disable-cluster-features.md | main | external-secrets | [
0.019442280754446983,
0.032564856112003326,
-0.016533100977540016,
-0.011170887388288975,
-0.0043472908437252045,
0.007092128042131662,
-0.052902646362781525,
-0.0029823249205946922,
0.009599518030881882,
0.04392059147357941,
0.04228374734520912,
-0.08573656529188156,
0.034748125821352005,
... | 0.028596 |
# Lifecycle The External Secrets Operator manages the lifecycle of secrets in Kubernetes. With `refreshPolicy`, `creationPolicy` and `deletionPolicy` you get fine-grained control of its lifecycle. !!! note "Creation/Deletion Policy Combinations" Some combinations of creationPolicy/deletionPolicy are not allowed as they... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/ownership-deletion-policy.md | main | external-secrets | [
-0.10323890298604965,
-0.038789935410022736,
0.007998289540410042,
0.034368306398391724,
-0.02309594675898552,
-0.008767814375460148,
0.013595635071396828,
-0.05874668061733246,
0.1575581580400467,
0.05457814037799835,
0.03962429240345955,
-0.018775928765535355,
-0.012220178730785847,
-0.0... | 0.108919 |
gets deleted on the provider side and is not accessible anymore this is not considered an error and the ExternalSecret does not go into SecretSyncedError status. | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/ownership-deletion-policy.md | main | external-secrets | [
-0.10841391235589981,
-0.03966769948601723,
-0.009345016442239285,
0.034779373556375504,
0.03590823709964752,
-0.019081033766269684,
-0.006020188797265291,
-0.0010104426182806492,
0.0759778693318367,
-0.01628516986966133,
0.0596928708255291,
0.02247176133096218,
0.016338838264346123,
0.028... | -0.001968 |
# Controller Classes > NOTE: this feature is experimental and not highly tested Controller classes are a property set during the deployment that allows multiple controllers to work in a group of workload. It works by separating which secretStores are going to be attributed to which controller. For the behavior of a sin... | https://github.com/external-secrets/external-secrets/blob/main/docs/guides/controller-class.md | main | external-secrets | [
-0.06891808658838272,
-0.00835566595196724,
-0.07319000363349915,
0.008814138360321522,
-0.004199496004730463,
0.010613062418997288,
-0.019337086006999016,
0.03158828616142273,
0.018945515155792236,
0.035804059356451035,
0.1039736345410347,
0.005192471668124199,
0.02719465270638466,
-0.033... | -0.049336 |
# GitOps using FluxCD (v2) FluxCD is a GitOps operator for Kubernetes. It synchronizes the status of the cluster from manifests allocated in different repositories (Git or Helm). This approach fits perfectly with External Secrets on clusters which are dynamically created, to get credentials with no manual intervention ... | https://github.com/external-secrets/external-secrets/blob/main/docs/examples/gitops-using-fluxcd.md | main | external-secrets | [
-0.10338130593299866,
-0.0016231279587373137,
0.015734359622001648,
-0.012828071601688862,
-0.01887749508023262,
-0.016463421285152435,
0.03313407674431801,
0.03823968395590782,
0.09692852199077606,
0.07324283570051193,
-0.03332572430372238,
-0.07186610996723175,
0.07930687069892883,
-0.03... | 0.246485 |
the CRDs As mentioned, CRDs can be deployed using the official Helm package, but to solve the race condition, they will be deployed from our git repository using a Kustomization manifest called `deployment-crds.yaml` as follows: ```yaml {% include 'gitops/deployment-crds.yaml' %} ``` ## Deploy the operator The operator... | https://github.com/external-secrets/external-secrets/blob/main/docs/examples/gitops-using-fluxcd.md | main | external-secrets | [
-0.01650422066450119,
0.003662011818960309,
0.015796344727277756,
-0.10072272270917892,
-0.003900666953995824,
-0.015397122129797935,
-0.02658027596771717,
0.004133619833737612,
-0.00879777129739523,
0.025509459897875786,
0.03940870985388756,
-0.05780963972210884,
0.026063309982419014,
-0.... | 0.042931 |
# PushSecret dataTo Examples This page provides practical examples of using the `dataTo` field in PushSecret to bulk-push secrets to external providers. ## Prerequisites Before using these examples, ensure you have: - External Secrets Operator installed in your cluster - A configured SecretStore (or ClusterSecretStore)... | https://github.com/external-secrets/external-secrets/blob/main/docs/examples/pushsecret-datato.md | main | external-secrets | [
-0.032853469252586365,
-0.06357535719871521,
-0.01332934107631445,
0.007702367380261421,
-0.07361236214637756,
-0.043476663529872894,
0.00249661598354578,
0.03398958966135979,
0.05213015526533127,
0.07070227712392807,
0.01838735304772854,
-0.10315482318401337,
0.03580111637711525,
-0.04827... | 0.047168 |
aws-secrets-manager selector: secret: name: legacy-secrets dataTo: - storeRef: name: aws-secrets-manager rewrite: # First: Remove "old-" prefix - regexp: source: "^old-" target: "" # Second: Add "migrated/" prefix - regexp: source: "^" target: "migrated/" # Third: Replace hyphens with slashes for hierarchy - regexp: so... | https://github.com/external-secrets/external-secrets/blob/main/docs/examples/pushsecret-datato.md | main | external-secrets | [
-0.04284822940826416,
0.02156827040016651,
-0.008542784489691257,
0.006337922997772694,
0.029638970270752907,
-0.031002767384052277,
-0.009137595072388649,
-0.046894412487745285,
0.049245115369558334,
0.09219615161418915,
0.03778022900223732,
-0.07134056836366653,
0.046934787184000015,
-0.... | 0.001137 |
yaml ``` Look for the `status.conditions` field for error messages. ### View Synced Secrets ```bash kubectl get pushsecret -n -o jsonpath='{.status.syncedPushSecrets}' | jq ``` ### Common Issues \*\*1. No keys matched:\*\* - Verify the source Secret has keys matching your pattern - Check regexp syntax: `kubectl get sec... | https://github.com/external-secrets/external-secrets/blob/main/docs/examples/pushsecret-datato.md | main | external-secrets | [
-0.03643941879272461,
0.003467195201665163,
0.07278814166784286,
-0.014994549565017223,
-0.057448405772447586,
-0.0010270250495523214,
-0.03769996017217636,
-0.06338605284690857,
0.10921332985162735,
0.0333443209528923,
0.012170742265880108,
-0.08480484038591385,
0.028660176321864128,
-0.0... | -0.002433 |
# Bitwarden support using webhook provider Bitwarden is an integrated open source password management solution for individuals, teams, and business organizations. !!! note This documentation is for Bitwarden \*\*Password Manager\*\*. It is different from [Bitwarden Secrets Manager](https://bitwarden.com/products/secret... | https://github.com/external-secrets/external-secrets/blob/main/docs/examples/bitwarden.md | main | external-secrets | [
-0.11878269910812378,
-0.021242793649435043,
-0.08167585730552673,
-0.004855410195887089,
-0.02029346115887165,
-0.04624081403017044,
-0.012000108137726784,
-0.022515572607517242,
-0.01292773149907589,
-0.004443629179149866,
0.02198396436870098,
-0.03786301240324974,
0.0793280154466629,
-0... | 0.098724 |
and `keyFingerprint` ```yaml {% include 'bitwarden-secret.yaml' %} ``` | https://github.com/external-secrets/external-secrets/blob/main/docs/examples/bitwarden.md | main | external-secrets | [
-0.07012051343917847,
-0.0195145346224308,
-0.02231195569038391,
-0.029435699805617332,
0.0023495901841670275,
-0.03511476889252663,
-0.00004263906157575548,
-0.03196074441075325,
-0.0211604293435812,
-0.008370337076485157,
0.17412349581718445,
0.06392808258533478,
0.03832481801509857,
-0.... | 0.023133 |
# Getting started Jenkins is one of the most popular automation servers for continuous integration, automation, scheduling jobs and for generic pipelining. It has an extensive set of plugins that extend or provide additional functionality including the [kubernetes credentials plugin](https://github.com/jenkinsci/kubern... | https://github.com/external-secrets/external-secrets/blob/main/docs/examples/jenkins-kubernetes-credentials.md | main | external-secrets | [
-0.09600162506103516,
0.0088399238884449,
-0.03862336277961731,
0.00283878855407238,
-0.061161063611507416,
-0.010111343115568161,
-0.01859411969780922,
0.006311197765171528,
0.08240161091089249,
0.012483594007790089,
-0.050676602870225906,
-0.040607478469610214,
0.04445735365152359,
-0.00... | 0.176633 |
# Getting started \*\*Anchore Engine\*\* is an open-source platform that provides centralized inspection, analysis, and certification of container images. When integrated with Kubernetes, it adds powerful features—such as preventing unscanned images from being deployed into your clusters. ## Installation with Helm Ther... | https://github.com/external-secrets/external-secrets/blob/main/docs/examples/anchore-engine-credentials.md | main | external-secrets | [
0.013270695693790913,
0.024704722687602043,
-0.026935985311865807,
-0.00665806932374835,
0.02026652917265892,
-0.020822737365961075,
0.0067910607904195786,
-0.005450442899018526,
0.07631642371416092,
0.033382244408130646,
-0.022134961560368538,
-0.06583283841609955,
0.07414171099662781,
-0... | 0.02651 |
 The `PushSecret` is namespaced and it describes what data should be pushed to the secret provider. \* tells the operator what secrets should be pushed by using `spec.selector`. \* you can specify what secret keys should be pushed by using `spec.data`. \* you can ... | https://github.com/external-secrets/external-secrets/blob/main/docs/api/pushsecret.md | main | external-secrets | [
-0.048868559300899506,
0.02576608397066593,
0.022253388538956642,
0.03481804579496384,
-0.021031489595770836,
-0.0128431161865592,
0.008054204285144806,
0.07414033263921738,
-0.012989646755158901,
-0.011569651775062084,
0.057193342596292496,
-0.05589451640844345,
0.011826186440885067,
0.02... | 0.031438 |
`"None"` - `"None"`: No conversion - `"ReverseUnicode"`: Reverse Unicode escape sequences in key names (useful when paired with ExternalSecret's `Unicode` strategy) ```yaml dataTo: - storeRef: name: my-store conversionStrategy: ReverseUnicode ``` ### Combining dataTo with data You can use both `dataTo` and `data` field... | https://github.com/external-secrets/external-secrets/blob/main/docs/api/pushsecret.md | main | external-secrets | [
-0.03589623048901558,
0.0019324111053720117,
-0.030669623985886574,
-0.003056020475924015,
-0.08362340927124023,
-0.05299147590994835,
0.005639649927616119,
-0.061753157526254654,
0.039623044431209564,
0.06243917718529701,
0.06385963410139084,
-0.05349494144320488,
0.05083027482032776,
-0.... | -0.020028 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.