content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 50
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
containers: ```yaml --- apiVersion: apps/v1 kind: Deployment metadata: labels: k8s-app: kube-dns annotations: kustomize.toolkit.fluxcd.io/prune: disabled kustomize.toolkit.fluxcd.io/ssa: merge name: coredns namespace: kube-system spec: replicas: 5 selector: matchLabels: eks.amazonaws.com/component: coredns k8s-app: kub... | https://github.com/fluxcd/website/blob/main/content/en/flux/faq.md | main | fluxcd | [
-0.04186396673321724,
0.02891434356570244,
0.007114885840564966,
-0.022654151543974876,
0.006477781571447849,
-0.008569019846618176,
-0.036218296736478806,
-0.0541144534945488,
0.07294392585754395,
0.01748604141175747,
0.008402237668633461,
-0.09366050362586975,
-0.013959747739136219,
-0.0... | 0.19197 |
features in the [migration FAQ](../migration/faq-migration/). ### How can I migrate from v1 to v2? The Flux community has created guides and example repositories to help you migrate to Flux v2: - [Migrate from Flux v1](/flux/migration/flux-v1-migration/) - [Migrate from `.flux.yaml` and kustomize](/flux/migration/flux-... | https://github.com/fluxcd/website/blob/main/content/en/flux/faq.md | main | fluxcd | [
0.023234616965055466,
-0.061889734119176865,
0.004054575692862272,
-0.03378986567258835,
0.08157740533351898,
0.0072724223136901855,
-0.04533318057656288,
-0.001722286338917911,
-0.034495774656534195,
-0.00924745760858059,
0.0406373031437397,
-0.10672925412654877,
0.021173009648919106,
0.0... | 0.107869 |
{{% alert color="warning" title="Disclaimer" %}} Note that this guide has not been updated since more than a year ago. It does not address `OCIRepository`, needs review in consideration of Flux v2.0.0, and likely needs to be refreshed. Expect this doc to receive an overhaul soon. {{% /alert %}} Below we describe the fl... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.04921239987015724,
0.034247759729623795,
0.03968718647956848,
0.07492897659540176,
0.14364543557167053,
-0.06922823190689087,
0.011677443981170654,
0.051416680216789246,
-0.003643026342615485,
-0.013452938757836819,
-0.028532596305012703,
-0.07160857319831848,
0.08115269988775253,
0.006... | 0.200779 |
a Custom Resource Definition (CRD) type for defining Custom Resources to be implemented by a controller. In Flux, examples include: `GitRepository`, `Bucket`, `HelmRepository`, `Kustomization`, `HelmRelease`, `Alert`, and others. \* \*\*Field\*\* - YAML resources are collections of data fields, which can be nested to c... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.09958327561616898,
0.0008337282342836261,
0.011319035664200783,
-0.012459802441298962,
0.012099816463887691,
-0.01675131358206272,
0.04821871593594551,
0.034778445959091187,
0.09954828023910522,
0.018269432708621025,
-0.01756751909852028,
-0.05652666836977005,
0.05518288537859917,
0.002... | 0.329011 |
the creation, mutation or removal of a `HelmRelease` resource in the cluster, Helm actions are performed by the controller. Helm Controller (and its predecessor, Helm Operator) stand alone in the GitOps world as Go client implementations of the Helm package library. While there are many projects in the GitOps space tha... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.06884216517210007,
0.02920711413025856,
0.011085865087807178,
-0.023102248087525368,
0.07437805086374283,
-0.00826298352330923,
-0.07569821178913116,
0.023746388033032417,
0.022240281105041504,
0.053922124207019806,
0.039708737283945084,
-0.0003793255891650915,
0.0033760396763682365,
-0... | 0.120261 |
cycle of a change as it's processed through Flux, centered around a Git commit: 0. [Bootstrapping Flux][] is the first step to get started using Flux. 1. [Generating a Flux resource][] with `flux create ...`. 2. [Previewing changes][] prior to making or pushing a commit with `flux diff kustomization`. 3. [Automating up... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.06944005936384201,
-0.03198381885886192,
0.020558355376124382,
0.026263054460287094,
0.09912611544132233,
-0.05613415688276291,
-0.020576629787683487,
0.023392396047711372,
0.055871300399303436,
0.031038306653499603,
0.0028379536233842373,
-0.00835132971405983,
0.05758204683661461,
-0.0... | 0.228289 |
``` ### Generating a Flux resource After bootstrapping, the Flux CLI provides `create` generators to help users build more of Flux's Custom Resources that drive the operation of Flux. `flux create source git --help` `flux create kustomization --help` These generators can be used imperatively to create Flux resources in... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.08864141255617142,
-0.027074843645095825,
-0.03469790890812874,
0.05522484332323074,
0.09304729104042053,
-0.0759085863828659,
0.016731813549995422,
0.025146620348095894,
0.024011950939893723,
-0.022799178957939148,
-0.003148719435557723,
-0.09809303283691406,
0.07408907264471054,
0.018... | 0.246085 |
Source of Truth Flux takes instructions from Git (or another source) which is meant to be the Single Source of Truth. Users create Git commits and push them to the repository that Flux is watching. Except when it happens as a result of Image Automation, the commit itself happens outside of Flux's purview. The source-co... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.10232394188642502,
-0.04014096409082413,
-0.017567571252584457,
0.04862485080957413,
0.13679270446300507,
-0.07074074447154999,
0.0038687882479280233,
0.013232908211648464,
0.11663006246089935,
0.05893118679523468,
0.013378855772316456,
-0.04456063732504845,
0.0789313018321991,
-0.03066... | 0.203631 |
`sourceRef`; for resources that come from the outside internet, or other non-native resources to Kubernetes, the Flux `Receiver` and a corresponding webhook configuration at the outside service is manually configured for this purpose instead. Any Flux resource that subscribes to any outside service (those that are exte... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.07467635720968246,
0.011193147860467434,
0.02324989065527916,
0.0000745069410186261,
0.10555769503116608,
-0.06183531880378723,
0.007505076937377453,
0.014497540891170502,
0.09882241487503052,
0.0429975762963295,
-0.02897702343761921,
-0.07125438749790192,
0.036615777760744095,
-0.05343... | 0.281633 |
Note that it does not make any difference to the Source Controller whether a source is hosted within the cluster or on an external service or server. The Source Controller will still attempt to verify the host using the SSH or TLS keys supplied in the GitRepository Custom Resource and will store its contents as a read-... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.053865183144807816,
0.024509375914931297,
-0.04528483375906944,
0.025901222601532936,
0.07284963130950928,
-0.05014410987496376,
-0.02354634739458561,
-0.04428550601005554,
0.06173073127865791,
0.05390264838933945,
-0.016167109832167625,
-0.0626581534743309,
0.0685194656252861,
-0.08000... | 0.124085 |
Apply \*\*Needs a link to Flux documentation for Server-Side Apply process!\*\* \_The only current on-point reference is the [Server-side reconciliation is coming](/blog/2021/09/server-side-reconciliation-is-coming/) blog post.\_ The Kustomize Controller communicates directly with the Kubernetes API using [server-side ... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.053693756461143494,
0.03126984462141991,
0.032018497586250305,
-0.030871668830513954,
-0.004620471503585577,
-0.002673354232683778,
0.016198283061385155,
0.03393534570932388,
0.10606443136930466,
0.03257130831480026,
-0.040752507746219635,
-0.027601057663559914,
0.010000141337513924,
-0... | 0.236454 |
HelmReleases through the same `GitRepository`, but instead limit it to one chart per `GitRepository`. It is a bad idea to create a `GitRepository` with 400 helm charts. Why exactly? The problem is that Git repo sources are simple `.tgz` files under the hood, and since it's not possible to partially fetch such an artifa... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.04675756022334099,
0.07033929228782654,
0.0549783818423748,
-0.024997670203447342,
0.03387609124183655,
-0.0615181066095829,
-0.03826095536351204,
0.03617925941944122,
0.03371007367968559,
0.05043353512883186,
-0.012378975749015808,
-0.012390506453812122,
0.07845819741487503,
-0.0183934... | 0.022028 |
emit events kube->>hc: 6. notify about new revision hc->>sc: 7. fetch chart hc->>kube: 8. get values hc->>hc: 9. render and customize manifests hc-->>kube: 10. apply CRDs hc->>kube: 11. upgrade release hc-->>kube: 12. run tests hc-->>kube: 13. wait for readiness hc->>kube: 14. update status hc-->>nc: 15. emit events nc... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.005936333443969488,
-0.007649423088878393,
0.02066357247531414,
0.011406431905925274,
0.07002337276935577,
-0.004353110212832689,
0.06680577248334885,
-0.00965050794184208,
0.07767127454280853,
0.01794498786330223,
-0.03571727126836777,
-0.13677704334259033,
0.02218588814139366,
0.00870... | 0.212488 |
automation guide]: /flux/guides/image-update/#configure-image-update-for-custom-resources [Core Concepts]: /flux/concepts/ [Get Started with Flux]: /flux/get-started/ [GitRepository Custom Resource]: /flux/components/source/gitrepositories/ [BucketSpec Custom Resource]: /flux/components/source/buckets/ [HelmRepository ... | https://github.com/fluxcd/website/blob/main/content/en/flux/flux-e2e.md | main | fluxcd | [
-0.0023053346667438745,
0.0052527678199112415,
-0.003905545687302947,
-0.0008190309745259583,
0.07027233392000198,
-0.008045054972171783,
-0.031003734096884727,
0.06301136314868927,
-0.01647169701755047,
0.012382963672280312,
0.02131618559360504,
-0.013917587697505951,
0.049187686294317245,
... | 0.166361 |
This tutorial shows you how to bootstrap Flux to a Kubernetes cluster and deploy a sample application in a GitOps manner. ## Before you begin To follow the guide, you need the following: - \*\*A Kubernetes cluster\*\*. We recommend [Kubernetes kind](https://kind.sigs.k8s.io/docs/user/quick-start/) for trying Flux out i... | https://github.com/fluxcd/website/blob/main/content/en/flux/get-started.md | main | fluxcd | [
-0.05361686274409294,
-0.042700257152318954,
-0.0005567322368733585,
-0.017017008736729622,
-0.008282250724732876,
-0.015879767015576363,
0.02132204733788967,
0.11011234670877457,
-0.0012916215928271413,
0.04978808015584946,
-0.046662040054798126,
-0.08589647710323334,
0.08259565383195877,
... | 0.18577 |
--wait=true \ --interval=30m \ --retry-interval=2m \ --health-check-timeout=3m \ --export > ./clusters/my-cluster/podinfo-kustomization.yaml ``` The output is similar to: ```yaml apiVersion: kustomize.toolkit.fluxcd.io/v1 kind: Kustomization metadata: name: podinfo namespace: flux-system spec: interval: 30m0s path: ./k... | https://github.com/fluxcd/website/blob/main/content/en/flux/get-started.md | main | fluxcd | [
0.019149525091052055,
-0.03341980651021004,
-0.02019975148141384,
0.013146663084626198,
0.031013263389468193,
-0.04548833146691322,
-0.03464001044631004,
0.02938498556613922,
0.033322952687740326,
0.02804054319858551,
0.05461996793746948,
-0.10306163132190704,
0.006790930405259132,
-0.0440... | 0.226679 |
Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration (like Git repositories), and automating updates to configuration when there is new code to deploy. Flux is built from the ground up to use Kubernetes' API extension system, and to integrate with Prometheus and other core components of ... | https://github.com/fluxcd/website/blob/main/content/en/flux/_index.md | main | fluxcd | [
-0.05636944621801376,
-0.07706231623888016,
0.0013126878766342998,
0.019198408350348473,
0.03712420538067818,
-0.06805822998285294,
0.01783697120845318,
0.005580301862210035,
0.014215486124157906,
0.03422064706683159,
-0.034814585000276566,
-0.04671807959675789,
0.0255258958786726,
0.02941... | 0.308925 |
do with Flux? Flux is based on a set of Kubernetes API extensions ("custom resources"), which control how git repositories and other sources of configuration are applied into the cluster ("synced"). For example, you create a `GitRepository` object to mirror configuration from a Git repository, then a `Kustomization` ob... | https://github.com/fluxcd/website/blob/main/content/en/flux/_index.md | main | fluxcd | [
-0.07334234565496445,
-0.07602416723966599,
-0.011104606091976166,
0.04500716179609299,
0.04181467741727829,
-0.05010451376438141,
0.003932708874344826,
0.014520373195409775,
0.028655320405960083,
0.02239786460995674,
-0.04040690138936043,
-0.038630709052085876,
0.0539044588804245,
-0.0066... | 0.243008 |
The Flux CLI is available as a binary executable for all major platforms, the binaries can be downloaded from GitHub [releases page](https://github.com/fluxcd/flux2/releases). ## Install using package management {{< tabpane text=true >}} {{% tab header="macOS" %}} With [Homebrew](https://brew.sh): ```sh brew install fl... | https://github.com/fluxcd/website/blob/main/content/en/flux/cmd/_index.md | main | fluxcd | [
-0.01973291113972664,
-0.057642612606287,
-0.010524063371121883,
-0.0914616733789444,
0.07531886547803879,
-0.0662403255701065,
-0.005533460061997175,
0.07890981435775757,
-0.028245747089385986,
-0.013799513690173626,
-0.00315947481431067,
-0.126413956284523,
-0.013777178712189198,
0.08160... | 0.167559 |
The Go packages in [github.com/fluxcd/pkg](https://github.com/fluxcd/pkg) are dedicated Go modules, each module has its own set of dependencies and release cycle. These packages are primarily meant for internal use in Flux controllers and for projects which integrate and/or extend Flux. ## Release versioning The Flux p... | https://github.com/fluxcd/website/blob/main/content/en/flux/releases/packages.md | main | fluxcd | [
-0.03698579594492912,
-0.029763903468847275,
-0.0005016496288590133,
-0.046598684042692184,
0.09950004518032074,
0.03743719309568405,
-0.019533326849341393,
0.052595432847738266,
0.008367716334760189,
-0.04014449194073677,
0.08809640258550644,
0.030234677717089653,
-0.04924563318490982,
0.... | 0.109483 |
This document provides an overview of the release procedures for each component type in the Flux project. It is intended for project maintainers, but may also be useful for contributors who want to understand the release process. If you have any questions, please reach out to another maintainer for clarification. ## Ta... | https://github.com/fluxcd/website/blob/main/content/en/flux/releases/procedure.md | main | fluxcd | [
-0.004171331413090229,
-0.04345104843378067,
0.05858665704727173,
-0.03610556572675705,
0.12799639999866486,
0.06741809099912643,
-0.01002424769103527,
0.03897932171821594,
-0.04795241355895996,
0.051230791956186295,
0.07251784950494766,
-0.010952952317893505,
-0.012526319362223148,
-0.009... | 0.1147 |
config/manager/kustomization.yaml git add go.mod config/manager/kustomization.yaml git commit -s -m "Release v1.2.0" git push origin release-v1.2.0 ``` 6. Create a pull request for the release branch and merge it into the release series branch (e.g., `release/v1.2.x`). 7. Create `api/` and `` tags for the merge commit ... | https://github.com/fluxcd/website/blob/main/content/en/flux/releases/procedure.md | main | fluxcd | [
0.0394231341779232,
-0.06383713334798813,
0.04072659835219383,
-0.06418955326080322,
-0.052654046565294266,
-0.021268025040626526,
-0.03421812877058983,
0.01340557262301445,
0.030064662918448448,
0.06232471019029617,
0.08137232065200806,
-0.025168735533952713,
-0.019532259553670883,
0.0038... | 0.022747 |
a Git tag, GitHub release, or a changelog entry. To create a preview release, follow the steps below. 1. Navigate to `https://github.com/fluxcd/-controller/actions/workflows/release.yml`. 2. Click the `Run workflow` button. 3. Select the branch to release from the `Branch` dropdown. 4. The default values for the `image... | https://github.com/fluxcd/website/blob/main/content/en/flux/releases/procedure.md | main | fluxcd | [
-0.02624352090060711,
-0.045005105435848236,
-0.008227505721151829,
0.008674541488289833,
0.12155911326408386,
-0.012033888138830662,
-0.017665965482592583,
0.0857911929488182,
-0.0010689017362892628,
0.0122549869120121,
0.008824980817735195,
-0.024005679413676262,
0.01827126555144787,
0.0... | 0.069127 |
cause automatic backports to fail with a conflict. 1. In `.github/labels.yaml` add an entry for the `backport:v2-N` label by copying the existing `backport:v2-(N-1)` one. 1. Commit the changes and create a PR for the `main` branch. 1. As soon as the PR is merged, create the "v2-N" branch from `main`: ```shell git check... | https://github.com/fluxcd/website/blob/main/content/en/flux/releases/procedure.md | main | fluxcd | [
-0.0033383171539753675,
-0.06815765053033829,
-0.013564747758209705,
-0.0666022077202797,
0.05706764757633209,
-0.02238927036523819,
-0.039089035242795944,
0.019567424431443214,
-0.004844079725444317,
-0.004911585245281458,
0.06994681060314178,
0.027793657034635544,
0.0016180988168343902,
... | -0.008988 |
file accordingly. ## Backport changes for patch releases The Flux projects have a backport bot that automates the process of backporting changes from `main` to the release series branches. The bot is configured to backport pull requests that are labeled with `backport:` (e.g., `backport:release/v2.1.x`) and have been m... | https://github.com/fluxcd/website/blob/main/content/en/flux/releases/procedure.md | main | fluxcd | [
-0.08193306624889374,
-0.08475127816200256,
0.043367549777030945,
-0.00784445833414793,
0.07753860950469971,
0.007033499889075756,
-0.022991938516497612,
0.05068480968475342,
-0.027664881199598312,
0.019438350573182106,
0.026601195335388184,
0.029703062027692795,
-0.0209965743124485,
-0.07... | 0.109167 |
The Flux controllers are [Kubernetes operators](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/), each controller has its own Git repository and release cycle (see below for details). Controller repositories and their interdependencies: 1. [source-controller](https://github.com/fluxcd/source-controller)... | https://github.com/fluxcd/website/blob/main/content/en/flux/releases/controllers.md | main | fluxcd | [
-0.0959320142865181,
-0.05719233304262161,
0.015009688213467598,
-0.022051312029361725,
0.08288618922233582,
0.0008841619710437953,
-0.002000991487875581,
0.05719008669257164,
0.08064857870340347,
0.06940337270498276,
0.06949932873249054,
-0.04611774533987045,
0.015484985895454884,
-0.0115... | 0.17564 |
feature additions or any type of user-facing changes. If a security fix requires a breaking change, then a minor release will provide the fix. We expect users to be running the latest patch release of a given minor release as soon as the controller release is included in a Flux patch release. ### Minor releases Minor r... | https://github.com/fluxcd/website/blob/main/content/en/flux/releases/controllers.md | main | fluxcd | [
-0.014921806752681732,
-0.022554099559783936,
0.13304659724235535,
-0.042847245931625366,
0.06992680579423904,
0.03477511927485466,
-0.09329105168581009,
-0.003405181923881173,
0.05115212872624397,
0.0621112659573555,
0.06531082838773727,
0.025286084040999413,
-0.029072169214487076,
-0.042... | 0.113543 |
The Flux project repository [fluxcd/flux2](https://github.com/fluxcd/flux2) contains the Flux command-line tool source code and the Kubernetes manifests for bundling the [Flux controllers](controllers.md) into a distributable package. ## Release versioning Flux is released by following the [semver](https://semver.org/)... | https://github.com/fluxcd/website/blob/main/content/en/flux/releases/_index.md | main | fluxcd | [
-0.025236260145902634,
-0.06689563393592834,
0.05862388014793396,
-0.025537777692079544,
0.09338950365781784,
0.01174002606421709,
-0.051050931215286255,
0.010057465173304081,
0.022043360397219658,
0.02015618607401848,
0.040314190089702606,
-0.015746157616376877,
-0.010072492994368076,
-0.... | 0.133086 |
any `v2.x` release to any other `v2.x` release (the latest patch version). After upgrade, [Flux Custom Resources](controllers.md#api-versioning) may require editing, for which migration instructions are provided as part of the [changelog](#release-changelog). We expect users to keep Flux up-to-date on their clusters us... | https://github.com/fluxcd/website/blob/main/content/en/flux/releases/_index.md | main | fluxcd | [
-0.06290365755558014,
-0.0358249768614769,
-0.0010536090703681111,
-0.002229399746283889,
0.11541295796632767,
0.02111043408513069,
-0.036009531468153,
0.03753039240837097,
-0.0419263020157814,
0.04544135928153992,
-0.025032179430127144,
0.010992013849318027,
0.06850581616163254,
0.0480812... | 0.102207 |
## Introduction The Flux project strives to keep its components secure by design and by default. This document aims to list all security-sensitive options or considerations that must be taken into account when deploying Flux. And also serve as a guide for security professionals auditing such deployments. Not all recomm... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/best-practices.md | main | fluxcd | [
-0.013124960474669933,
0.03150567039847374,
0.0012256518239155412,
-0.023758985102176666,
0.06584759056568146,
0.02185421995818615,
0.029805129393935204,
0.0760221779346466,
0.02568991668522358,
0.04052087664604187,
-0.017922447994351387,
-0.07634273171424866,
0.05114028602838516,
0.018071... | 0.161461 |
Check Kustomize Controller's pod YAML for the arguments used at start-up: ```sh kubectl describe pod -n flux-system -l app=kustomize-controller | grep -B 5 -A 10 Args ``` #### Secret Decryption - Ensure Secret Decryption is enabled and secrets are not being held in Flux Sources in plaintext. Rationale The kustomize-con... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/best-practices.md | main | fluxcd | [
-0.0388152040541172,
0.02853921242058277,
-0.03836158663034439,
-0.038292333483695984,
-0.019835537299513817,
-0.028559798374772072,
0.03164159879088402,
-0.005733152851462364,
0.12524940073490143,
0.011350600980222225,
-0.023898586630821228,
-0.06722041219472885,
0.01561983022838831,
-0.0... | 0.182451 |
for `helm-controller`, and `--default-service-account` for `source-controller`, `notification-controller`, `image-reflector-controller` and `image-automation-controller`. Audit Procedure Check all Flux controllers for workload identity default service account flags (`--default-service-account`, `--default-decryption-se... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/best-practices.md | main | fluxcd | [
0.004236715380102396,
-0.006242583971470594,
-0.02037426084280014,
-0.04156678915023804,
0.08900982141494751,
-0.03148609772324562,
0.07062195241451263,
0.04215042293071747,
0.06177006661891937,
0.031082279980182648,
0.040638819336891174,
-0.12463337928056717,
0.07370650768280029,
-0.02903... | 0.130593 |
Plane privileges while some tenants may not. A co-located pod could leverage its privileges in the shared worker node to bypass its own Control Plane access limitations by compromising one of the co-located Flux components. For cases in which cross-tenant isolation requirements must be enforced, the same risks apply. E... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/best-practices.md | main | fluxcd | [
0.08253460377454758,
-0.004201958887279034,
0.033843062818050385,
-0.010198360309004784,
0.016094494611024857,
-0.03538237512111664,
-0.000878873688634485,
-0.0708501935005188,
0.023003729060292244,
0.005236728582531214,
0.0047792308032512665,
-0.02492249757051468,
-0.022895699366927147,
0... | 0.102636 |
## Introduction Most cloud providers support context-based authorization, enabling applications to benefit from strong access controls applied to a given context (e.g. Virtual Machine), without the need of managing authentication tokens and credentials. For example, by granting a given Virtual Machine (or principal tha... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/contextual-authorization.md | main | fluxcd | [
-0.09856006503105164,
0.01430579461157322,
0.007135326042771339,
-0.03924090787768364,
0.06276945024728775,
0.021322807297110558,
0.04637350142002106,
0.023425115272402763,
0.04211662337183952,
0.04196982830762863,
-0.028929609805345535,
-0.018447231501340866,
0.10167766362428665,
-0.00995... | 0.131108 |
## Introduction Flux has a multi-component design, and integrates with many other systems. This document outlines an overview of security considerations for Flux components, project processes, artifacts, as well as Flux configurable options and what they enable for both Kubernetes cluster and external system security. ... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/_index.md | main | fluxcd | [
-0.039372026920318604,
0.04169130325317383,
0.019305067136883736,
-0.056873396039009094,
0.14160506427288055,
-0.020514648407697678,
0.0592864491045475,
0.0908067598938942,
0.027820002287626266,
-0.00009287463035434484,
0.006763212848454714,
-0.06470268219709396,
0.07773204892873764,
0.027... | 0.167206 |
statically built using Go. To properly scan Flux container images, the scanner must be able to detect the Alpine apk packages and the Go modules included in the controller's Go binary. The Go modules and apk packages are also available for inspection in the attached [SBOM](#software-bill-of-materials). The Flux team re... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/_index.md | main | fluxcd | [
-0.04021049663424492,
0.0296940840780735,
-0.09438678622245789,
-0.06551280617713928,
0.10481665283441544,
-0.0817013680934906,
0.03902113437652588,
0.07668747007846832,
-0.07111810892820358,
-0.02995298244059086,
0.05053302273154259,
-0.0491659976541996,
0.08203800767660141,
0.12095449864... | 0.08951 |
not reconcile a tenant's repo under the `cluster-admin` role. Instead, you specify a different service account in your manifest, and the Flux controllers will use the Kubernetes Impersonation API under `cluster-admin` to impersonate that service account [^2]. In this way, policy restrictions for this service account ar... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/_index.md | main | fluxcd | [
-0.030487366020679474,
-0.09014981240034103,
-0.010127303190529346,
-0.03386438265442848,
0.009447726421058178,
0.00181017373688519,
0.06679732352495193,
-0.026442065834999084,
0.038407519459724426,
0.026607854291796684,
-0.004192454740405083,
-0.09780199825763702,
0.09952814877033234,
0.0... | 0.101777 |
## Introduction Supply Chain Levels for Software Artifacts, or SLSA (pronounced "salsa"), is a security framework which aims to prevent tampering and secure artifacts in a project. SLSA is designed to support automation that tracks code handling from source to binary protecting against tampering regardless of the compl... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/slsa-assessment.md | main | fluxcd | [
-0.09206041693687439,
-0.029115132987499237,
-0.003474589204415679,
-0.03193773701786995,
0.06923802196979523,
-0.07068980485200882,
-0.03621894121170044,
0.04166199266910553,
-0.056962750852108,
-0.0464455746114254,
0.02110064961016178,
-0.05999002605676651,
0.07916387170553207,
-0.009008... | 0.163638 |
The provenance file stores the SHA-256 hashes of the release artifacts (binaries, SBOMs, deploy manifests, source code). - The provenance identifies the Flux container images using their digest in SHA-256 format. > Consumers MUST be able to validate the authenticity of the provenance attestation in order to ensure inte... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/slsa-assessment.md | main | fluxcd | [
-0.03622577339410782,
0.019859660416841507,
-0.07369857281446457,
-0.01909189112484455,
0.15041260421276093,
-0.02465144544839859,
-0.011760633438825607,
0.029399855062365532,
0.048025570809841156,
0.003412314923480153,
0.058158062398433685,
-0.009994604624807835,
0.025030752643942833,
-0.... | 0.120913 |
digest of the image to verify: ```console $ crane digest ghcr.io/fluxcd/source-controller:v1.0.0 sha256:8dfd386a338eab2fde70cd7609e3b35a6e2f30283ecf2366da53013295fa65f3 ``` Using the digest, verify the provenance of the Flux controller by specifying the repository and version: ```console $ slsa-verifier verify-image gh... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/slsa-assessment.md | main | fluxcd | [
-0.10451251268386841,
-0.030168721452355385,
-0.05535346269607544,
-0.04348644241690636,
0.15432608127593994,
-0.08777406066656113,
-0.029810089617967606,
0.046974342316389084,
0.007412318140268326,
0.000970024149864912,
0.10072830319404602,
-0.08963710069656372,
0.03149726241827011,
-0.00... | 0.059994 |
## Introduction Flux improves the application deployment process by continuously reconciling a desired state, defined at a source, against a target cluster. One of the challenges with this process is its dependency on secrets, that must not be stored in plain-text like the rest of the desired state. Secrets are sensiti... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/secrets-management.md | main | fluxcd | [
-0.07235223799943924,
0.027024008333683014,
0.044175975024700165,
-0.001372033730149269,
0.023093925788998604,
0.0010681940475478768,
0.010669305920600891,
0.039710354059934616,
0.04856695979833603,
0.02742747776210308,
-0.029933476820588112,
-0.05330272763967514,
0.07640437036752701,
-0.0... | 0.218301 |
using Age and PGP. This mechanism supports [kustomize-secretgenerator] which ensures that dependent workloads will reload automatically and start using the latest version of the secret. Notice that most approaches that are based on Kubernetes Secrets would require something like [stakater/Reloader] to achieve the same ... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/secrets-management.md | main | fluxcd | [
-0.09148441255092621,
0.03312106430530548,
0.011323138140141964,
0.019447267055511475,
0.0026037099305540323,
0.010409862734377384,
0.0026133658830076456,
0.002798239002004266,
0.030374176800251007,
-0.03654716536402702,
-0.015906784683465958,
0.053081221878528595,
-0.0013058050535619259,
... | 0.112244 |
Secret Manager, without a rate limiter across all of them, this could easily lead to an outage at scale. Flux currently does not directly fetch secrets from out-of-cluster solutions, in the same way that most Kubernetes native tools don't, therefore this approach may need to be combined with things such as Secrets Sync... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/secrets-management.md | main | fluxcd | [
-0.08953908085823059,
-0.01642875000834465,
0.03019990213215351,
-0.007084548939019442,
0.018536217510700226,
0.014220218174159527,
-0.051982175558805466,
0.0033569668885320425,
0.0636955052614212,
0.009763933718204498,
0.030480172485113144,
-0.005414243321865797,
0.04022100940346718,
-0.0... | 0.083662 |
ciphertext and understand what needs to be compromised for the data to be at risk. #### Single Points of Failure Identify all potential single points of failure and ensure that there is a way around them. If all your secrets are encrypted using an encryption key stored in Vault, and due to a major failure your Vault in... | https://github.com/fluxcd/website/blob/main/content/en/flux/security/secrets-management.md | main | fluxcd | [
-0.014689232222735882,
0.03710181638598442,
0.048891227692365646,
0.006065963301807642,
0.020299924537539482,
0.02850915677845478,
-0.021179277449846268,
0.03749360516667366,
0.06748517602682114,
0.01031876727938652,
-0.02269751764833927,
-0.00447851000353694,
0.10511292517185211,
-0.06242... | 0.042523 |
No matter which [installation](\_index.md) method you've used to deploy the Flux controllers on a cluster, you can uninstall them using the Flux CLI. The uninstallation procedure removes only the Flux components, without touching reconciled namespaces, tenants, cluster addons, workloads, Helm releases, etc. Please note... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/uninstall.md | main | fluxcd | [
-0.002011398086324334,
0.01013550441712141,
0.023779921233654022,
-0.008111602626740932,
0.06344407796859741,
-0.014082856476306915,
0.003886120393872261,
-0.051099106669425964,
0.05101928487420082,
-0.010772043839097023,
0.0010778139112517238,
-0.021819395944476128,
0.04110626503825188,
-... | 0.154481 |
Flux can be upgrade from any `v2.x` release to any other `v2.x` release (the latest patch version). For more details about supported versions and upgrades please see the Flux [release documentation](/flux/releases/). {{% alert color="info" title="Upgrade Procedure for Flux v2.7+" %}} We have published a dedicated step-... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/upgrade.md | main | fluxcd | [
-0.011630749329924583,
-0.08927503973245621,
0.03286859393119812,
-0.049948517233133316,
0.10764860361814499,
-0.027616525068879128,
-0.04724007844924927,
0.04048888757824898,
-0.06059517711400986,
0.002023824490606785,
-0.008541307412087917,
-0.0452149324119091,
0.007398966699838638,
0.04... | 0.103669 |
helm.toolkit.fluxcd.io/v2 kind: HelmRelease metadata: name: << inputs.provider.name >> namespace: << inputs.provider.namespace >> spec: interval: 1h releaseName: << inputs.provider.name >> serviceAccountName: << inputs.provider.name >> upgrade: strategy: name: RetryOnFailure chartRef: kind: OCIRepository name: << input... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/upgrade.md | main | fluxcd | [
-0.046979762613773346,
-0.02665821462869644,
0.04076099023222923,
-0.013685843907296658,
0.08194021880626678,
-0.018530961126089096,
-0.04402150586247444,
0.07441718876361847,
-0.014743916690349579,
0.013346954248845577,
-0.00808924250304699,
-0.05458303168416023,
0.02996320091187954,
0.05... | 0.116214 |
The Flux project is comprised of a command-line tool (the Flux CLI) and a series of [Kubernetes controllers](/flux/components/). To install Flux, first you'll need to download the `flux` CLI. Then using the CLI, you can deploy the Flux controllers on your clusters and configure your first GitOps delivery pipeline. ## P... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/_index.md | main | fluxcd | [
0.0028179355431348085,
-0.08194656670093536,
0.03034236654639244,
0.0033838595263659954,
0.019731955602765083,
-0.006685571279376745,
-0.014936489053070545,
0.03338457643985748,
-0.02441522292792797,
0.05115009471774101,
-0.04458250105381012,
-0.1146872416138649,
0.027841871604323387,
0.02... | 0.122275 |
[Enforcing tenant isolation on shared clusters](configuration/multitenancy.md) \* [Using workload identity on AWS, Azure and GCP](configuration/workload-identity.md) Please see the [bootstrap configuration](configuration/\_index.md) section for more examples on how to customize Flux. ### Bootstrap with Terraform The bo... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/_index.md | main | fluxcd | [
-0.07229944318532944,
0.005250825081020594,
0.008901843801140785,
-0.0023886330891400576,
0.044785674661397934,
-0.009127603843808174,
0.020487116649746895,
-0.013937980867922306,
-0.013293461874127388,
0.05399332940578461,
-0.02595769427716732,
-0.04895329475402832,
0.11195748299360275,
0... | 0.082439 |
When Flux is managing hundreds of applications that are deployed multiple times per day, cluster admins can fine tune the Flux controller at [bootstrap time](bootstrap-customization.md) to run at scale by: - [Increasing the number of workers and resource limits](#increase-the-number-of-workers-and-limits) - [Enabling i... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/vertical-scaling.md | main | fluxcd | [
0.023635653778910637,
0.029494009912014008,
-0.009660065174102783,
0.04395526275038719,
0.0782061517238617,
-0.039052460342645645,
-0.04623839631676674,
0.06713436543941498,
-0.0408756360411644,
0.01651262864470482,
-0.025667941197752953,
-0.0007377121364697814,
0.08324899524450302,
0.0229... | 0.119771 |
storageClassName: standard resources: requests: storage: 10Gi ``` Add the PVC file to the `kustomization.yaml` resources and patch the source-controller volumes: ```yaml apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources: - gotk-components.yaml - gotk-sync.yaml - gotk-pvc.yaml patches: - patch: |... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/vertical-scaling.md | main | fluxcd | [
-0.03902555629611015,
0.0012900835135951638,
-0.03589927405118942,
0.021619092673063278,
0.011998035944998264,
0.01226793508976698,
0.006793611217290163,
0.03797522932291031,
0.011394941247999668,
0.04864206165075302,
0.024671096354722977,
-0.08568926900625229,
-0.006973997224122286,
0.008... | 0.151757 |
Flux allows different organizations and/or teams to share the same Kubernetes control plane; this is referred to as "multi-tenancy". To make this safe, Flux supports segmentation and isolation of resources by using namespaces and role-based access control (RBAC). ## Flux authorization model Flux defers to Kubernetes' n... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/multitenancy.md | main | fluxcd | [
-0.015855589881539345,
-0.04692067205905914,
-0.02859526127576828,
-0.015797046944499016,
0.013017361052334309,
-0.01279293093830347,
0.06755726784467697,
-0.0070962365716695786,
0.07501392066478729,
0.024156587198376656,
-0.01857762411236763,
-0.052663013339042664,
0.08750276267528534,
0.... | 0.195726 |
- patch: | - op: add path: /spec/template/spec/containers/0/args/- value: --default-service-account=default target: kind: Deployment name: "(kustomize-controller|helm-controller)" - patch: | - op: add path: /spec/serviceAccountName value: kustomize-controller target: kind: Kustomization name: "flux-system" ``` With the... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/multitenancy.md | main | fluxcd | [
-0.001687773852609098,
0.029966356232762337,
0.013697001151740551,
-0.016662361100316048,
-0.0002164566540159285,
0.009436341002583504,
0.04567752033472061,
-0.04029474034905434,
0.018710456788539886,
0.043727170675992966,
0.01564227044582367,
-0.07475277036428452,
0.05327654257416725,
0.0... | 0.157818 |
When memory usage of the helm-controller exceeds the configured limit, the controller will forcefully be killed by Kubernetes' OOM killer. This may result in a Helm release being left in a `pending-\*` state which causes the HelmRelease to get stuck in an `another operation (install/upgrade/rollback) is in progress` er... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/helm-oom-detection.md | main | fluxcd | [
0.05166255682706833,
0.06092515587806702,
0.02470472641289234,
0.0255022831261158,
0.0845465138554573,
-0.035051293671131134,
-0.0269639790058136,
0.04225097596645355,
0.11416471749544144,
0.06651921570301056,
0.016366824507713318,
0.058486830443143845,
-0.005508910398930311,
-0.0430719032... | 0.109502 |
If the Kubernetes cluster has Internet restrictions, requiring egress traffic to go through a proxy for accessing external services, you can configure the Flux controllers to use a HTTP/S and/or SOCKS5 SSH proxy. ## Using HTTP/S proxy for egress traffic If your cluster uses an HTTP proxy to reach GitHub or other extern... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/proxy-setting.md | main | fluxcd | [
-0.01995297521352768,
-0.04038741812109947,
0.014222419820725918,
-0.021541006863117218,
0.015771543607115746,
0.006546349730342627,
-0.03731947019696236,
0.036346450448036194,
0.03588885813951492,
0.06945671141147614,
-0.06855817884206772,
0.0009507990325801075,
-0.00032359204487875104,
0... | 0.123698 |
When running Flux on AWS EKS, Azure AKS and Google Cloud GKE you can leverage Kubernetes Workload Identity to grant Flux controllers access to cloud resources such as container registries, KMS, S3, etc. ## AWS IAM roles for service accounts To grant Flux access to AWS resources using IRSA [during bootstrap](bootstrap-c... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/workload-identity.md | main | fluxcd | [
-0.08781255781650543,
0.024624770507216454,
0.012550991959869862,
-0.0211560670286417,
0.06508642435073853,
0.019817592576146126,
0.0447629913687706,
-0.01915059983730316,
0.0485847070813179,
0.08876075595617294,
-0.024372799322009087,
-0.0676274374127388,
0.07707297801971436,
0.0175523180... | 0.145673 |
The `flux bootstrap` command deploys a series of Kubernetes controllers along with their CRDs, RBAC and network policies in the `flux-system` namespace. ## Default components The default components are specified with the `--components` flag. ```shell flux bootstrap git \ --components source-controller,kustomize-control... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/optional-components.md | main | fluxcd | [
-0.06154320389032364,
-0.06133675575256348,
0.032292719930410385,
-0.012258975766599178,
0.11449752748012543,
0.013497469946742058,
0.01594705320894718,
0.050410013645887375,
0.027526961639523506,
0.028125958517193794,
0.03698936849832535,
-0.06381139159202576,
0.05998042970895767,
0.02272... | 0.142608 |
To customize the Flux controllers during [bootstrap](/flux/installation#bootstrap-with-flux-cli), first you'll need to create a Git repository and clone it locally. Create the file structure required by bootstrap with: ```sh mkdir -p clusters/my-cluster/flux-system touch clusters/my-cluster/flux-system/gotk-components.... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/bootstrap-customization.md | main | fluxcd | [
-0.03537803888320923,
-0.024586699903011322,
0.0016857906011864543,
-0.029653018340468407,
0.023457355797290802,
0.021356068551540375,
-0.007558279670774937,
0.07556565850973129,
-0.010841012932360172,
0.06259100139141083,
-0.008151380345225334,
-0.03773592785000801,
0.031145082786679268,
... | 0.115716 |
When Flux is managing tens of thousands of applications, it is advised to adopt a sharding strategy to spread the load between multiple instances of Flux controllers. To enable horizontal scaling, each controller can be deployed multiple times with a unique label selector which is used as the sharding key. What follows... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/sharding.md | main | fluxcd | [
-0.0010612279875203967,
-0.07240402698516846,
-0.029819808900356293,
-0.022899584844708443,
0.029369864612817764,
-0.03630808740854263,
-0.0352037139236927,
0.05721774697303772,
0.01341666653752327,
-0.027682138606905937,
0.0017214469844475389,
-0.0460098572075367,
0.10958493500947952,
0.0... | 0.076522 |
helm-controller 1/1 1 1 1m helm-controller-shard1 1/1 1 1 1m kustomize-controller 1/1 1 1 1m kustomize-controller-shard1 1/1 1 1 1m notification-controller 1/1 1 1 1m source-controller 1/1 1 1 1m source-controller-shard1 1/1 1 1 1m ``` When upgrading Flux, either by rerunning bootstrap with a newer version or by using ... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/sharding.md | main | fluxcd | [
0.006099160294979811,
-0.049817778170108795,
-0.008361708372831345,
-0.043555282056331635,
0.06040111929178238,
-0.00759296165779233,
-0.002413820242509246,
0.010827161371707916,
0.021051540970802307,
-0.012306495569646358,
0.012085347436368465,
-0.06741682440042496,
0.08494153618812561,
-... | 0.058391 |
There are several reasons you may want to rotate the deploy key: - The token used to generate the key has expired. - The key has been compromised. - You want to change the scope of the key, e.g. to allow write access using the `--read-write-key` flag to `flux bootstrap`. While you can run `flux bootstrap` repeatedly, b... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/deploy-key-rotation.md | main | fluxcd | [
-0.02405737154185772,
-0.018552714958786964,
0.016254758462309837,
-0.028737321496009827,
-0.0007830694084987044,
-0.008672161027789116,
0.0028171318117529154,
0.06387457251548767,
0.08504975587129593,
0.06646324694156647,
0.05767664685845375,
-0.0063326102681458,
0.09776314347982407,
-0.0... | 0.076366 |
By default, the helm-controller will not perform DNS lookups when rendering Helm templates in clusters because of potential [security implications](https://github.com/helm/helm/security/advisories/GHSA-pwcw-6f5g-gxf8). To enable DNS lookups [during bootstrap](bootstrap-customization.md) add the following patches to the... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/helm-dns-lookup.md | main | fluxcd | [
-0.07242640107870102,
0.061728037893772125,
0.05978352949023247,
-0.03373299911618233,
0.04087383300065994,
-0.019553720951080322,
-0.08835595101118088,
0.00533296400681138,
0.06828080862760544,
0.03620274364948273,
-0.04227302968502045,
-0.005737571977078915,
-0.015795515850186348,
-0.003... | 0.031279 |
Flux can be installed on air-gapped environments where the Kubernetes cluster, the container registry and the Git server are not connected to the internet. ## Copy the container images On a machine with access to `github.com` and `ghcr.io`, download the Flux CLI from [GitHub releases page](https://github.com/fluxcd/flu... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/air-gapped.md | main | fluxcd | [
-0.04715671390295029,
-0.050211258232593536,
0.005917609203606844,
-0.01435520313680172,
0.0824093297123909,
-0.027784673497080803,
-0.012304997071623802,
0.061870820820331573,
0.006378794088959694,
0.01193633396178484,
0.058834247291088104,
-0.0786496251821518,
0.03152584284543991,
0.0286... | 0.104548 |
{{% alert color="danger" title="Required permissions" %}} To bootstrap Flux, the person running the command must have \*\*cluster admin rights\*\* for the target OpenShift cluster. It is also required to prepare a Git repository as described in the [bootstrap customization](bootstrap-customization.md). {{% /alert %}} F... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/configuration/openshift.md | main | fluxcd | [
0.01706506311893463,
-0.022754130885004997,
-0.05205987021327019,
0.01771586388349533,
0.14603959023952484,
0.007335437461733818,
-0.022729497402906418,
0.08893124759197235,
-0.037683241069316864,
-0.008601415902376175,
-0.011657054536044598,
-0.0856492817401886,
0.05941334739327431,
0.064... | 0.166679 |
To install Flux on a GKE cluster using a Google Cloud Source repository as the source of truth, you can use the [`flux bootstrap git`](generic-git-server.md) command. {{% alert color="danger" title="Required permissions" %}} To bootstrap Flux, the person running the command must have \*\*cluster admin rights\*\* for th... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/google-cloud-source.md | main | fluxcd | [
-0.027117695659399033,
-0.028621643781661987,
0.05508626624941826,
-0.05058057978749275,
0.07118164002895355,
-0.011770404875278473,
-0.000829362019430846,
0.030964279547333717,
0.0020255164708942175,
0.02850227802991867,
-0.008439398370683193,
-0.10566878318786621,
0.1025942787528038,
-0.... | 0.06021 |
The [flux bootstrap gitea](/flux/cmd/flux\_bootstrap\_gitea/) command deploys the Flux controllers on a Kubernetes cluster and configures the controllers to sync the cluster state from a Gitea repository. Besides installing the controllers, the bootstrap command pushes the Flux manifests to the Gitea repository and con... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/gitea.md | main | fluxcd | [
-0.0202307291328907,
-0.06476166099309921,
-0.007967655546963215,
0.01615934632718563,
0.06310741603374481,
0.0036426493898034096,
0.008306849747896194,
0.04796528443694115,
-0.006845878437161446,
0.055481914430856705,
0.0015296255005523562,
-0.04304084554314613,
0.07760993391275406,
0.042... | 0.171669 |
generated SSH key defaults to `ECDSA P-384`, to change the format use `--ssh-key-algorithm` and `--ssh-ecdsa-curve`. The SSH public key, is used to create a Gitea deploy key. The deploy key is linked to the personal access token used to authenticate. By default, the Gitea deploy key is set to read-only access. If you'r... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/gitea.md | main | fluxcd | [
-0.0076491027139127254,
-0.025290202349424362,
-0.03957538306713104,
0.0007128454744815826,
0.083127960562706,
-0.007291482761502266,
-0.04320857673883438,
0.06627065688371658,
0.047911208122968674,
0.026600759476423264,
0.07750588655471802,
0.008650485426187515,
0.12325342744588852,
0.026... | 0.079853 |
To install Flux on an [OKE](https://www.oracle.com/cloud/cloud-native/container-engine-kubernetes) cluster using an Oracle VBS Git repository as the source of truth, you can use the [`flux bootstrap git`](generic-git-server.md) command. {{% alert color="danger" title="Required permissions" %}} To bootstrap Flux, the pe... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/oracle-vbs-git-repositories.md | main | fluxcd | [
-0.03193523362278938,
-0.02657882682979107,
0.003345564240589738,
-0.024742087349295616,
0.0733867734670639,
-0.0061505576595664024,
0.027929946780204773,
0.06345707923173904,
0.002396050840616226,
0.032680217176675797,
-0.037684716284275055,
-0.11603463441133499,
0.026586664840579033,
0.0... | 0.124375 |
To install Flux on an EKS cluster using a CodeCommit repository as the source of truth, you can use the [`flux bootstrap git`](generic-git-server.md) command. {{% alert color="danger" title="Required permissions" %}} To bootstrap Flux, the person running the command must have \*\*cluster admin rights\*\* for the target... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/aws-codecommit.md | main | fluxcd | [
-0.0015672871377319098,
-0.004046338144689798,
-0.04002048820257187,
0.023414745926856995,
0.08319578319787979,
0.0323285311460495,
0.017931634560227394,
0.032815009355545044,
0.0512983538210392,
0.05816235393285751,
-0.006204519886523485,
-0.1037343293428421,
0.07271288335323334,
0.002067... | 0.121442 |
The [flux bootstrap github](/flux/cmd/flux\_bootstrap\_github/) command deploys the Flux controllers on a Kubernetes cluster and configures the controllers to sync the cluster state from a GitHub repository. Besides installing the controllers, the bootstrap command pushes the Flux manifests to the GitHub repository and... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/github.md | main | fluxcd | [
-0.04500390961766243,
-0.07789912074804306,
-0.01215134933590889,
0.0169378612190485,
0.08250965178012848,
-0.005946829449385405,
-0.01247958093881607,
0.050940096378326416,
0.016033563762903214,
0.040554940700531006,
0.00803805235773325,
-0.05017993971705437,
0.0773693099617958,
0.0252505... | 0.185262 |
GitHub teams with `--team=team1-slug,team2-slug`, those teams will be granted maintainer access to the repository. ## GitHub Enterprise To run the bootstrap for a repository hosted on GitHub Enterprise, you have to specify your GitHub hostname: ```sh flux bootstrap github \ --token-auth \ --hostname=my-github-enterpris... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/github.md | main | fluxcd | [
-0.020076127722859383,
-0.05146034434437752,
-0.04772699996829033,
-0.009506355039775372,
0.031153524294495583,
-0.03631795570254326,
-0.03555338457226753,
0.03554454818367958,
0.013377048075199127,
-0.0021675091702491045,
0.008853600360453129,
-0.0714678019285202,
0.10377904772758484,
0.0... | 0.139895 |
The [flux bootstrap bitbucket-server](/flux/cmd/flux\_bootstrap\_bitbucket-server/) command deploys the Flux controllers on a Kubernetes cluster and configures the controllers to sync the cluster state from a Bitbucket project. Besides installing the controllers, the bootstrap command pushes the Flux manifests to the B... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/bitbucket.md | main | fluxcd | [
-0.059321168810129166,
-0.046858835965394974,
-0.013016385026276112,
0.031634245067834854,
0.0687682181596756,
-0.009509427472949028,
0.01952115260064602,
0.05302777141332626,
0.007231138180941343,
0.0668584406375885,
0.005350951105356216,
-0.05648091435432434,
0.07316523790359497,
0.02548... | 0.1364 |
it write access with `--read-write-key=true`. To run the bootstrap for Bitbucket server with a custom SSH hostname and port: ```sh flux bootstrap bitbucket-server \ --hostname=my-bitbucket-server.com \ --ssh-hostname=my-bitbucket-server.com:7999 \ --owner=my-bitbucket-project \ --username=my-bitbucket-username \ --repo... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/bitbucket.md | main | fluxcd | [
-0.04853293299674988,
-0.0338260643184185,
-0.04544875770807266,
0.0589270293712616,
0.058598436415195465,
-0.03340398520231247,
0.0018696748884394765,
0.11636195331811905,
0.011036448180675507,
0.0408669076859951,
0.003077446948736906,
-0.0031443648040294647,
0.09300244599580765,
-0.01699... | 0.127238 |
The [flux bootstrap gitlab](/flux/cmd/flux\_bootstrap\_gitlab/) command deploys the Flux controllers on a Kubernetes cluster and configures the controllers to sync the cluster state from a GitLab project. Besides installing the controllers, the bootstrap command pushes the Flux manifests to the GitLab project and confi... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/gitlab.md | main | fluxcd | [
-0.07033588737249374,
-0.05235474929213524,
0.0038079265505075455,
0.023902500048279762,
0.0566384494304657,
-0.040134236216545105,
0.02272868901491165,
0.039546988904476166,
0.01558965165168047,
0.04223761707544327,
0.00006697785283904523,
-0.05646306276321411,
0.09979352355003357,
0.0500... | 0.145402 |
`flux-system` secret from the cluster and re-run the bootstrap command using a valid GitLab PAT. {{% /alert %}} ## Bootstrap without a GitLab PAT For existing GitLab repositories, you can bootstrap Flux over SSH without using a GitLab PAT. To use an SSH key instead of a GitLab PAT, the command changes to `flux bootstra... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/gitlab.md | main | fluxcd | [
-0.03764384612441063,
-0.03728888928890228,
-0.013981986790895462,
0.01766708865761757,
0.04881433770060539,
-0.08586473762989044,
-0.009872515685856342,
0.07544314861297607,
0.011357936076819897,
0.022364702075719833,
-0.002334867138415575,
-0.032246556133031845,
0.12391383200883865,
0.06... | 0.064123 |
The [flux bootstrap git](/flux/cmd/flux\_bootstrap\_git/) command deploys the Flux controllers on a Kubernetes cluster and configures the controllers to sync the cluster state from a Git repository. Besides installing the controllers, the bootstrap command pushes the Flux manifests to the Git repository and configures ... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/generic-git-server.md | main | fluxcd | [
-0.0247198399156332,
-0.0640796422958374,
-0.003614718560129404,
0.01977415382862091,
0.07956723868846893,
0.0016219826648011804,
0.012140083126723766,
0.062017373740673065,
0.00893581286072731,
0.04822898283600807,
0.021394828334450722,
-0.050846368074417114,
0.06869188696146011,
0.034610... | 0.173459 |
used to reconcile the target cluster. To control multiple clusters from the same Git repository, you have to set a unique path per cluster e.g. `clusters/staging` and `clusters/production`: ```sh ./clusters/ ├── staging # <- path=clusters/staging │ └── flux-system # <- namespace dir generated by bootstrap │ ├── gotk-co... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/generic-git-server.md | main | fluxcd | [
-0.028456246480345726,
-0.07765404134988785,
0.018334636464715004,
0.037093762308359146,
0.09412713348865509,
-0.022077267989516258,
0.01101160142570734,
0.038849931210279465,
0.055347226560115814,
0.0016671926714479923,
-0.028944125398993492,
-0.09033822268247604,
0.08730118721723557,
0.0... | 0.152346 |
To install Flux on an AKS cluster using an Azure DevOps Git repository as the source of truth, you can use the [`flux bootstrap git`](generic-git-server.md) command. {{% alert color="danger" title="Required permissions" %}} To bootstrap Flux, the person running the command must have \*\*cluster admin rights\*\* for the... | https://github.com/fluxcd/website/blob/main/content/en/flux/installation/bootstrap/azure-devops.md | main | fluxcd | [
-0.021364761516451836,
-0.02751302905380726,
-0.00490503991022706,
0.02549353986978531,
0.05200514942407608,
0.016662076115608215,
0.030206922441720963,
-0.00237566651776433,
0.061465632170438766,
0.104994036257267,
-0.017831265926361084,
-0.0669386237859726,
0.04799694940447807,
0.0756782... | 0.13955 |
The Flux APIs integrate with the following Google Cloud Platform (GCP) services: - The source-controller integrates the [OCIRepository](/flux/components/source/ocirepositories/) API with [Google Cloud Artifact Registry (GAR)](https://cloud.google.com/artifact-registry/docs/overview) for pulling OCI artifacts into the c... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/gcp.md | main | fluxcd | [
-0.11498245596885681,
-0.032156944274902344,
0.02669103816151619,
-0.0005251896800473332,
0.1073736771941185,
-0.10668496787548065,
0.010499921627342701,
0.002601268235594034,
-0.006965844426304102,
-0.01861819252371788,
0.012549390085041523,
-0.056406419724226,
0.08268170058727264,
0.0111... | 0.148042 |
inside that folder will inherit the grant. > \*\*Reminder\*\*: The grant relationship has \*three\* involved entities: > - The identity that will use the permissions to perform actions. > - The resource that will be the target of the actions. > - The role containing the permissions required for the actions. ### Grantin... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/gcp.md | main | fluxcd | [
-0.07940135896205902,
-0.016923341900110245,
0.051560234278440475,
-0.055095188319683075,
-0.041615765541791916,
0.04113931581377983,
0.14613895118236542,
-0.051800768822431564,
0.07392731308937073,
0.06784222275018692,
-0.02598143368959427,
-0.10109381377696991,
0.047667767852544785,
0.00... | 0.098525 |
recommended roles and permissions for enabling the Flux integrations with GCP services. ### For Google Cloud Artifact Registry The `OCIRepository`, `ImageRepository` and `ImagePolicy` Flux APIs are integrated with GAR. The `OCIRepository` API can be used to pull OCI artifacts from GAR repositories into the cluster, whi... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/gcp.md | main | fluxcd | [
-0.08333374559879303,
-0.026006244122982025,
0.035794369876384735,
-0.026535766199231148,
0.028587566688656807,
-0.07582420855760574,
0.017147473990917206,
-0.015497518703341484,
-0.05335412546992302,
-0.00648320559412241,
0.015320929698646069,
-0.07069072872400284,
0.06622744351625443,
0.... | 0.089688 |
permissions to the IAM Principal on the target remote cluster. The resulting set of permissions granted to the IAM Principal will be the union of the permissions granted via Kubernetes RBAC with the permissions granted via IAM roles. In GCP a GKE cluster is regarded as a project-level resource, so IAM roles granting ac... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/gcp.md | main | fluxcd | [
0.00017806555842980742,
0.01828523725271225,
0.011489972472190857,
-0.013022261671721935,
-0.03761758282780647,
0.005754151381552219,
0.020115278661251068,
-0.017578905448317528,
0.010538104921579361,
0.03248509392142296,
-0.024714291095733643,
-0.12473323941230774,
0.03718464821577072,
0.... | 0.097274 |
and [non-GKE](https://cloud.google.com/iam/docs/workload-identity-federation-with-kubernetes) clusters. In GKE Autopilot, Workload Identity Federation is always enabled, no cluster setup is required. In GKE Standard, follow these [docs](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#enable\_on... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/gcp.md | main | fluxcd | [
-0.01865472085773945,
0.004745046608150005,
0.04295913875102997,
-0.020651547238230705,
-0.0026307234074920416,
-0.014122366905212402,
0.06328170001506805,
-0.028371961787343025,
0.01761968992650509,
0.04976462200284004,
-0.01172043289989233,
-0.13388633728027344,
0.06253582239151001,
-0.0... | 0.126552 |
- [`iam service-accounts keys create`](https://cloud.google.com/sdk/gcloud/reference/iam/service-accounts/keys/create) Configuring Flux to use a GCP Service Account Key can be done either [at the object level](#at-the-object-level) or [at the controller level](#at-the-controller-level). ### At the object level All the ... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/gcp.md | main | fluxcd | [
-0.06135975196957588,
-0.046704113483428955,
-0.007245148066431284,
-0.049574125558137894,
-0.020991288125514984,
0.01617758348584175,
0.09597260504961014,
-0.009885364212095737,
0.03751010820269585,
0.05068323388695717,
-0.0001863904035417363,
-0.09876105189323425,
0.13042235374450684,
0.... | 0.129347 |
provider from the metadata in the SOPS-encrypted Secret. The key inside the `.data` field of the Secret must be `sops.gcp-kms`. ### At the controller level All the Flux APIs support configuring authentication at the controller level. This is more appropriate for single-tenant scenarios, where all the Flux resources ins... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/gcp.md | main | fluxcd | [
-0.036287304013967514,
-0.013612796552479267,
0.023292260244488716,
-0.010837859474122524,
0.042790737003088,
0.029239438474178314,
0.07397336512804031,
0.01356186717748642,
0.026585260406136513,
0.01640946976840496,
-0.006602807901799679,
-0.045087993144989014,
0.07297486811876297,
0.0446... | 0.067812 |
apiVersion: v1 kind: ConfigMap metadata: name: some-controller-workload-identity-federation namespace: flux-system data: credential-configuration.json: | { "universe\_domain": "googleapis.com", "type": "external\_account", "audience": "//iam.googleapis.com/projects/PROJECT\_NUMBER/locations/global/workloadIdentityPools... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/gcp.md | main | fluxcd | [
-0.061509475111961365,
-0.020861143246293068,
-0.0026014551986008883,
-0.022345269098877907,
0.030988195911049843,
-0.04995264112949371,
0.02022385597229004,
0.010127466171979904,
0.00866441335529089,
0.03978467732667923,
-0.017464958131313324,
-0.10765837877988815,
0.04186520725488663,
0.... | 0.063954 |
The tables below show the compatibility matrix for Flux running inside a \*source cluster\* aiming to get access to resources in a \*target cloud provider\* using secret-less authentication. For each target cloud provider, you can find the authentication docs here: - [AWS](aws.md#authentication) - [Azure](azure.md#auth... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/cross-cloud.md | main | fluxcd | [
-0.033071454614400864,
-0.04137525334954262,
-0.008605177514255047,
-0.03323743864893913,
0.06404385715723038,
0.04867705702781677,
0.02234466001391411,
-0.012770689092576504,
0.023394888266921043,
0.047519877552986145,
-0.005191628821194172,
-0.08391232788562775,
0.10242978483438492,
0.01... | 0.074338 |
that allow customizing the Issuer URL and JWKS URI of the cluster's \*service account token issuer\*. See [docs](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#service-account-issuer-discovery). These flags are: - `--service-account-issuer`: Allows setting the `issuer` field returne... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/cross-cloud.md | main | fluxcd | [
-0.011224898509681225,
0.030366621911525726,
0.00637915451079607,
0.011790052056312561,
0.0035733638796955347,
0.00743119977414608,
0.02126207761466503,
-0.026882944628596306,
0.06930436193943024,
0.03627391904592514,
-0.04010450839996338,
-0.02586737833917141,
0.0033437847159802914,
-0.00... | 0.229352 |
be publicly accessible. 8. Test that the JWKS document was correctly uploaded by `curl`ing the URL you created. For example, if you decide to use AWS S3, the `curl` command should look like this: `curl https://s3.amazonaws.com//openid/v1/jwks`. The output should be the JWKS document you uploaded. 9. Finally, update the... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/cross-cloud.md | main | fluxcd | [
-0.042532116174697876,
0.04986994341015816,
-0.017066359519958496,
-0.016270600259304047,
-0.0013673527864739299,
-0.029194258153438568,
-0.11113952845335007,
-0.0700230747461319,
0.1542619913816452,
0.07445403188467026,
-0.0026538672391325235,
-0.037210915237665176,
-0.018769413232803345,
... | 0.027104 |
The Flux APIs integrate with the following Amazon Web Services (AWS) services: - The source-controller integrates the [OCIRepository](/flux/components/source/ocirepositories/) API with [Amazon Elastic Container Registry (ECR)](https://docs.aws.amazon.com/AmazonECR/latest/userguide/what-is-ecr.html) for pulling OCI arti... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/aws.md | main | fluxcd | [
-0.06961193680763245,
-0.009109556674957275,
-0.02963337115943432,
0.019000345841050148,
0.1735663115978241,
-0.10093062371015549,
-0.030655549839138985,
0.06047461926937103,
0.03943454846739769,
-0.01708139479160309,
0.006125480867922306,
-0.07706758379936218,
0.07146666198968887,
0.01708... | 0.219346 |
example, the `AmazonS3ReadOnlyAccess` policy above uses the wildcard `\*` to allow access to all S3 resources. This is not recommended, as it violates the [Least Privilege Principle](https://en.wikipedia.org/wiki/Principle\_of\_least\_privilege). The recommended way of granting permissions to Flux is to use specific AR... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/aws.md | main | fluxcd | [
-0.06350380182266235,
0.005328673403710127,
-0.047488488256931305,
-0.008793547749519348,
0.07223840802907944,
-0.002196942688897252,
0.06763534992933273,
-0.032278988510370255,
0.00925921555608511,
0.012535642832517624,
-0.038645584136247635,
-0.04137708246707916,
0.06899384409189224,
0.0... | 0.117842 |
IAM Role with a trust policy using ACK, you can use the following custom resource (look for the `spec.assumeRolePolicyDocument` field): - [`Role`](https://aws-controllers-k8s.github.io/community/reference/iam/v1alpha1/role/) To create an IAM Role with a trust policy using Terraform/OpenTofu, you can use the following r... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/aws.md | main | fluxcd | [
-0.028712444007396698,
0.04096810519695282,
-0.022983461618423462,
0.005721732508391142,
-0.003040001494809985,
-0.046665117144584656,
0.0564311258494854,
-0.030026178807020187,
-0.011442904360592365,
0.09309300035238266,
0.03869049623608589,
-0.13848990201950073,
0.08804843574762344,
-0.0... | 0.060452 |
bucket is: - [`aws\_s3\_bucket\_policy`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3\_bucket\_policy) The `aws` CLI command for attaching an inline permission policy to an S3 bucket is: - [`aws s3api put-bucket-policy`](https://docs.aws.amazon.com/cli/latest/reference/s3api/put-bucket... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/aws.md | main | fluxcd | [
-0.034423377364873886,
0.004864908289164305,
-0.027348985895514488,
-0.02474302612245083,
0.07622851431369781,
-0.0362682081758976,
-0.013598483055830002,
-0.04379633441567421,
-0.013912582769989967,
0.07958861440420151,
0.013276567682623863,
-0.06760755181312561,
0.062045782804489136,
0.0... | 0.104439 |
cluster. Optionally, the Access Entry can also have [Access Policies](https://docs.aws.amazon.com/eks/latest/userguide/access-policy-permissions.html), which are predefined sets of Kubernetes permissions defined by EKS. The resulting set of permissions granted to the IAM Role or User will be the union of: 1) the permis... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/aws.md | main | fluxcd | [
0.009433778002858162,
0.04671687260270119,
-0.03225081413984299,
0.05324443802237511,
-0.027043676003813744,
0.04468701779842377,
0.03344457596540451,
-0.06507820636034012,
0.06644371151924133,
0.048186369240283966,
-0.027448885142803192,
-0.05858854576945305,
0.04633180424571037,
0.016699... | 0.182368 |
always enabled, no cluster setup is required. In standard EKS, follow these [docs](https://docs.aws.amazon.com/eks/latest/userguide/pod-id-agent-setup.html). Next, to [link an IAM Role with a Kubernetes Service Account of a Flux controller in Pod Identity](https://docs.aws.amazon.com/eks/latest/userguide/pod-id-associa... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/aws.md | main | fluxcd | [
-0.019076207652688026,
0.0036597102880477905,
0.015824809670448303,
0.04952565208077431,
-0.0019685248844325542,
0.026624517515301704,
0.006759060081094503,
-0.034860096871852875,
0.07022344321012497,
0.07834949344396591,
0.020136944949626923,
-0.1015101820230484,
0.06937529146671295,
0.03... | 0.19699 |
[here](#allowing-kubernetes-service-accounts-to-assume-iam-roles-trust-policies) how to create/attach trust policies to IAM Roles. 2. \*\*Annotate the Kubernetes Service Account with the IAM Role ARN.\*\* This is done by adding the annotation `eks.amazonaws.com/role-arn: arn:aws:iam::ACCOUNT\_ID:role/ROLE\_NAME` to the... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/aws.md | main | fluxcd | [
-0.06268464028835297,
-0.003873715875670314,
-0.004671088885515928,
-0.024067426100373268,
0.01246853917837143,
0.01620682142674923,
0.10367695987224579,
-0.033593665808439255,
0.05416172370314598,
0.07917839288711548,
-0.011143798008561134,
-0.13031569123268127,
0.0830255001783371,
0.0570... | 0.148401 |
with a seamless experience. #### For IAM User Access Keys Only the S3 and KMS integrations support configuring authentication through an IAM User Access Key at the object level. For configuring authentication through an IAM User Access Key, the `.spec.secretRef.name` field must be set to the name of the Kubernetes Secr... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/aws.md | main | fluxcd | [
-0.047439638525247574,
0.021440967917442322,
0.01705940067768097,
-0.030937407165765762,
-0.003997332416474819,
-0.01367222610861063,
0.06738517433404922,
0.01013986486941576,
0.08019807189702988,
0.049485333263874054,
-0.004988147411495447,
-0.11147309094667435,
0.07919245958328247,
-0.03... | 0.110939 |
kind: Deployment name: "(some-controller)" patch: | - op: add path: /spec/template/spec/containers/0/env/- value: name: AWS\_REGION value: AWS\_REGION # This is the region of the AWS STS endpoint. - op: add path: /spec/template/spec/containers/0/env/- value: name: AWS\_ROLE\_ARN value: arn:aws:iam::ACCOUNT\_ID:role/ROL... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/aws.md | main | fluxcd | [
0.0323406457901001,
0.04423408582806587,
-0.05815540999174118,
-0.027387816458940506,
0.02671298384666443,
-0.0036682672798633575,
0.05544774606823921,
0.026498788967728615,
0.01592731662094593,
0.0672510415315628,
-0.009905225597321987,
-0.10105273127555847,
0.010513230226933956,
0.025175... | 0.126487 |
The Flux APIs integrate with the following Microsoft Azure services: - The source-controller integrates the [OCIRepository](/flux/components/source/ocirepositories/) API with [Azure Container Registry (ACR)](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-intro) for pulling OCI artifacts i... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/azure.md | main | fluxcd | [
-0.08746892958879471,
-0.02392360381782055,
-0.05591084063053131,
0.04954665154218674,
0.14216570556163788,
-0.08211958408355713,
0.028677362948656082,
0.056774672120809555,
0.02372494712471962,
0.016471169888973236,
0.04014509171247482,
-0.06897000223398209,
0.08141408860683441,
0.0664360... | 0.220659 |
Azure Storage blob containers and data", "id": "/providers/Microsoft.Authorization/roleDefinitions/2a2b9908-6ea1-4ae2-8e65-a410df84e7d1", "name": "2a2b9908-6ea1-4ae2-8e65-a410df84e7d1", "permissions": [ { "actions": [ "Microsoft.Storage/storageAccounts/blobServices/containers/read", "Microsoft.Storage/storageAccounts/b... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/azure.md | main | fluxcd | [
0.03171084076166153,
0.013150773011147976,
-0.04251435771584511,
0.036674730479717255,
-0.04455083981156349,
0.005589987151324749,
0.1026952937245369,
-0.06275775283575058,
0.03513238951563835,
0.07056397199630737,
0.013234015554189682,
-0.08024195581674576,
0.06304675340652466,
0.05130261... | -0.022591 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.