content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
# Deprecation Policy We follow the [Kubernetes Deprecation Policy](https://kubernetes.io/docs/reference/using-api/deprecation-policy/) and [API Versioning Scheme](https://kubernetes.io/docs/reference/using-api/#api-versioning): alpha, beta, GA. The project is currently in `beta` state. Please try the `beta` features an... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/deprecation-policy.md | main | external-secrets | [
-0.022169293835759163,
0.01354540977627039,
0.1131000965833664,
-0.0058677708730101585,
0.07713443040847778,
0.017214030027389526,
-0.036013051867485046,
-0.02834372967481613,
0.006841755006462336,
0.05408463627099991,
0.019393887370824814,
0.018651533871889114,
-0.04753972217440605,
-0.00... | 0.196313 |
# Glossary This glossary includes technologies related to ESO in alphabetic order. Cluster ### What is it? A group of nodes (computers, VMs) that execute workloads in Kubernetes, i.e., run containerized applications. It's a technique that groups multiple computational resources into a single logical unit. These resourc... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/glossary.md | main | external-secrets | [
0.04628754407167435,
-0.03280586749315262,
-0.014451618306338787,
-0.0018649930134415627,
0.03099668025970459,
-0.0072251721285283566,
-0.007002305705100298,
0.011675468645989895,
0.0759003609418869,
0.026420021429657936,
-0.028251538053154945,
0.029664836823940277,
0.03631114587187767,
-0... | 0.423915 |
is it? Horizontal Pod Autoscaler (HPA) ### What is it for? It's used to control the number of Pods in a Deployment. For example, if CPU usage is too high, the HPA would increase the number of Pods. It's also possible to use the Vertical Pod Autoscaler (VPA), which would increase the amount of resources for each Pod ins... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/glossary.md | main | external-secrets | [
-0.06946133077144623,
0.03224426880478859,
-0.00013508423580788076,
-0.013379480689764023,
-0.03842006251215935,
-0.039482783526182175,
0.021842580288648605,
0.0315442755818367,
0.08114051073789597,
0.014343658462166786,
0.003614584682509303,
0.012342164292931557,
-0.013745082542300224,
-0... | 0.380463 |
issues, and non-compliance with best coding practices. ### What is it for? Ensures code quality, consistency, and adherence to predefined standards by identifying syntax errors, formatting issues, and poor development practices before code execution. It contributes to maintaining clean, readable, and efficient code. ##... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/glossary.md | main | external-secrets | [
-0.01607329212129116,
0.007381360977888107,
0.04361141473054886,
0.030584657564759254,
0.09058807045221329,
-0.03232666105031967,
0.01446865126490593,
0.036327704787254333,
0.010457862168550491,
0.056471243500709534,
-0.0032021731603890657,
-0.031288910657167435,
-0.004257902503013611,
-0.... | 0.339338 |
This page lists the status, timeline and policy for currently supported ESO releases and its providers. Please also see our [deprecation policy](deprecation-policy.md) that describes API versioning, deprecation and API surface. ## Supported Versions external-secrets only supports the most-up-to date, current minor vers... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/stability-support.md | main | external-secrets | [
-0.003565395949408412,
0.005528130102902651,
0.14129675924777985,
-0.05065451189875603,
0.06680000573396683,
-0.01009245403110981,
-0.10568500310182571,
-0.023206371814012527,
0.000011606467523961328,
0.04446614906191826,
0.016935955733060837,
0.023579277098178864,
-0.06883227080106735,
-0... | 0.143503 |
would give to major version upgrades in other projects. ## Provider Stability and Support Level The following table describes the stability level of each provider and who's responsible. | Provider | Stability | Maintainer | | -------- | --------: | -----------------------------------------------------------------------... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/stability-support.md | main | external-secrets | [
0.006768994964659214,
-0.05696292966604233,
-0.006283899769186974,
-0.07004579156637192,
-0.012407279573380947,
-0.03389129042625427,
-0.08359639346599579,
0.01198820024728775,
-0.08190174400806427,
-0.00973279308527708,
0.02054930478334427,
0.03808661177754402,
-0.013598483055830002,
-0.0... | 0.033271 |
| Akeyless | x | x | | x | x | x | x | | 1Password | x | x | | | x | x | x | | 1Password SDK | | | | | x | x | x | | Generic Webhook | | | | | | | x | | senhasegura DSM | | | | | x | | | | Doppler | x | | | | x | | | | Keeper Security | x | | | | x | x | | | Scaleway | x | x | | | x | x | x | | CyberArk Secrets Manager... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/stability-support.md | main | external-secrets | [
-0.04385252296924591,
-0.09933847188949585,
-0.03433100879192352,
-0.0436483770608902,
-0.02187585085630417,
-0.039435409009456635,
0.09330836683511734,
0.034699697047472,
-0.10180793702602386,
0.04235202819108963,
0.0886513888835907,
-0.05376254394650459,
0.10334821045398712,
-0.065557204... | 0.138935 |
## Can I manually trigger a secret refresh? You can trigger a secret refresh by using kubectl or any other kubernetes api client. You just need to change an annotation, label or the spec of the resource: ``` kubectl annotate es my-es force-sync=$(date +%s) --overwrite ``` For ClusterExternalSecrets you can refresh all ... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/faq.md | main | external-secrets | [
-0.05313458293676376,
-0.055223360657691956,
0.04533347859978676,
0.05228922516107559,
0.05432824790477753,
-0.005619162693619728,
-0.006309513933956623,
-0.019057629629969597,
0.12174852192401886,
0.04251386597752571,
-0.0085624223574996,
-0.07570774108171463,
0.0075674885883927345,
-0.05... | 0.089722 |
them, some of them will require manual intervention. We recommend to first convert the manifest files, and actually see if the tool provides a warning about any file needed to be changed. Beware that the tool points the SecretStores to use KES Service Account, so you'll also need to tweak that if you plan to uninstall ... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/faq.md | main | external-secrets | [
-0.10018251091241837,
0.001780047663487494,
0.06286212056875229,
-0.09681985527276993,
0.02405523508787155,
-0.03916117548942566,
-0.06045374646782875,
-0.040879495441913605,
-0.032452791929244995,
-0.014721914194524288,
0.07001941651105881,
0.01980571821331978,
-0.05462425574660301,
-0.05... | 0.047408 |
# Prerequisites To collaborate on the External Secrets Operator (ESO) project, you need to install some tools on your computer. This guide explains what each tool is, why it is needed, the recommended version, and how to install it on the corresponding operating system. ### Supported Operating Systems To collaborate on... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/prerequisites.md | main | external-secrets | [
-0.04992774873971939,
-0.042092204093933105,
-0.036258306354284286,
-0.015582124702632427,
-0.030164411291480064,
-0.005303134210407734,
-0.0016229922184720635,
0.07616834342479706,
-0.019279152154922485,
0.00466943858191371,
-0.012868348509073257,
-0.031098905950784683,
-0.04860251769423485... | 0.20509 |
jq 1.6 or later. ### How to Install jq Please consult the [official jq website](https://stedolan.github.io/jq/). ## Kubernetes About Kubernetes ### What is Kubernetes? Kubernetes is an open-source platform for automating the deployment, scaling, and management of containerized applications. It orchestrates containerize... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/prerequisites.md | main | external-secrets | [
-0.046763788908720016,
0.012914067134261131,
0.04889989644289017,
-0.008331387303769588,
-0.0471530482172966,
0.0008317333995364606,
-0.0028082779608666897,
0.004031077492982149,
0.03865019604563713,
0.025586603209376335,
-0.06069182604551315,
-0.01080020796507597,
0.011390908621251583,
-0... | 0.185782 |
containers as cluster nodes. How to Create a Kind Cluster with Local Registry ### 1. Create a local container registry: ``` docker run -d --restart=always -p "5000:5000" --name kind-registry registry:2 ``` ### 2. Create a Kind cluster using ctlptl and connect it to the local registry: ``` ctlptl create cluster kind --r... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/prerequisites.md | main | external-secrets | [
-0.03995060548186302,
-0.003108871867880225,
0.008858665823936462,
0.005695858970284462,
-0.04129447415471077,
0.027413632720708847,
-0.04272511228919029,
-0.003461971413344145,
0.01885705627501011,
0.035897642374038696,
0.012000848539173603,
-0.09242428094148636,
0.0026202548760920763,
-0... | 0.167466 |
# Getting started External-secrets runs within your Kubernetes cluster as a deployment resource. It utilizes CustomResourceDefinitions to configure access to secret providers through SecretStore resources and manages Kubernetes secret resources with ExternalSecret resources. This tutorial is intended for those who alre... | https://github.com/external-secrets/external-secrets/blob/main//docs/introduction/getting-started.md | main | external-secrets | [
-0.04635072499513626,
-0.00835708063095808,
0.04735825955867767,
-0.03689902648329735,
0.005501993931829929,
0.03627384826540947,
-0.029243750497698784,
0.0718458741903305,
0.0879848375916481,
0.08296714723110199,
0.004616211634129286,
-0.05627285689115524,
0.011281391605734825,
-0.0079417... | 0.053273 |
 Sync secrets from [Infisical](https://www.infisical.com) to your Kubernetes cluster using External Secrets Operator. ## Authentication In order for the operator to fetch secrets from Infisical, it needs to first authenticate with Infisical. To authenti... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/infisical.md | main | external-secrets | [
-0.06735307723283768,
0.023447999730706215,
0.01417854055762291,
-0.013474026694893837,
-0.051217515021562576,
0.013831336982548237,
0.05084001645445824,
-0.005193114746361971,
0.06723260134458542,
0.027195008471608162,
0.005869791842997074,
-0.07565247267484665,
0.043353237211704254,
-0.0... | 0.129323 |
 ## Azure Key vault External Secrets Operator integrates with [Azure Key vault](https://azure.microsoft.com/en-us/services/key-vault/) for secrets, certificates and Keys management. ### Authentication We support authentication with Microsoft Entra identities that can be used... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/azure-key-vault.md | main | external-secrets | [
-0.0706653743982315,
0.022059183567762375,
-0.05037364363670349,
0.007158383727073669,
-0.016472293063998222,
0.028732065111398697,
0.026635771617293358,
-0.022702498361468315,
0.0908353179693222,
0.11006741225719452,
0.028468063101172447,
0.004302352666854858,
0.05055522918701172,
0.04233... | 0.069591 |
secret store or reference a correctly configured one the ability to read secrets. \*\*This approach is usually not recommended\*\*. But may make sense when you want to share an identity with multiple namespaces. Also see our [Multi-Tenancy Guide](../guides/multi-tenancy.md) for design considerations. ```yaml {% include... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/azure-key-vault.md | main | external-secrets | [
-0.07703962922096252,
0.01995917037129402,
-0.10050699859857559,
0.011244785971939564,
-0.06133579462766647,
0.02852027676999569,
0.10782676190137863,
-0.05133524164557457,
0.10119541734457016,
0.10910617560148239,
0.04352430999279022,
-0.032012924551963806,
0.14577294886112213,
0.05001136... | -0.059757 |
include 'azkv-secret-store.yaml' %} ``` \*\*NOTE:\*\* In case of a `ClusterSecretStore`, Be sure to provide `namespace` in `clientId` and `clientSecret` with the namespaces where the secrets reside. Or in case of Managed Identity authentication: ```yaml {% include 'azkv-secret-store-mi.yaml' %} ``` ### Object Types Azu... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/azure-key-vault.md | main | external-secrets | [
0.0014617692213505507,
0.0660601481795311,
-0.08267350494861603,
0.06352327764034271,
-0.04674793779850006,
-0.0014704713830724359,
0.036658406257629395,
-0.021761111915111542,
0.09576508402824402,
0.08203010261058807,
0.02441767044365406,
-0.03611115366220474,
0.1282832771539688,
0.053058... | -0.057047 |
External Secrets Operator allows to retrieve secrets from a Kubernetes Cluster - this can be either a remote cluster or the local one where the operator runs in. A `SecretStore` points to a \*\*specific namespace\*\* in the target Kubernetes Cluster. You are able to retrieve all secrets from that particular namespace g... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/kubernetes.md | main | external-secrets | [
-0.06885337829589844,
-0.043289557099342346,
-0.01768486388027668,
0.04933002218604088,
-0.0441657230257988,
-0.010231790132820606,
-0.0023912324104458094,
-0.015762168914079666,
0.06500045210123062,
0.023094553500413895,
-0.013814860954880714,
-0.05480925366282463,
0.011878905817866325,
-... | 0.086687 |
- create ``` #### Authenticating with BearerToken Create a Kubernetes secret with a client token. There are many ways to acquire such a token, please refer to the [Kubernetes Authentication docs](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#authentication-strategies). ```yaml apiVersion: v1 k... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/kubernetes.md | main | external-secrets | [
-0.06713758409023285,
0.011916385032236576,
0.014421731233596802,
0.03266393020749092,
-0.06302456557750702,
0.025616375729441643,
0.013376273214817047,
0.0650775358080864,
0.07853546738624573,
0.06088196486234665,
-0.02789853699505329,
-0.053898125886917114,
0.012919844128191471,
-0.00682... | 0.078638 |
type: ConfigMap name: kube-root-ca.crt key: ca.crt auth: token: bearerToken: name: eso-token key: token --- apiVersion: external-secrets.io/v1 kind: ExternalSecret metadata: name: eso-kubernetes-secret namespace: target-namespace spec: secretStoreRef: kind: SecretStore name: kubernetes-secret-store target: name: eso-ku... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/kubernetes.md | main | external-secrets | [
-0.03584316000342369,
-0.06284230202436447,
0.00864290352910757,
0.0021499863360077143,
-0.007576370146125555,
-0.01543426513671875,
0.012535491026937962,
0.06473403424024582,
0.0831756666302681,
0.04478985443711281,
-0.014773494563996792,
-0.12306486815214157,
0.019662700593471527,
0.0003... | 0.143643 |
or Replace targetMergePolicy: Merge # or Replace / Ignore labels: color: red annotations: yes: please ``` | Field | Type | Description | |-------------------|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/kubernetes.md | main | external-secrets | [
0.008132651448249817,
0.054942697286605835,
0.05757516250014305,
0.03457856550812721,
0.05357111617922783,
0.06253889948129654,
0.058291174471378326,
-0.007685644552111626,
0.03288649395108223,
-0.07981129735708237,
0.004614124074578285,
-0.07277259230613708,
0.004300317727029324,
-0.04551... | 0.04572 |
## 1Password Secrets Automation External Secrets Operator integrates with [1Password Secrets Automation](https://1password.com/products/secrets/) for secret management. ## Deprecation Consider using [1Password SDK provider](1password-sdk.md) instead. It uses an official [SDK for 1Password](https://developer.1password.c... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/1password-automation.md | main | external-secrets | [
-0.0755777657032013,
-0.026843765750527382,
-0.043943166732788086,
-0.004476873204112053,
-0.018223753198981285,
-0.05097762122750282,
0.057092513889074326,
0.022681832313537598,
0.009405103512108326,
0.009774381294846535,
-0.016818447038531303,
-0.017442626878619194,
0.11969989538192749,
... | 0.041076 |
in the [Setup Authentication section](#setup-authentication). \* The Service's name will be referenced in SecretStores/ClusterSecretStores. \* Keep in mind the likely need for additional Connect Servers for other Automation Environments when naming objects. For example dev, staging, prod, etc. \* Unencrypted secret val... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/1password-automation.md | main | external-secrets | [
-0.04140621796250343,
-0.08559355139732361,
-0.07969137281179428,
0.013811795972287655,
-0.075495146214962,
0.04469800740480423,
0.011757912114262581,
0.049377184361219406,
0.02168622426688671,
0.06343697756528854,
-0.029233794659376144,
-0.050543371587991714,
0.10927042365074158,
0.024858... | -0.015373 |
for Kubernetes secrets mounted as files, and Password type Items for ones that will be mounted as environment variables, but either can be used for either. It comes down to what's more convenient. #### Why no version history \* 1Password only supports version history on their in-built `password` field. Therefore, imple... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/1password-automation.md | main | external-secrets | [
-0.03180506452918053,
-0.009912161156535149,
0.037695951759815216,
-0.04893830791115761,
-0.0034191750455647707,
0.029376164078712463,
-0.010690410621464252,
-0.028003353625535965,
0.0749083012342453,
0.06656251847743988,
-0.022940294817090034,
-0.014799945056438446,
0.057658515870571136,
... | 0.041598 |
## Delinea DevOps Secrets Vault External Secrets Operator integrates with [Delinea DevOps Secrets Vault](https://docs.delinea.com/online-help/products/devops-secrets-vault/current). Please note that the [Delinea Secret Server](https://delinea.com/products/secret-server) product is NOT in scope of this integration. ### ... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/delinea.md | main | external-secrets | [
-0.08284635841846466,
-0.0024864685256034136,
-0.014854981563985348,
-0.08940016478300095,
-0.05173962563276291,
-0.038678739219903946,
0.020661290735006332,
0.019587237387895584,
0.11356710642576218,
-0.00341240712441504,
-0.014973463490605354,
-0.0450739748775959,
-0.0038672725204378366,
... | 0.055385 |
## Segura® DevOps Secret Manager (DSM) External Secrets Operator integrates with [Segura®](https://segura.security/) [DevOps Secret Manager (DSM)](https://segura.security/solutions/devops) module to sync application secrets to secrets held on the Kubernetes cluster. --- ## Authentication Authentication in Segura® uses ... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/senhasegura-dsm.md | main | external-secrets | [
-0.037672821432352066,
-0.038214363157749176,
0.01433279737830162,
0.008637812919914722,
-0.056875597685575485,
-0.047682251781225204,
0.04519873857498169,
0.04734080657362938,
0.025617294013500214,
0.02303505688905716,
0.02514064498245716,
-0.07931522279977798,
0.018084444105625153,
-0.04... | 0.162069 |
 ## Secrets Manager A `SecretStore` points to AWS Secrets Manager 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`. This way users of the `SecretStore... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/aws-secrets-manager.md | main | external-secrets | [
-0.027845771983265877,
0.033523354679346085,
-0.05987091362476349,
0.09046535938978195,
0.003230765461921692,
0.006919530685991049,
0.003979536704719067,
0.012466062791645527,
0.0009667305275797844,
0.06635331362485886,
0.038231298327445984,
-0.07069113850593567,
0.0958627238869667,
-0.060... | 0.025647 |
contains the policy JSON. ##### Resource Policy Example To attach a resource policy to a secret for cross-account access: ```yaml apiVersion: external-secrets.io/v1alpha1 kind: PushSecret metadata: name: pushsecret-example namespace: default spec: refreshInterval: 10s secretStoreRefs: - name: aws-secretsmanager kind: S... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/aws-secrets-manager.md | main | external-secrets | [
-0.09445792436599731,
0.007050322834402323,
-0.017458811402320862,
-0.01530523132532835,
0.05151822790503502,
-0.002581218956038356,
0.00411268463358283,
-0.011584462597966194,
-0.01686668023467064,
0.050448156893253326,
0.04718947038054466,
-0.09424975514411926,
0.03503613546490669,
0.007... | 0.016675 |
## IBM Cloud Secret Manager External Secrets Operator integrates with [IBM Cloud Secret Manager](https://www.ibm.com/cloud/secrets-manager) for secret management. ### Authentication We support API key and trusted profile container authentication for this provider. #### API key secret To generate your key (for test purp... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/ibm-secrets-manager.md | main | external-secrets | [
-0.10496079176664352,
-0.021415406838059425,
-0.05027516186237335,
0.015432669781148434,
0.006258158478885889,
0.03540951758623123,
0.0372772254049778,
0.033873554319143295,
0.05562114343047142,
0.05051269754767418,
0.1108584776520729,
-0.0724378377199173,
0.12426752597093582,
-0.061435017... | 0.053364 |
the secrets manager secret and sets appropriate key:value pairs in the resulting Kubernetes secret #### iam\_credentials \* `remoteRef` retrieves an apikey from secrets manager and sets it for specified `secretKey` \* `dataFrom` retrieves an apikey from secrets manager and sets it for the `apikey` Kubernetes secret key... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/ibm-secrets-manager.md | main | external-secrets | [
0.00875694677233696,
0.047382596880197525,
0.0072655887342989445,
-0.021652594208717346,
-0.06301132589578629,
0.03925880044698715,
0.040582478046417236,
0.009480208158493042,
0.07061868160963058,
0.04952184483408928,
0.0208783857524395,
-0.12459735572338104,
0.09398005157709122,
-0.040067... | 0.046145 |
kubernetes secret from the IBM Secrets Manager, a `Kind=ExternalSecret` is needed. Below example creates a kubernetes secret based on ID of the secret in Secrets Manager. ```yaml {% include 'ibm-external-secret.yaml' %} ``` Alternatively, the secret name along with its secret group name can be specified instead of secr... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/ibm-secrets-manager.md | main | external-secrets | [
-0.0803440660238266,
0.01970668137073517,
-0.014286374673247337,
0.008655918762087822,
0.014430503360927105,
-0.019894946366548538,
0.02813873067498207,
0.013585737906396389,
0.08763694018125534,
0.01568370684981346,
0.03858171030879021,
-0.07162515074014664,
0.017285533249378204,
-0.02104... | 0.133299 |
## Yandex Lockbox External Secrets Operator integrates with [Yandex Lockbox](https://cloud.yandex.com/docs/lockbox/) for secret management. ### Prerequisites \* [External Secrets Operator installed](../introduction/getting-started.md#installing-with-helm) \* [Yandex.Cloud CLI installed](https://cloud.yandex.com/docs/cl... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/yandex-lockbox.md | main | external-secrets | [
-0.08954530954360962,
-0.022168954834342003,
0.004121060948818922,
-0.02688216231763363,
0.012476843781769276,
0.030789967626333237,
0.0854262113571167,
-0.0355699248611927,
0.06588698923587799,
0.0545533187687397,
0.03675497695803642,
-0.009218528866767883,
0.06395365297794342,
-0.0112322... | 0.06569 |
## BeyondTrust Password Safe External Secrets Operator integrates with [BeyondTrust Password Safe](https://www.beyondtrust.com/docs/beyondinsight-password-safe/). Warning: The External Secrets Operator secure usage involves taking several measures. Please see [Security Best Practices](https://external-secrets.io/latest... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/beyondtrust.md | main | external-secrets | [
-0.07760142534971237,
-0.04165288060903549,
-0.0011533289216458797,
-0.018799006938934326,
0.05323919281363487,
-0.002391805173829198,
0.026801088824868202,
0.01909460686147213,
0.07293709367513657,
0.0024367792066186666,
0.010411811992526054,
-0.022778956219553947,
0.07248464226722717,
-0... | 0.056342 |
ClusterSecretStore The following example demonstrates how to create a `ClusterSecretStore` configured to use the BeyondTrust provider. ```sh kubectl apply -f beyondtrust-cluster-secret-store.yml ``` ```yaml {% include 'beyondtrust-cluster-secret-store.yaml' %} ``` ### Creating an PushSecret The example below demonstrat... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/beyondtrust.md | main | external-secrets | [
-0.024575429037213326,
-0.04547726735472679,
-0.017934557050466537,
0.003892507404088974,
-0.0015003924490883946,
-0.024019956588745117,
-0.009266907349228859,
0.03924517333507538,
0.035938672721385956,
0.043319638818502426,
0.0702376663684845,
-0.10722742229700089,
0.07226760685443878,
-0... | 0.098959 |
## Pulumi ESC Sync environments, configs and secrets from [Pulumi ESC](https://www.pulumi.com/product/esc/) to Kubernetes using the External Secrets Operator.  More information about setting up [Pulumi](https://www.pulumi.com/) ESC can be found in the [Pulumi ESC documentation](... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/pulumi.md | main | external-secrets | [
-0.0814611166715622,
-0.06986810266971588,
-0.06360509991645813,
-0.03393648937344551,
-0.0528143085539341,
-0.025745032355189323,
0.028397098183631897,
-0.04223966598510742,
0.05382751300930977,
0.008991464041173458,
0.04793263599276543,
-0.06600897014141083,
0.02863665297627449,
-0.03943... | 0.157096 |
## Chef `Chef External Secrets provider` will enable users to seamlessly integrate their Chef-based secret management with Kubernetes through the existing External Secrets framework. In many enterprises, legacy applications and infrastructure are still tightly integrated with the Chef/Chef Infra Server/Chef Server Clus... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/chef.md | main | external-secrets | [
-0.047125060111284256,
0.010388706810772419,
-0.039461683481931686,
-0.0010877575259655714,
-0.010455641895532608,
-0.02162804827094078,
-0.006404178217053413,
-0.029617058113217354,
0.08033169060945511,
-0.055552855134010315,
0.04024598002433777,
-0.020540326833724976,
-0.004620484076440334... | 0.134918 |
using the private key and will fetch the data bags contained in the `vivid-credentials` secret resource. To get all data items inside the data bag, you can use the `dataFrom` directive: ```yaml apiVersion: external-secrets.io/v1 kind: ExternalSecret metadata: name: vivid-external-secrets # name of ExternalSecret namesp... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/chef.md | main | external-secrets | [
-0.037642333656549454,
0.026075249537825584,
-0.025927148759365082,
0.03652413561940193,
0.046988192945718765,
-0.05507352948188782,
0.057781919836997986,
0.023768335580825806,
0.10121019929647446,
0.013123824261128902,
0.02616208977997303,
-0.09414629638195038,
0.02014879696071148,
-0.062... | 0.068238 |
 ## Onboardbase Secret Management Sync secrets from [Onboardbase](https://www.onboardbase.com/) to Kubernetes using the External Secrets Operator. ## Authentication ### Get an Onboardbase [API Key](https://docs.onboardbase.com/reference/api-a... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/onboardbase.md | main | external-secrets | [
-0.01961020566523075,
-0.00941306073218584,
-0.005392199847847223,
0.009211182594299316,
-0.011245613917708397,
0.0269631315022707,
-0.010946777649223804,
0.01660677045583725,
0.059068381786346436,
0.050945721566677094,
-0.022387666627764702,
-0.07860779762268066,
0.0633552074432373,
-0.02... | 0.070063 |
## Keeper Security External Secrets Operator integrates with [Keeper Security](https://www.keepersecurity.com/) for secret management by using [Keeper Secrets Manager](https://docs.keeper.io/secrets-manager/secrets-manager/about). ## Authentication ### Secrets Manager Configuration (SMC) KSM can authenticate using \*On... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/keeper-security.md | main | external-secrets | [
-0.05971168726682663,
-0.03849296271800995,
-0.025375038385391235,
0.005971087608486414,
-0.04157554730772972,
0.0006513898260891438,
-0.008734483271837234,
0.05052917078137398,
0.034575484693050385,
0.046353526413440704,
0.0196861419826746,
-0.06066087260842323,
0.04178581386804581,
-0.02... | 0.063028 |
one key per secret at the moment \* If the record with the selected name exists but the key does not exist, the record cannot be updated. See [Ability to add custom fields to existing secret #17](https://github.com/Keeper-Security/secrets-manager-go/issues/17) | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/keeper-security.md | main | external-secrets | [
-0.06596271693706512,
0.029747378081083298,
-0.0889921486377716,
0.013121269643306732,
-0.034937430173158646,
0.012397238984704018,
0.041990406811237335,
-0.03122984617948532,
0.05610930547118187,
0.015709184110164642,
0.07746098190546036,
-0.050947364419698715,
0.08492936939001083,
-0.069... | 0.018512 |
## GitHub External Secrets Operator integrates with GitHub to sync Kubernetes secrets with [GitHub Actions secrets](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions). ### Limitations The GitHub provider is \*\*write-only\*\*, designed specifically to \*\*create and update\*\* GitHub Ac... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/github.md | main | external-secrets | [
-0.061393190175294876,
-0.043312039226293564,
0.006266511511057615,
0.009973578155040741,
-0.02515273541212082,
-0.006276286207139492,
-0.01859757862985134,
0.012595762498676777,
0.08209152519702911,
0.05096891522407532,
0.015462450683116913,
-0.04605972766876221,
0.045438822358846664,
-0.... | 0.149339 |
## 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 |
!!! warning "Provider Deprecated" This provider is deprecated due to lack of maintenance and licensing issues. It will be removed on the next minor release. ## Alibaba Cloud Secrets Manager External Secrets Operator integrates with [Alibaba Cloud Key Management Service](https://www.alibabacloud.com/help/en/key-manageme... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/alibaba.md | main | external-secrets | [
-0.025745121762156487,
0.0050721378065645695,
-0.027391355484724045,
0.005461610853672028,
-0.06543879210948944,
0.043670762330293655,
0.017070572823286057,
0.008534416556358337,
0.0754476860165596,
0.060050979256629944,
0.0020001535303890705,
0.01485644280910492,
0.057010237127542496,
-0.... | 0.099092 |
## 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 |
## 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 ### Workload Identity Federation Through [Workload Identity Federation](https://cloud.google.com/kubernetes-engine/docs/concepts/workload-identity) (WIF), platforms that support worklo... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.09301887452602386,
-0.03972078487277031,
0.039403077214956284,
-0.026899415999650955,
-0.02102467603981495,
-0.0018435263773426414,
0.058501917868852615,
-0.0050478302873671055,
0.04591688513755798,
0.0532807782292366,
-0.018175706267356873,
-0.05336311087012291,
0.009181443601846695,
-... | 0.115465 |
for the `demo-secret` that references this `SecretStore`: ```yaml {% include 'gcpsm-wif-externalsecret.yaml' %} ``` \_Note the above secretStore example uses GCP native Workload Identity. The implementation for WorkloadIdentityFederation is defined in the [WorkloadIdentityFederation API spec](https://external-secrets.i... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.10876372456550598,
-0.01976299285888672,
0.02488240972161293,
0.020549587905406952,
-0.015287394635379314,
-0.0009620905620977283,
0.04678301140666008,
0.01342186238616705,
0.04040513560175896,
0.0409119687974453,
0.0361848920583725,
-0.04701049625873566,
0.019881054759025574,
0.0038968... | 0.126609 |
To verify this (or to determine the service account's name in a different setup), you can run: ```shell kubectl get pods --namespace external-secrets \ --selector app.kubernetes.io/name=external-secrets \ --output jsonpath='{.items[0].spec.serviceAccountName}' ``` Use WIF to grant this Kubernetes service account access... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.07297834008932114,
-0.013880869373679161,
0.031781766563653946,
-0.026555189862847328,
-0.02318844385445118,
-0.012958737090229988,
0.0719248428940773,
-0.031281907111406326,
0.0568583607673645,
0.06735798716545105,
0.009037111885845661,
-0.11455003172159195,
0.02580307237803936,
-0.017... | 0.083075 |
add the label `"managed-by": "external-secrets"`. By default, the PushSecret spec will replace any existing labels on the existing GCP Secret Manager Secret. To prevent this, a new field was added to the `spec.data.metadata` object called `mergePolicy` which defaults to `Replace` to ensure that there are no breaking ch... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.09350186586380005,
-0.06376907974481583,
0.0071620037779212,
0.02028101682662964,
-0.03461147099733353,
0.028493717312812805,
0.031960636377334595,
0.0011368653504177928,
-0.0019907793030142784,
0.0075239273719489574,
0.0719418078660965,
-0.040352948009967804,
0.003670112229883671,
-0.0... | -0.004767 |
or the specific `secretmanager.versions.list` permission in addition to the standard `secretmanager.secretAccessor` role. ``` | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/google-secrets-manager.md | main | external-secrets | [
-0.03463947772979736,
-0.008543566800653934,
-0.05339377000927925,
-0.0033926137257367373,
0.06944441050291061,
-0.028677726164460182,
-0.026958921924233437,
-0.04114098101854324,
-0.08240120112895966,
0.0013644715072587132,
0.08274531364440918,
0.01960197649896145,
-0.022574884817004204,
... | 0.015226 |
 ## 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 |
{% include 'vault-iam-store-sa.yaml' %} ``` Reference the service account from above in the Secret Store: ```yaml {% include 'vault-iam-store.yaml' %} ``` ### Controller's Pod Identity This is basically a zero-configuration authentication approach that inherits the credentials from the controller's pod identity. This a... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/hashicorp-vault.md | main | external-secrets | [
-0.06385571509599686,
0.04305260255932808,
-0.05119612067937851,
-0.014236505143344402,
0.02034110203385353,
0.007544263266026974,
0.08323191106319427,
-0.02051582559943199,
0.09696315973997116,
0.05540226027369499,
0.07747992128133774,
-0.030521491542458534,
0.07770787179470062,
-0.027581... | 0.10238 |
need to review them and pick the best fit for your environment and Vault configuration. #### Vault Namespaces [Vault namespaces](https://www.vaultproject.io/docs/enterprise/namespaces) are an enterprise feature that support multi-tenancy. You can specify a vault namespace using the `namespace` property when you define ... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/hashicorp-vault.md | main | external-secrets | [
-0.004629550501704216,
-0.03693104535341263,
-0.07179690152406693,
-0.03044935315847397,
-0.03866133466362953,
-0.0848216637969017,
-0.06460315734148026,
0.008431206457316875,
0.042362697422504425,
-0.02005649358034134,
0.024921651929616928,
-0.030164644122123718,
0.06134829670190811,
0.04... | -0.074158 |
## 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 [Device42 API](https://api.device42.com/#!/Passwords/getPassword) to sync Device42 secrets into a Kubernetes cluster. ### Authentication `username` and `password` is required to talk to the Device42 API. ```yaml apiVersion: v1 kind: Secret metadata: name: device42-credentials d... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/device42.md | main | external-secrets | [
-0.034178685396909714,
-0.03003661520779133,
0.024146882817149162,
-0.026406720280647278,
-0.02791726589202881,
-0.029032131657004356,
-0.022164108231663704,
0.015051514841616154,
0.08269298076629639,
0.04888752102851868,
0.022246992215514183,
-0.032294075936079025,
0.024213502183556557,
0... | 0.073976 |
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.060316476970911026,
-0.01775216870009899,
0.028053315356373787,
0.04651091992855072,
-0.021641220897436142,
0.0019114650785923004,
-0.0005195630947127938,
0.018203632906079292,
0.07537677884101868,
0.035195492208004,
-0.015726085752248764,
-0.07864141464233398,
0.011559274047613144,
-0.... | 0.053203 |
# 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 |
omit it to retrieve the entire secret. ### Preparing your secret You can either retrieve your entire secret or you can use a JSON formatted string stored in your secret located at Items[0].ItemValue to retrieve a specific value. See example JSON secret below. #### Examples Using the json formatted secret below: - Looku... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/secretserver.md | main | external-secrets | [
-0.09044697880744934,
0.06847245991230011,
-0.035051681101322174,
0.055238377302885056,
-0.012738277204334736,
-0.02393144555389881,
0.037039048969745636,
-0.014271377585828304,
0.05757113918662071,
-0.015919791534543037,
0.03341086953878403,
-0.024130748584866524,
0.03625589609146118,
-0.... | -0.104597 |
# 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 |
Ensure the application has the necessary permissions in DVLS 3. Check that the DVLS server URL is accessible from your Kubernetes cluster ### Entry Not Found If an entry cannot be found: 1. Verify the vault UUID and entry UUID are correct 2. Ensure the application has at least read access to the vault 3. Check that the... | https://github.com/external-secrets/external-secrets/blob/main//docs/provider/devolutions-server.md | main | external-secrets | [
0.04059154912829399,
-0.017781861126422882,
-0.0106728570535779,
-0.08385089039802551,
-0.04060849919915199,
-0.05602486804127693,
-0.08475140482187271,
-0.050249237567186356,
0.14883746206760406,
0.015788359567523003,
-0.05511965975165367,
-0.10666946321725845,
0.001616648631170392,
0.019... | -0.032962 |
## 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 |
## 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 restrict this by modifying the `ClusterRole` to only allow token creation for specific, known service accounts. This limits the operator's ability to impersonate other service... | https://github.com/external-secrets/external-secrets/blob/main//docs/guides/security-best-practices.md | main | external-secrets | [
-0.0031196349300444126,
0.03355879709124565,
-0.02601366676390171,
-0.02743404731154442,
-0.006963450461626053,
0.036407217383384705,
0.03170398622751236,
0.010816005989909172,
-0.014417765662074089,
0.043427444994449615,
0.033867232501506805,
-0.046051740646362305,
0.05603819712996483,
0.... | 0.163144 |
align with changes in your network infrastructure and security requirements. It is the responsibility of the user to define and configure Network Policies tailored to their specific environment and security needs. By implementing proper network restrictions, you can enhance the overall security posture of the External ... | https://github.com/external-secrets/external-secrets/blob/main//docs/guides/security-best-practices.md | main | external-secrets | [
0.0025879524182528257,
0.048806287348270416,
0.009743132628500462,
-0.020731188356876373,
-0.02687777206301689,
0.015565209090709686,
0.00043891099630855024,
0.003945521079003811,
0.059530116617679596,
0.05175177752971649,
-0.01389328483492136,
-0.08065427839756012,
0.02927004173398018,
-0... | 0.151234 |
following policy validates the usage of the `provider` field in the SecretStore manifest. ```yaml {% filter indent(width=4) %} {% include 'kyverno-policy-secretstore.yaml' %} {% endfilter %} ``` ## Regular Patches To maintain a secure environment, it is crucial to regularly patch and update all software components of E... | https://github.com/external-secrets/external-secrets/blob/main//docs/guides/security-best-practices.md | main | external-secrets | [
-0.05924610793590546,
-0.0036906644236296415,
0.02523808740079403,
-0.039585985243320465,
0.01954251527786255,
-0.02551608718931675,
-0.019179893657565117,
-0.00819464772939682,
-0.057139378041028976,
0.040542423725128174,
0.028059562668204308,
0.027080271393060684,
-0.015693064779043198,
... | 0.158049 |
GitHub Workflow SHA: a0d2aef2e35c259c9ee75d65f7587e6ed71ef2ad GitHub Workflow Name: Create Release GitHub Workflow Trigger external-secrets/external-secrets GitHub Workflow Ref: refs/heads/main { "\_type": "https://in-toto.io/Statement/v0.1", "predicateType": "https://slsa.dev/provenance/v0.2", "subject": [ { "name": "... | https://github.com/external-secrets/external-secrets/blob/main//docs/guides/security-best-practices.md | main | external-secrets | [
-0.06501075625419617,
0.008695757016539574,
-0.025677187368273735,
0.011486348696053028,
0.07107241451740265,
-0.05461229383945465,
-0.008580377325415611,
-0.003731258912011981,
0.07927687466144562,
0.026285294443368912,
0.0323069803416729,
-0.08309555798768997,
0.0043799844570457935,
0.02... | 0.106841 |
# 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.