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 |
|---|---|---|---|---|---|
Azure > resources. If you need continuous reconciliation of the resources, prefer using > ASO or Terraform/OpenTofu. ## Authorization In this section we describe the recommended roles and permissions for enabling the Flux integrations with Azure services. ### For Azure Container Registry The `OCIRepository`, `ImageRepo... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/azure.md | main | fluxcd | [
-0.038009725511074066,
0.015996180474758148,
-0.06188151612877846,
0.039805371314287186,
0.10878486931324005,
-0.08982496708631516,
0.02401331625878811,
-0.01408182643353939,
0.03461391478776932,
0.005045023281127214,
0.007079605478793383,
-0.060000307857990265,
0.08910340815782547,
0.1055... | 0.137967 |
API is integrated with ABS. The `Bucket` API can be used to pull manifests from ABS containers and package them as artifacts inside the cluster. The recommended role containing the required permissions for the `Bucket` API is: - [Storage Blob Data Reader (`/providers/Microsoft.Authorization/roleDefinitions/2a2b9908-6ea... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/azure.md | main | fluxcd | [
0.010622136294841766,
-0.008741519413888454,
-0.0577470101416111,
0.03039364516735077,
-0.013202270492911339,
-0.0028400951996445656,
0.04205998405814171,
-0.02199530228972435,
-0.0038092657923698425,
0.02757684513926506,
-0.00161131308414042,
-0.044837526977062225,
0.09480517357587814,
0.... | 0.059212 |
to Microsoft Entra identity on the following scopes: - Namespace: `/subscriptions/SUBSCRIPTION\_ID/resourceGroups/RESOURCE\_GROUP\_NAME/providers/Microsoft.ContainerService/managedClusters/CLUSTER\_NAME/namespaces/NAMESPACE\_NAME` - Cluster: `/subscriptions/SUBSCRIPTION\_ID/resourceGroups/RESOURCE\_GROUP\_NAME/provider... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/azure.md | main | fluxcd | [
-0.0517648346722126,
-0.016792569309473038,
-0.09920157492160797,
0.046780772507190704,
0.005748718976974487,
0.01429967675358057,
0.06281065940856934,
-0.1006915494799614,
0.03103761374950409,
0.07158482819795609,
0.02202792838215828,
-0.10059390962123871,
0.09045334905385971,
0.082653045... | 0.133451 |
[Issuer URL](cross-cloud.md#source-cluster-setup) of the cluster. - The Subject string that Kubernetes uses to identify the Service Account, which is `system:serviceaccount:NAMESPACE:KSA\_NAME`. Additionally, the Federated Credential needs: - A name for itself. - The \*Audience\* to be set to `api://AzureADTokenExchang... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/azure.md | main | fluxcd | [
-0.004644840955734253,
-0.04692814126610756,
-0.03183235228061676,
-0.005438854452222586,
-0.08627033978700638,
0.04622553661465645,
0.024854350835084915,
-0.03375643491744995,
0.0810365229845047,
0.10886363685131073,
-0.06680575013160706,
-0.1641148030757904,
0.07643869519233704,
0.016410... | 0.11238 |
the referenced `ConfigMap` from `.spec.kubeConfig.configMapRef`. 3. Use the `.spec.serviceAccountName` field to specify the name of the Kubernetes Service Account in the same namespace as the Flux resource. For SOPS decryption with the `Kustomization` API, the field is `.spec.decryption.serviceAccountName`. For remote ... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/azure.md | main | fluxcd | [
-0.05544529855251312,
0.042138632386922836,
-0.008920008316636086,
0.005603019148111343,
0.024521708488464355,
0.009798899292945862,
0.10274358093738556,
-0.03064599819481373,
0.11879602819681168,
0.04720064252614975,
-0.022508570924401283,
-0.08953191339969635,
0.06439583748579025,
0.0340... | 0.201128 |
azure.workload.identity/client-id: CLIENT\_ID azure.workload.identity/tenant-id: TENANT\_ID - target: kind: Deployment name: "(some-controller)" patch: | apiVersion: apps/v1 kind: Deployment metadata: name: (some-controller) spec: template: metadata: labels: azure.workload.identity/use: "true" ``` If the configuration ... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/azure.md | main | fluxcd | [
-0.04503466933965683,
0.00783078558743,
0.006204161327332258,
0.017481965944170952,
-0.0034546945244073868,
0.06532727181911469,
0.0404503233730793,
-0.03280426934361458,
0.06454000622034073,
0.09912745654582977,
-0.0003394650120753795,
-0.03206377476453781,
0.07937852293252945,
0.04785083... | 0.091505 |
point to a JSON configuration file mounted into the controller pod that defines the custom Azure endpoints. An example configuration file with the list of custom endpoints supported by Flux is shared below. ```json { "resourceManagerEndpoint": "https://management.core.private/", "tokenAudience": "https://management.cor... | https://github.com/fluxcd/website/blob/main/content/en/flux/integrations/azure.md | main | fluxcd | [
0.005747659131884575,
-0.0407128781080246,
-0.050882842391729355,
0.03558313101530075,
0.03102705627679825,
0.0675564706325531,
0.0037477687001228333,
0.00921756960451603,
0.056535754352808,
0.11511552333831787,
-0.010224482975900173,
-0.049790091812610626,
0.04216361790895462,
0.118352375... | 0.107352 |
Flux is constructed with the GitOps Toolkit components, which is a set of - specialized tools and Flux Controllers - composable APIs - reusable Go packages for GitOps under the [fluxcd GitHub organisation](https://github.com/fluxcd) for building Continuous Delivery on top of Kubernetes. . ## Flags | Name | Type | Description | |---------------------------------------|---------------|----------------------------------------------------------------... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/notification/options.md | main | fluxcd | [
-0.015619626268744469,
-0.02878192998468876,
-0.048410963267087936,
0.0008619105792604387,
0.10213730484247208,
0.05241764709353447,
0.006161751691251993,
0.051868170499801636,
0.008173754438757896,
0.03888462111353874,
0.03809148818254471,
-0.026415299624204636,
0.015160851180553436,
0.01... | 0.017955 |
The Notification Controller is a Kubernetes operator, specialized in handling inbound and outbound events.  The controller handles events coming from external systems (GitHub, GitLab, Bitbucket, Harbor, Jenkins, etc) and notifies the GitOps toolkit con... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/notification/_index.md | main | fluxcd | [
-0.0324784554541111,
-0.05547558516263962,
0.00946605671197176,
0.01636643335223198,
0.0989268496632576,
-0.022615978494286537,
0.04337050020694733,
0.052546072751283646,
0.12310504168272018,
0.06855477392673492,
-0.017007874324917793,
-0.043013256043195724,
0.03223647177219391,
-0.0099322... | 0.247937 |
To customise the controller options at install time, please see the [bootstrap customization guide](/flux/installation/configuration/bootstrap-customization/). ## Source controller flags | Name | Type | Description | |---------------------------------------|---------------|----------------------------------------------... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/source/options.md | main | fluxcd | [
-0.019314821809530258,
-0.022113896906375885,
-0.058921754360198975,
-0.0254716444760561,
0.07391133904457092,
0.07683748006820679,
-0.040002014487981796,
0.07228975743055344,
-0.019571810960769653,
0.039903346449136734,
0.015440596267580986,
-0.004464819096028805,
-0.026497434824705124,
-... | -0.029661 |
The list of key exchange algorithms to use for ssh connections, arranged from most preferred to the least. | | `--storage-addr` | string | The address the static file server binds to. (default ":9090") | | `--storage-adv-addr` | string | The advertised address of the static file server. | | `--storage-path` | string | ... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/source/options.md | main | fluxcd | [
0.02044929563999176,
-0.05540449172258377,
-0.09506150335073471,
0.017467211931943893,
-0.0023731107357889414,
-0.049345314502716064,
-0.008912245742976665,
0.039204344153404236,
0.015353956259787083,
-0.0048530553467571735,
0.029016191139817238,
0.03446371853351593,
0.06526605039834976,
-... | 0.169119 |
(default "json") | | `--log-level` | string | Log verbosity level. Can be one of 'trace', 'debug', 'info', 'error'. (default "info") | | `--max-retry-delay` | duration | The maximum amount of time for which an object being reconciled will have to wait before a retry. (default 15m0s) | | `--metrics-addr` | string | The ... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/source/options.md | main | fluxcd | [
-0.09580601751804352,
-0.023112131282687187,
-0.023788094520568848,
0.026607882231473923,
-0.04089302197098732,
-0.057136420160532,
-0.03437241166830063,
0.004414347466081381,
0.04739345610141754,
0.007745324168354273,
0.008541233837604523,
-0.04156211391091347,
-0.01167279202491045,
0.032... | 0.119755 |
## Source controller The main role of source-controller is to provide a common interface for artifacts acquisition. The source API defines a set of Kubernetes objects that cluster admins and various automated operators can interact with to offload the Git and Helm repositories operations to a dedicated controller. . ## Image automation flags | Name | Type | Description | |---------------------------------------|---------------|-----------------------------------------------... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/image/options.md | main | fluxcd | [
-0.02555239200592041,
-0.004107440821826458,
-0.04381405562162399,
-0.012977523729205132,
0.09424512088298798,
0.033065687865018845,
-0.013971274718642235,
0.0899922177195549,
-0.047138944268226624,
0.04873289912939072,
0.06835228204727173,
-0.03011064976453781,
0.014682522974908352,
0.012... | 0.049597 |
of "force push" when pushing changes to a separate branch. This fixes issues with stale push branches. | | `GitSparseCheckout` | `false` | Enables the use of Git sparse checkout to only fetch the path defined in `.spec.update.path` from the repository. | | `ObjectLevelWorkloadIdentity` | `false` | Enables the use of ob... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/image/options.md | main | fluxcd | [
-0.012923747301101685,
-0.08379047363996506,
0.01565038412809372,
0.08137180656194687,
0.009962077252566814,
-0.12715081870555878,
-0.04076296091079712,
-0.00033161748433485627,
0.04743626341223717,
0.05980033054947853,
0.05798506364226341,
-0.001572499517351389,
-0.05858955532312393,
-0.0... | -0.02302 |
cluster-wide RBAC permissions (list and watch). | | `ObjectLevelWorkloadIdentity` | `false` | Enables the use of object-level workload identity for the controller. | | https://github.com/fluxcd/website/blob/main/content/en/flux/components/image/options.md | main | fluxcd | [
-0.06005983054637909,
-0.04900142922997475,
-0.1756860613822937,
0.0791957899928093,
0.01816992461681366,
0.05107617378234863,
0.04348619282245636,
-0.016458898782730103,
-0.026995375752449036,
0.019760029390454292,
-0.016983341425657272,
0.020939357578754425,
0.00228675315156579,
0.038647... | 0.209929 |
The image-reflector-controller and image-automation-controller work together to update a Git repository when new container images are available. - The image-reflector-controller scans image repositories and reflects the image metadata in Kubernetes resources. - The image-automation-controller updates YAML files based o... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/image/_index.md | main | fluxcd | [
-0.06600832939147949,
-0.07174412161111832,
0.053500350564718246,
-0.029341131448745728,
0.11328239738941193,
-0.048916712403297424,
-0.008282133378088474,
0.039362214505672455,
0.038437046110630035,
0.05770834535360336,
0.08291655778884888,
-0.023585772141814232,
0.03316456824541092,
-0.0... | 0.176577 |
To customise the controller options at install time, please see the [bootstrap customization guide](/flux/installation/configuration/bootstrap-customization/). ## Flags | Name | Type | Description | |----------------------------------------|---------------|---------------------------------------------------------------... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/kustomize/options.md | main | fluxcd | [
-0.015174527652561665,
-0.01570432074368,
-0.05752144381403923,
-0.023471390828490257,
0.07374797016382217,
0.0726657584309578,
-0.03619780391454697,
0.07311468571424484,
-0.026974821463227272,
0.03655029833316803,
0.020405225455760956,
-0.005952861160039902,
-0.02467513643205166,
0.007655... | -0.023273 |
The name of a Kubernetes secret in the RUNTIME\_NAMESPACE containing a SOPS age decryption key for fallback usage. | | `--token-cache-max-size` | int | The maximum amount of entries in the LRU cache used for tokens. (default 100, enabled) | | `--token-cache-max-duration` | duration | The maximum duration for which a to... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/kustomize/options.md | main | fluxcd | [
-0.018505623564124107,
-0.017868440598249435,
0.025961654260754585,
0.018461400642991066,
0.0501059927046299,
-0.01477833092212677,
0.012947183102369308,
-0.014546138234436512,
0.07844921201467514,
-0.011934541165828705,
-0.009085962548851967,
-0.0634579136967659,
-0.004371256101876497,
-0... | 0.189432 |
The kustomize-controller is a Kubernetes operator, specialized in running continuous delivery pipelines for infrastructure and workloads defined with Kubernetes manifests and assembled with Kustomize.  Features: - Reconciles the cluster state from multiple s... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/kustomize/_index.md | main | fluxcd | [
-0.051582735031843185,
0.015031849965453148,
-0.024052077904343605,
-0.005464926362037659,
-0.011906753294169903,
0.028063850477337837,
0.006913265213370323,
-0.02057555690407753,
0.06137280911207199,
0.017788084223866463,
0.006902068387717009,
-0.015829645097255707,
0.018479807302355766,
... | 0.265481 |
To customise the controller options at install time, please see the [bootstrap customization guide](/flux/installation/configuration/bootstrap-customization/). ## Flags | Name | Type | Description | |----------------------------------------|---------------|---------------------------------------------------------------... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/helm/options.md | main | fluxcd | [
-0.015174527652561665,
-0.01570432074368,
-0.05752144381403923,
-0.023471390828490257,
0.07374797016382217,
0.0726657584309578,
-0.03619780391454697,
0.07311468571424484,
-0.026974821463227272,
0.03655029833316803,
0.020405225455760956,
-0.005952861160039902,
-0.02467513643205166,
0.007655... | -0.023273 |
to the cgroup current memory usage file. Requires feature gate 'OOMWatch' to be enabled. If not set, the path will be automatically detected. | | `--override-manager` | stringArray | List of field managers to override during drift detection e.g. '--override-manager=kubectl-edit --override-manager=kubectl-patch' | | `--... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/helm/options.md | main | fluxcd | [
0.052004389464855194,
0.027325669303536415,
-0.002356094541028142,
0.013390088453888893,
0.009235609322786331,
-0.03325141221284866,
-0.037526361644268036,
0.013600276783108711,
0.10627906769514084,
0.025211820378899574,
0.012197683565318584,
-0.07862818986177444,
-0.014559227973222733,
-0... | 0.133695 |
| `false` | Restores Helm v3 defaults. When enabled, uses client-side apply for installation, Helm's legacy readiness logic, and the `nohooks` post-render strategy instead of the Helm v4 defaults (server-side apply, kstatus-based health checking, and `combined` post-render strategy). | | https://github.com/fluxcd/website/blob/main/content/en/flux/components/helm/options.md | main | fluxcd | [
-0.001975516090169549,
0.06886570155620575,
0.02819925732910633,
-0.036486536264419556,
0.09944743663072586,
-0.015106307342648506,
-0.1175522580742836,
-0.05350351333618164,
0.013693037442862988,
0.031835947185754776,
0.07175923883914948,
0.03367222473025322,
-0.025190914049744606,
-0.027... | 0.074734 |
The Helm Controller is a Kubernetes operator, allowing one to declaratively manage Helm chart releases with Kubernetes manifests.  The desired state of a Helm release is described through a Kubernetes Custom Resource named `HelmRelease`. Based on the creation, mutatio... | https://github.com/fluxcd/website/blob/main/content/en/flux/components/helm/_index.md | main | fluxcd | [
0.013713188469409943,
0.048577822744846344,
0.03440719097852707,
0.011860867962241173,
0.03504303842782974,
0.017676522955298424,
-0.06710851192474365,
-0.01596553437411785,
0.08699169009923935,
0.11736784130334854,
0.03795180097222328,
-0.007806907407939434,
0.013765010051429272,
-0.06513... | 0.166232 |
{{% alert color="warning" title="Disclaimer" %}} Note that this guide has not been updated since more than a year ago, it does not address Kubernetes 1.24 or above, and needs to be refreshed. Expect this doc to either be archived soon, or to receive an overhaul. {{% /alert %}} This guide explains how to configure Flux ... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/jenkins.md | main | fluxcd | [
-0.006425159517675638,
0.05055742710828781,
0.08452080935239792,
0.03190474957227707,
0.11771213263273239,
-0.05755699425935745,
0.03207813948392868,
0.026546727865934372,
0.0650443509221077,
0.01221444457769394,
-0.04323713481426239,
-0.08843160420656204,
0.11247168481349945,
-0.000793467... | 0.220724 |
Repository Jenkins is responsible for building and testing OCI images. Those images can be tested internally on Jenkins as part of the build, before pushing, or once deployed in a non-production cluster or other staging context. Jenkins workflows are often as varied and complex as a snowflake. Finer points of Jenkins i... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/jenkins.md | main | fluxcd | [
-0.07117939740419388,
0.03798628970980644,
0.04415033012628555,
0.013727942481637001,
0.07976503670215607,
-0.16955091059207916,
-0.05350006744265556,
-0.003299930365756154,
0.06535427272319794,
-0.04804951697587967,
-0.08612064272165298,
-0.05884769558906555,
0.05857593193650246,
0.047777... | 0.171225 |
to explain and show compatible choices that work well with Flux. It should be clear that if we use Jenkins or Docker, or any other competing tool for building images, much of the same advice for working with Flux will still apply. #### What Should We Do? We recommend users implement SemVer and/or [Sortable image tags][... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/jenkins.md | main | fluxcd | [
-0.026515012606978416,
-0.015024028718471527,
0.06404618173837662,
-0.003579953219741583,
0.08016608655452728,
-0.09115567803382874,
-0.0712607130408287,
0.038131263107061386,
-0.02603621408343315,
0.018084365874528885,
-0.049259234219789505,
-0.05171629413962364,
0.038424670696258545,
0.0... | 0.143804 |
and keep it locally for now stage('Build') { steps { container('docker') { script { gitCommit = env.GIT\_COMMIT.substring(0,8) branchName = env.BRANCH\_NAME unixTime = (new Date().time.intdiv(1000)) developmentTag = "${branchName}-${gitCommit}-${unixTime}" developmentImage = "${dockerRepoUser}/${dockerRepoProj}:${devel... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/jenkins.md | main | fluxcd | [
0.048303041607141495,
0.059643447399139404,
0.015690825879573822,
-0.004423241596668959,
0.07116406410932541,
-0.09526580572128296,
-0.05704648047685623,
0.03504052758216858,
0.016889289021492004,
0.06924298405647278,
0.019919000566005707,
-0.07534141838550568,
0.054126378148794174,
0.0264... | -0.074338 |
tests again, and finally on success push a SemVer image tag. #### Example Resources You can find this example tested with a Jenkins instance at [kingdonb/jenkins-example-workflow]; it has been configured to run as you can see from the commit status checks found on all commits, tags, and pull requests. The images are pu... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/jenkins.md | main | fluxcd | [
-0.06381547451019287,
0.010909425094723701,
0.015212208032608032,
0.035217802971601486,
0.08554612100124359,
-0.11123974621295929,
-0.06216888502240181,
-0.019869856536388397,
0.005128136835992336,
0.0064269741997122765,
-0.022454800084233284,
-0.09380220621824265,
0.09772053360939026,
-0.... | 0.175962 |
{{% alert color="warning" title="Disclaimer" %}} This document is under review and may be declared out of scope for Flux. Note that this guide needs further review in consideration of Flux v2.0.0. It also predates the introduction of `OCIRepository` and likely needs updates in consideration of those advancements. Expec... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-app-builder.md | main | fluxcd | [
-0.032915011048316956,
0.029037808999419212,
-0.0155301159247756,
0.04005144163966179,
0.183995321393013,
-0.06810124218463898,
0.03520461916923523,
0.09093383699655533,
0.048082832247018814,
-0.03965209051966667,
-0.003961250651627779,
-0.07426485419273376,
0.1413026601076126,
0.003655846... | 0.158101 |
}} password: ${{ secrets.DOCKERHUB\_TOKEN }} - name: Build and push id: docker\_build uses: docker/build-push-action@v6 with: push: true tags: | ${{ env.IMAGE }}:${{ steps.prep.outputs.BUILD\_ID }} ${{ env.IMAGE }}:${{ steps.prep.outputs.LATEST\_ID }} - name: Image digest run: echo ${{ steps.docker\_build.outputs.diges... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-app-builder.md | main | fluxcd | [
-0.04269222542643547,
0.06957238912582397,
0.00009338614472653717,
0.04038567095994949,
0.08759479224681854,
-0.05601015314459801,
0.009913641028106213,
0.008977035991847515,
0.06888707727193832,
-0.0032280634623020887,
-0.03608901798725128,
-0.08173328638076782,
0.07024398446083069,
0.027... | 0.106924 |
many possible uses for mutable image tags. Another sensible choice could be to build and push canary images only from the `main` branch. This script can be as elaborate as you want, the important logic is all contained in the shell script embedded in the `Prepare` step: ### Prepare Step ```yaml steps: - name: Prepare i... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-app-builder.md | main | fluxcd | [
0.03915172815322876,
0.036176785826683044,
0.02885287068784237,
-0.0024524470791220665,
0.08575119823217392,
-0.05819890648126602,
-0.06952672451734543,
0.03994316980242729,
0.031086057424545288,
0.021488768979907036,
0.02192334085702896,
-0.013592187315225601,
0.05869200453162193,
-0.0459... | 0.016776 |
pushing their updated truth as a new input for a standard GitOps deployment, or using another Git target as an intermediate store that still derives from GitOps intents declared further upstream. So automation can push directly back to a default branch, or we can configure Flux to [Push updates to a different branch] t... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-app-builder.md | main | fluxcd | [
-0.09726840257644653,
-0.044898346066474915,
-0.03842189162969589,
-0.00524272071197629,
0.07148432731628418,
-0.05335095152258873,
0.00019101951329503208,
0.07305432856082916,
0.013274663127958775,
0.04807470366358757,
0.011671426706016064,
-0.04277758300304413,
0.04624151065945625,
0.025... | 0.183365 |
Welcome Helm users! We think Flux's Helm Controller is the best way to do Helm according to GitOps principles, and we're dedicated to doing what we can to help you feel the same way. [Flux supports Helm v4!](https://fluxcd.io/blog/2026/02/flux-v2.8.0/) Stay tuned for updates to this doc for added ways that Flux benefit... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/helm.md | main | fluxcd | [
-0.04902380332350731,
0.021221192553639412,
0.013637689873576164,
-0.03191401809453964,
0.0498066209256649,
0.004962730221450329,
-0.009481308981776237,
0.0857255756855011,
0.07875692844390869,
0.040466565638780594,
-0.04672723636031151,
-0.05814272537827492,
0.02915623039007187,
0.0257313... | 0.213998 |
GitOps](https://youtu.be/r-upyR-cfDY). ## Customizing Your Release While Helm charts are usually installable using default configurations, users will often customize charts with their preferred configuration by [overriding the default values](https://helm.sh/docs/intro/using\_helm/#customizing-the-chart-before-installi... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/helm.md | main | fluxcd | [
-0.03367159888148308,
0.061755597591400146,
-0.023614957928657532,
-0.03700460121035576,
-0.02319813147187233,
-0.03437681868672371,
0.005049291532486677,
0.07487600296735764,
0.037081725895404816,
0.052970949560403824,
0.05384945496916771,
-0.02268381416797638,
-0.005170163232833147,
-0.0... | 0.100204 |
the Helm rollback action rollback: timeout: 5m disableWait: false disableHooks: false recreate: false force: false cleanupOnFail: false ``` ## Next Steps - [Guides > Manage Helm Releases](../guides/helmreleases.md) - [Toolkit Components > Helm Controller](../components/helm/\_index.md) - [Migration > Migrate to the Hel... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/helm.md | main | fluxcd | [
0.027153948321938515,
0.05954889580607414,
0.013106361962854862,
0.017852315679192543,
0.08616816252470016,
-0.009650514461100101,
-0.08815018087625504,
-0.06372005492448807,
0.015098512172698975,
0.06715432554483414,
0.08473553508520126,
0.07495719939470291,
-0.0201864056289196,
-0.056785... | -0.009949 |
This guide shows how to configure Flux and GitHub Actions to promote Helm Releases across environments when a new Helm chart version is available.  For this guide we assume a scenario with two clusters: staging and production; with the following... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-helm-promotion.md | main | fluxcd | [
-0.014032691717147827,
-0.0694160982966423,
0.050642259418964386,
-0.03831718489527702,
0.11729452759027481,
-0.011094728484749794,
-0.07787096500396729,
0.011588085442781448,
0.022310951724648476,
0.025360723957419395,
0.02658720314502716,
-0.033016592264175415,
0.0445745512843132,
-0.001... | 0.100942 |
echo VERSION=${VERSION} >> $GITHUB\_OUTPUT # Patch the chart version in the production Helm release manifest. - name: Set chart version in production id: production env: CHART\_VERSION: ${{ steps.staging.outputs.version }} run: | echo "set chart version to ${CHART\_VERSION}" yq eval '.spec.chart.spec.version=env(CHART\... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-helm-promotion.md | main | fluxcd | [
0.039591554552316666,
0.01968521624803543,
0.042154815047979355,
-0.02140192873775959,
0.0809217095375061,
0.005386189091950655,
-0.07476847618818283,
-0.0036437001544982195,
0.025826595723628998,
0.04100007936358452,
0.04475191608071327,
-0.025447936728596687,
-0.013665757142007351,
-0.04... | 0.035614 |
corresponding OCI digest. - Patches the digest in the `OCIRepository` manifest at `clusters/production/apps/demo.yaml`. - Creates a new branch called `demo-promotion`, commits the version change and opens a Pull Request against `main`. \*\*Note\*\* that you should adapt the workflow to match your release name, namespac... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-helm-promotion.md | main | fluxcd | [
-0.010535966604948044,
-0.04518325626850128,
0.03291350230574608,
-0.014617947861552238,
0.12395385652780533,
-0.07648467272520065,
-0.04636264964938164,
0.012566226534545422,
0.05713499337434769,
0.040222425013780594,
0.015892360359430313,
-0.07244767993688583,
0.012936324812471867,
-0.01... | 0.172181 |
Additional considerations have to be made when managing Kubernetes Jobs with Flux. By default, if you were to have Flux reconcile a Job resource, it would apply it once to the cluster, the Job would create a Pod that can either error or run to completion. Attempting to update the Job manifest after it has been applied ... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/running-jobs.md | main | fluxcd | [
-0.06461331993341446,
-0.0492846816778183,
0.05785922333598137,
-0.0206266138702631,
0.02867022715508938,
0.006148181390017271,
-0.008184253238141537,
-0.015711260959506035,
0.00941087119281292,
0.040836405009031296,
-0.0646900162100792,
-0.021133972331881523,
0.011046278290450573,
0.02703... | 0.2167 |
{{% alert color="warning" title="Disclaimer" %}} Note that this guide is not for doing GitOps, but for managing Helm releases for applications among multiple clusters. Also note that this guide needs review in consideration of Flux v2.0.0, and likely needs to be refreshed. Expect this doc to either be archived soon, or... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/karmada.md | main | fluxcd | [
-0.004693539813160896,
-0.029996534809470177,
0.014926652424037457,
0.007363240234553814,
0.08587624132633209,
-0.029669176787137985,
-0.014752056449651718,
0.01609424687922001,
0.036341238766908646,
0.03943159803748131,
-0.04072710499167442,
-0.05032004788517952,
0.05377752706408501,
-0.0... | 0.165628 |
is similar to: ``` helmrelease.helm.toolkit.fluxcd.io/podinfo created helmrepository.source.toolkit.fluxcd.io/podinfo created propagationpolicy.policy.karmada.io/helm-release created propagationpolicy.policy.karmada.io/helm-repo created ``` 4. Switch to the distributed cluster and verify: ```sh helm --kubeconfig ~/.kub... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/karmada.md | main | fluxcd | [
-0.008316703140735626,
-0.03056253492832184,
0.02075447142124176,
-0.006555413827300072,
0.04170097038149834,
-0.012336548417806625,
-0.040126506239175797,
-0.03221087530255318,
0.03152221813797951,
0.07275357097387314,
0.022974325343966484,
-0.0606563575565815,
0.03965777903795242,
-0.064... | 0.122419 |
This guide shows how to configure GitHub Actions to open a pull request whenever a selected branch is pushed. From [Image Update Guide] we saw that Flux can set `.spec.git.push.branch` to [Push updates to a different branch] than the one used for checkout. Configure an `ImageUpdateAutomation` resource to push to a targ... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-auto-pr.md | main | fluxcd | [
-0.01797175407409668,
-0.07354476302862167,
0.010929929092526436,
-0.0016335368854925036,
0.07781457155942917,
-0.05466097593307495,
-0.00005826873893965967,
0.0754445269703865,
0.010937320999801159,
0.07912176847457886,
0.02624410390853882,
-0.03142603859305382,
0.05687912181019783,
0.049... | 0.146077 |
{{% alert color="warning" title="Disclaimer" %}} This document is under review and may be declared out of scope for Flux. Note that this guide no longer describes the recommended way to handle manifest generation in Flux. It also predates the introduction of `OCIRepository` and needs updates in consideration of those a... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.04640345647931099,
0.09437742084264755,
-0.02452785335481167,
0.0788378193974495,
0.12649981677532196,
-0.06751760840415955,
0.0907696932554245,
0.09796883910894394,
0.04746188968420029,
-0.061376817524433136,
-0.025685373693704605,
-0.07699412852525711,
0.1222681775689125,
0.0388225391... | 0.147714 |
Flux; the goal of this guide is to show several common use cases of this pattern in secure ways. #### Demonstrated Concepts It is intended, finally, to show through this use case, three fundamental ideas for use in CI to accompany Flux automation: 1. Writing workflow that can commit changes back to the same branch of a... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.14293304085731506,
-0.014927353709936142,
-0.030333641916513443,
-0.013052846305072308,
0.014787047170102596,
-0.0319424644112587,
0.02074960619211197,
0.05628187581896782,
0.03835640102624893,
0.01024648081511259,
-0.007439968641847372,
-0.05494490638375282,
0.12293896079063416,
0.0508... | 0.230086 |
the build. ```bash # excerpt from above - set two outputs named "VERSION" and "BUILD\_DATE" VERSION=${GITHUB\_SHA::8} echo BUILD\_DATE=$(date -u +'%Y-%m-%dT%H:%M:%SZ') >> $GITHUB\_OUTPUT echo VERSION=${VERSION} >> $GITHUB\_OUTPUT ``` {{% alert title="When migrating to Flux v2" %}} Users will find that [some guidance ha... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.03533206135034561,
-0.007871019653975964,
0.021322762593626976,
0.031993117183446884,
0.1434510201215744,
-0.019131707027554512,
-0.027283303439617157,
0.0683952122926712,
0.00456153554841876,
-0.030515270307660103,
0.02510286122560501,
-0.020534714683890343,
0.09331026673316956,
0.0394... | 0.075037 |
From the Actions marketplace, [Build and push Docker images] provides the heavy lifting in this example. Flux has nothing to do with building images, but we include this still — as some images will need to be built for our use in these examples. {{% alert title="ImageRepository can reflect both branches and tags" %}} T... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.021416038274765015,
0.022533856332302094,
-0.0032334248535335064,
0.01834135316312313,
0.07862093299627304,
-0.033243559300899506,
0.003946011420339346,
0.08739655464887619,
0.05786231532692909,
0.01530034001916647,
0.0065301950089633465,
-0.0798049345612526,
0.101130910217762,
0.011369... | 0.114813 |
/alert %}} It is advisable to protect repository main and release branches with eg. branch policies and review requirements, as through automation, these branches can directly represent the production environment. The CI user for this example should be allowed to push directly to the `deploy` branch that Kustomize depl... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.01636054925620556,
0.00460549583658576,
0.018468370661139488,
-0.01782333478331566,
0.059790439903736115,
-0.037947576493024826,
0.008725127205252647,
-0.020696980878710747,
0.059109270572662354,
0.06367101520299911,
0.07925118505954742,
0.015432159416377544,
0.05580983683466911,
0.0243... | 0.161995 |
$BRANCH git checkout $BRANCH -- # Prepare the output to commit by itself in the deploy branch's root directory. mv -f ./production.yaml ../ # Overwrite any existing files (no garbage collection here) git diff # All done (the commit will take place in the next action!) popd ``` Give this file `chmod +x` before adding an... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
0.030222682282328606,
0.015649890527129173,
0.032927438616752625,
0.005067058838903904,
0.06106072664260864,
-0.03983866795897484,
-0.01985514909029007,
0.0009541941108182073,
0.058424320071935654,
0.07304055243730545,
0.03845129534602165,
0.018999718129634857,
0.004064730368554592,
0.0137... | 0.040346 |
namespaces, some RBAC configuration may be required. When you write a `Kustomization` to apply this, be sure you are aware of whether or not you have set `targetNamespace` on the Flux `Kustomization` as it may override any namespace settings in the Jsonnet output. You may note similar configuration in the `kustomizatio... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.0698164626955986,
-0.056120071560144424,
-0.004192347638309002,
-0.02421138808131218,
0.008120204322040081,
-0.01552083995193243,
-0.011250211857259274,
0.013128752820193768,
0.002951566129922867,
0.00853718165308237,
0.04622609540820122,
-0.045554179698228836,
0.02349034883081913,
0.09... | 0.125374 |
These examples are going to get progressively more advanced as I learn Jsonnet while I go. At this point I already think it's pretty cool and I barely know how to use it, but I am starting to understand what type of problems people are using it to solve. ConfigMap values are not treated as secret data, so there is no e... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.07915762811899185,
0.007988620549440384,
0.018407704308629036,
0.01741098426282406,
0.05457586795091629,
-0.07231060415506363,
-0.0023984878789633512,
-0.0008443077676929533,
0.0002342052903259173,
-0.01559338066726923,
0.024388467893004417,
-0.043243419378995895,
0.02873414009809494,
0... | 0.130172 |
taken my word for it.) But now, these two differ. We're creating two configurations for `any\_old\_app`, named `test` and `prod`. One of them has `prune` enabled, the test environment, and `prod` is set more conservatively to prevent accidental deletions, with a setting of `prune: false`. Since the two environments sho... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.06194467097520828,
0.07008984684944153,
0.04965797811746597,
0.0035711508244276047,
0.14164935052394867,
-0.02906617522239685,
0.0010960351210087538,
0.035405680537223816,
0.005853898357599974,
-0.03259442374110222,
0.0632806047797203,
0.01950353942811489,
-0.0078500397503376,
-0.017948... | 0.092222 |
then false else true, }, }, } for ns in items // Credit: // https://groups.google.com/g/jsonnet/c/ky6sjYj4UZ0/m/d4lZxWbhAAAJ // thanks Dave for showing how to do something like this in Jsonnet }, } ``` This is the sixth revision of this example, (some have been omitted from the story, but they are [in Git history][exam... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.08182663470506668,
0.07795342803001404,
0.015107828192412853,
0.024312522262334824,
0.05911271274089813,
-0.08484548330307007,
0.06438372284173965,
-0.042388711124658585,
0.008789991028606892,
0.010068437084555626,
0.06944256275892258,
0.027491135522723198,
0.05561567842960358,
0.064307... | 0.126087 |
is called): ```javascript local items = ['test', 'prod'], joined: { [ns + '\_flux\_kustomization']: { data: example.any\_old\_app(ns) { spec+: { prune: if ns == 'prod' then false else true, }, }, } for ns in items }, ``` Two `any\_old\_app` templates are invoked programmatically, with different properties and names, an... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.06637219339609146,
0.048759620636701584,
0.04599587619304657,
0.003016580594703555,
0.07917217165231705,
-0.061882562935352325,
0.00749514764174819,
-0.0008500728872604668,
0.060429103672504425,
-0.010883638635277748,
0.07859726250171661,
0.025193162262439728,
-0.03370078280568123,
0.01... | 0.187708 |
Imagine that two policies should exist for promoting releases into environments. The environments for `dev`elopment, `U`ser `A`cceptance `T`esting (`uat`), and `Q`uality `A`ssurance (`qa`) can all be primed with the latest release candidate build at any given time. This is perhaps an excessive amount of formality for a... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.03882424160838127,
-0.05666666850447655,
0.07123295962810516,
-0.060386478900909424,
0.08680382370948792,
-0.027193086221814156,
-0.05111101269721985,
-0.004900211002677679,
0.050649188458919525,
0.06522969156503677,
0.010581850074231625,
-0.07329284399747849,
0.06640801578760147,
0.032... | 0.13203 |
this example, and internalize all of the concepts explained there. You will need to have configured your cluster's Kustomization with a decryption provider and decryption keys to enable the inclusion of encrypted secrets in your config repos. It is not safe to write unencrypted secrets into your git repository, and thi... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.03942717984318733,
-0.016222937032580376,
-0.02035142295062542,
0.01927069015800953,
0.02804037183523178,
-0.023686546832323074,
-0.011781550943851471,
-0.009463738650083542,
0.02883853018283844,
0.028026487678289413,
0.06940234452486038,
0.000676969822961837,
0.04502132907509804,
0.049... | 0.073393 |
all resources to use the `stg` namespace instead of the `prod` namespace. The secret can be copied anywhere we want within the reach of our Flux Kustomization, and since our Flux Kustomization still has `cluster-admin` and local access to the decryption key, there is no obstacle to copying secrets. #### Handling `Secre... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.1124652698636055,
-0.017770759761333466,
-0.0019649325404316187,
0.030376479029655457,
0.049210742115974426,
0.002924986882135272,
0.03569065406918526,
0.034706659615039825,
0.07579240947961807,
-0.010359995067119598,
0.013736716471612453,
-0.047913163900375366,
0.00956457294523716,
-0.... | 0.100654 |
the `flux-system` namespace. It cannot be over-emphasized; if users want secrets to remain secret, the `flux-system` namespace (and indeed the entire cluster itself) must be hardened and protected, managed by qualified cluster admins. It is recommended that changes which could access encrypted secrets are tightly contr... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.07829979062080383,
0.006280661094933748,
0.012325635179877281,
0.03867334499955177,
0.056746289134025574,
0.007147335447371006,
0.03636981174349785,
-0.016927529126405716,
0.05113067477941513,
-0.012860412709414959,
-0.04010046273469925,
0.014680062420666218,
0.055391546338796616,
-0.07... | 0.115129 |
is fine for Dev environments, but this is not a strategy for Production use cases. Your app's CI can commit and push YAML manifests (or one manifest for each app) into a separate deploy branch for `Kustomization` to apply. The deploy branch in a separate repository should be a branch to which the CI user is granted wri... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
0.021215343847870827,
-0.03860066831111908,
0.0208881963044405,
-0.06228150054812431,
-0.020223231986165047,
-0.09835857897996902,
-0.0303354375064373,
-0.01183020044118166,
-0.0023025486152619123,
0.03122352808713913,
0.03951128199696541,
-0.07584400475025177,
0.05479671433568001,
-0.0270... | 0.098924 |
these examples to the letter. They present an evolution and are meant to show some of the breadth of options that are available, rather than as prescriptive guidance. If you are on GitHub, and are struggling to get started using GitHub Actions, or maybe still waiting to make a move on your planned migration from Flux v... | https://github.com/fluxcd/website/blob/main/content/en/flux/use-cases/gh-actions-manifest-generation.md | main | fluxcd | [
-0.10889822244644165,
-0.021782556548714638,
0.03479166701436043,
0.0007866887608543038,
0.1495804786682129,
-0.04826290160417557,
-0.03222811594605446,
0.11075245589017868,
-0.05662064999341965,
-0.004297436214983463,
0.0013839089078828692,
-0.06098686903715134,
0.028361376374959946,
0.03... | 0.158667 |
The [helm-controller](../components/helm/\_index.md) allows you to declaratively manage Helm chart releases with Kubernetes manifests. It makes use of the artifacts produced by the [source-controller](../components/source/\_index.md) from `HelmRepository`, `GitRepository`, `Bucket` and `HelmChart` resources. The helm-c... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/helmreleases.md | main | fluxcd | [
0.032570187002420425,
-0.0016662009293213487,
0.03564721345901489,
-0.01739509589970112,
0.012849323451519012,
0.024092895910143852,
-0.05740965157747269,
0.017561474815011024,
0.060649216175079346,
0.10281011462211609,
-0.021606238558888435,
-0.05470138043165207,
0.020927682518959045,
-0.... | 0.076273 |
the repository and omits all other files. {{% alert color="info" title="Authentication" %}} HTTP/S basic and SSH authentication can be configured for private Git repositories. See the [`GitRepository` CRD docs](../components/source/gitrepositories.md) for more details. {{% /alert %}} ### Cloud Storage It is inadvisable... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/helmreleases.md | main | fluxcd | [
0.005588111001998186,
0.02104877308011055,
-0.017232701182365417,
0.015404636040329933,
0.10448656231164932,
-0.04373135790228844,
-0.016787808388471603,
0.03043704852461815,
0.1218002587556839,
0.07678361237049103,
0.03762741759419441,
0.027442574501037598,
0.06825916469097137,
-0.0329205... | 0.007477 |
Helm actions are performed. See the [`HelmRelease` CRD docs](../components/helm/helmreleases.md) for more details. {{% /alert %}} ### Using a chart reference It is possible to reference a chart directly from an `OCIRepository`: ```yaml apiVersion: helm.toolkit.fluxcd.io/v2 kind: HelmRelease metadata: name: podinfo spec... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/helmreleases.md | main | fluxcd | [
0.000047344416088890284,
0.01901332661509514,
0.005437609739601612,
-0.008896889165043831,
0.07562413811683655,
0.01763950102031231,
-0.034788403660058975,
0.07288672775030136,
0.11101152747869492,
0.031590916216373444,
0.01986713521182537,
-0.05508416146039963,
0.018504051491618156,
-0.03... | 0.106782 |
for triggering a reconciliation is [reacting immediately to changes in the Secret through the controller watch](#reacting-immediately-to-changes-in-referenced-secrets-and-configmaps). #### Encrypting a `values.yaml` with the SOPS CLI To prepare the encrypted secret, please note there are some divergences from encryptin... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/helmreleases.md | main | fluxcd | [
-0.0181867778301239,
0.01668599247932434,
0.013414744287729263,
-0.02030949853360653,
-0.006442961748689413,
-0.017914792522788048,
0.007983129471540451,
-0.05890472233295441,
0.12176904082298279,
0.025915440171957016,
0.007518916856497526,
-0.04866260662674904,
-0.01700996235013008,
-0.03... | 0.050603 |
repository. In order to notify source-controller about a chart update, you can [setup webhook receivers](webhook-receivers.md). First generate a random string and create a secret with a `token` field: ```sh TOKEN=$(head -c 12 /dev/urandom | shasum | cut -d ' ' -f1) echo $TOKEN kubectl -n flux-system create secret gener... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/helmreleases.md | main | fluxcd | [
-0.048288483172655106,
0.024155324324965477,
0.0005751257995143533,
-0.0014105351874604821,
0.08066284656524658,
-0.023283911868929863,
0.04006623104214668,
-0.008514970541000366,
0.12289997190237045,
0.041529905050992966,
-0.008742490783333778,
-0.14041326940059662,
0.08721260726451874,
-... | 0.169527 |
In order to store secrets safely in a public or private Git repository, you can use Bitnami's [sealed-secrets controller](https://github.com/bitnami-labs/sealed-secrets) and encrypt your Kubernetes Secrets into SealedSecrets. The sealed secrets can be decrypted only by the controller running in your cluster and nobody ... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/sealed-secrets.md | main | fluxcd | [
-0.03659440204501152,
-0.03528802841901779,
-0.027833305299282074,
0.01384630985558033,
-0.014726235531270504,
0.042645297944545746,
0.010410865768790245,
0.02368018962442875,
0.061376720666885376,
0.049213290214538574,
0.004063487518578768,
-0.0361284539103508,
0.01521217543631792,
-0.016... | 0.097884 |
a Kubernetes Secret on a cluster, they use kubeseal and the public key corresponding to that cluster to generate a SealedSecret. Assuming a team member wants to deploy an application that needs to connect to a database using a username and password, they'll be doing the following: \* create a Kubernetes Secret manifest... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/sealed-secrets.md | main | fluxcd | [
-0.010293369181454182,
-0.030006995424628258,
-0.018383994698524475,
-0.02621341124176979,
-0.06635914742946625,
-0.019570326432585716,
0.07432395964860916,
0.0225315373390913,
0.0752846896648407,
0.059299200773239136,
0.003978230990469456,
-0.05493898317217827,
0.097897969186306,
-0.02555... | 0.09296 |
In order to store secrets safely in a public or private Git repository, you can use [SOPS](https://github.com/mozilla/sops) CLI to encrypt Kubernetes secrets with OpenPGP, AWS KMS, GCP KMS and Azure Key Vault. ## Prerequisites To follow this guide you'll need a Kubernetes cluster with the GitOps toolkit controllers ins... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/mozilla-sops.md | main | fluxcd | [
-0.07246500998735428,
-0.00368546973913908,
-0.03027856908738613,
0.019014040008187294,
0.057649850845336914,
0.0401608869433403,
0.01968531496822834,
0.027219697833061218,
0.049445994198322296,
0.04965886101126671,
-0.020083485171198845,
-0.028384758159518242,
0.033956725150346756,
-0.040... | 0.104286 |
## Encrypting secrets using HashiCorp Vault [HashiCorp Vault](https://www.vaultproject.io/docs/what-is-vault) is an identity-based secrets and encryption management system. Encrypting with HashiCorp Vault follows the same workflow as PGP & Age. Export the `VAULT\_ADDR` and `VAULT\_TOKEN` environment variables to your s... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/mozilla-sops.md | main | fluxcd | [
0.03942328318953514,
0.037428807467222214,
-0.026048537343740463,
-0.01219705119729042,
-0.023931117728352547,
0.004146936349570751,
-0.016783298924565315,
0.008601921610534191,
0.019620127975940704,
-0.014101296663284302,
-0.0035842815414071083,
-0.03140098974108696,
-0.00824552308768034,
... | 0.033085 |
injecting secret data into environment variable key-value pairs in the Pod spec, which is a bad security practice. It should be taken as an explanation of Flux's behavior related to handling merging of secret data, not a security recommendation. {{% /alert %}} If your resource is encrypted it will be decrypted right be... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/mozilla-sops.md | main | fluxcd | [
-0.025487316772341728,
0.08783956617116928,
0.045332614332437515,
0.004610189702361822,
0.09681730717420578,
-0.050476886332035065,
0.07153984159231186,
-0.013738250359892845,
0.05249466001987457,
0.03713293746113777,
-0.002243434078991413,
-0.02717498689889908,
0.0349087156355381,
0.02245... | 0.109509 |
Flux is by design \*\*pull-based\*\*. In order to notify the Flux controllers about changes in Git or Helm repositories, you can setup webhooks and trigger a cluster reconciliation every time a source changes. Using webhook receivers make \*\*pull-based\*\* pipelines as responsive as \*\*push-based\*\* pipelines. ## Pr... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/webhook-receivers.md | main | fluxcd | [
-0.0606740340590477,
-0.06344391405582428,
0.006948024034500122,
0.020161401480436325,
0.07685208320617676,
-0.041800931096076965,
-0.0008499700925312936,
0.04851852357387543,
0.07579689472913742,
0.0479169636964798,
-0.043041158467531204,
-0.1019609272480011,
0.03321832790970802,
-0.01953... | 0.219977 |
a GitHub repository that you have control over: ```yaml apiVersion: source.toolkit.fluxcd.io/v1 kind: GitRepository metadata: name: webapp namespace: flux-system spec: interval: 60m url: https://github.com// ref: branch: master ``` {{% alert color="info" title="Authentication" %}} SSH or token based authentication can ... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/webhook-receivers.md | main | fluxcd | [
-0.06733199208974838,
-0.017332859337329865,
-0.05596531927585602,
-0.008713793009519577,
0.05521820858120918,
-0.027444588020443916,
0.0035543018020689487,
0.08213511854410172,
0.06665102392435074,
0.04608261212706566,
0.015557046979665756,
-0.09737655520439148,
0.10227035731077194,
-0.00... | 0.165644 |
This guide walks you through configuring container image scanning and deployment rollouts with Flux. For a container image you can configure Flux to: - scan the container registry and fetch the image tags - select the latest tag based on the defined policy (semver, calver, regex) - replace the tag in Kubernetes manifes... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/image-update.md | main | fluxcd | [
0.03280798718333244,
0.0012380164116621017,
0.07517768442630768,
-0.022774163633584976,
0.046079181134700775,
-0.019986726343631744,
-0.012838550843298435,
0.03542473912239075,
-0.013380228541791439,
0.06894587725400925,
0.0019169723382219672,
-0.054292429238557816,
0.04539024829864502,
-0... | 0.124358 |
your repository with: ```sh git clone https://github.com/$GITHUB\_USER/flux-image-updates cd flux-image-updates ``` Create a deployment for [podinfo](https://github.com/stefanprodan/podinfo) inside `clusters/my-cluster`: ```sh cat < ./clusters/my-cluster/podinfo-deployment.yaml apiVersion: apps/v1 kind: Deployment meta... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/image-update.md | main | fluxcd | [
0.04832161217927933,
-0.04823140427470207,
0.034225866198539734,
-0.008736304007470608,
0.052534494549036026,
-0.027371583506464958,
-0.010643422603607178,
0.07102738320827484,
0.03976956009864807,
0.09327001869678497,
0.049213338643312454,
-0.10069037973880768,
0.008775799535214901,
0.023... | 0.194537 |
image tag matches the policy semver range with: ```sh $ flux get image policy podinfo NAME LATEST IMAGE READY MESSAGE podinfo ghcr.io/stefanprodan/podinfo:5.0.3 True Latest image tag for 'ghcr.io/stefanprodan/podinfo' resolved to 5.0.3 ``` ## Configure image updates Edit the `podinfo-deployment.yaml` and add a marker t... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/image-update.md | main | fluxcd | [
0.004931674804538488,
-0.031326279044151306,
0.06568825989961624,
-0.006852276157587767,
0.11291063576936722,
-0.08603192865848541,
-0.004144781734794378,
0.0559956356883049,
-0.000498227309435606,
0.03915545344352722,
0.04434248432517052,
-0.08663138002157211,
0.036567773669958115,
0.0354... | 0.183918 |
ghcr.io/stefanprodan/podinfo newName: ghcr.io/stefanprodan/podinfo # {"$imagepolicy": "flux-system:podinfo:name"} newTag: 5.0.0 # {"$imagepolicy": "flux-system:podinfo:tag"} ``` ## Push updates to a different branch With `.spec.git.push.branch` you can configure Flux to push the image updates to different branch than t... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/image-update.md | main | fluxcd | [
-0.0284370556473732,
-0.056747592985630035,
0.01389124896377325,
0.003861447796225548,
0.06308828294277191,
-0.08645409345626831,
0.01807582937180996,
0.08279742300510406,
0.013056882657110691,
0.028513778001070023,
0.013955186121165752,
-0.057442955672740936,
0.03864218294620514,
0.059747... | 0.151623 |
to its latest stable version: ```sh flux create image policy podinfo \ --image-ref=podinfo \ --select-semver=">=5.0.0" ``` If the latest version e.g. `5.0.1` causes an incident in production, you can tell Flux to revert the image tag to a previous version e.g. `5.0.0` with: ```sh flux create image policy podinfo \ --im... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/image-update.md | main | fluxcd | [
0.008282041177153587,
-0.03601529821753502,
0.1038273498415947,
-0.005364658311009407,
0.12082212418317795,
-0.06632150709629059,
-0.02366577833890915,
0.047795966267585754,
-0.005444370210170746,
0.013941574841737747,
0.026712467893958092,
-0.009424012154340744,
0.011552390642464161,
0.00... | 0.17485 |
one you want to follow, and setting `digestReflectionPolicy` to `Always`, which will tell Flux to fetch the digest for that tag according to the specified `interval`, once every ten minutes in the example above. Then in the manifest where you want to use the `latest` tag, you can do the following: ```yaml apiVersion: a... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/image-update.md | main | fluxcd | [
0.047054629772901535,
0.017677688971161842,
0.04027196019887924,
-0.04769795015454292,
0.06753498315811157,
-0.0619487389922142,
0.0218069925904274,
0.06393759697675705,
0.055441588163375854,
-0.003254647133871913,
0.004329053219407797,
-0.05503947660326958,
0.014565475285053253,
0.0538378... | 0.120694 |
This guide walks you through several approaches of organizing repositories for a smooth GitOps experience with Flux. ## Monorepo In a monorepo approach you would store all your Kubernetes manifests in a single Git repository. The various environments specific configs are all stored in the same branch (e.g. `main`). ###... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/repository-structure.md | main | fluxcd | [
-0.01812628284096718,
-0.08424597233533859,
0.051358409225940704,
-0.012857891619205475,
0.0029442566446959972,
-0.024618234485387802,
0.001896980800665915,
0.05448455363512039,
0.033896055072546005,
0.05321682244539261,
-0.05005929246544838,
-0.08623408526182175,
0.05063110962510109,
-0.0... | 0.181511 |
apps definitions (Kubernetes deployments, Helm releases). \* Configures how the apps are reconciled on each environment (Kustomize overlays, Helm values). \* Manages the apps promotion between environments using Flux's automated image updates to Git. ### Repository structure Platform admin repository example (kustomize... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/repository-structure.md | main | fluxcd | [
-0.0008873544866219163,
-0.037891533225774765,
0.06765494495630264,
-0.07094229757785797,
0.038676269352436066,
-0.058679744601249695,
-0.025197690352797508,
0.06536025553941727,
0.08193418383598328,
0.04774381220340729,
-0.0014276652364060283,
-0.09838137775659561,
0.08051212877035141,
0.... | 0.212851 |
Flux does not support selecting the latest image by build time. Obtaining the build time needs the container config for each image, and fetching that is subject to strict rate limiting by image registries (e.g., by [DockerHub][dockerhub-rates]). This guide explains how to construct image tags so that the most recent im... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/sortable-image-tags.md | main | fluxcd | [
0.008519257418811321,
0.03494630381464958,
0.02933722361922264,
-0.03612691909074783,
0.09059201180934906,
-0.043839819729328156,
-0.04128094017505646,
0.07746604084968567,
0.024044906720519066,
0.017336413264274597,
-0.0361899696290493,
-0.033693984150886536,
0.04304103925824165,
0.062327... | 0.001554 |
and the git SHA1: ```yaml jobs: build-push: env: IMAGE: org/my-app runs-on: ubuntu-latest steps: # These are prerequisites for the docker build step - name: Set up QEMU uses: docker/setup-qemu-action@v2 - name: Set up Docker Buildx uses: docker/setup-buildx-action@v2 - name: Login to DockerHub uses: docker/login-action... | https://github.com/fluxcd/website/blob/main/content/en/flux/guides/sortable-image-tags.md | main | fluxcd | [
0.015267382375895977,
0.0467742420732975,
-0.0027108651120215654,
-0.028845172375440598,
-0.05141054838895798,
0.014418017119169235,
-0.04973043128848076,
0.00859496183693409,
0.03742075338959694,
0.03913230448961258,
0.013338555581867695,
-0.08711432665586472,
0.061242058873176575,
-0.001... | -0.046387 |
## Getting basic information Show all Flux objects that are not ready ```cli flux get all -A --status-selector ready=false ``` Show flux warning events ```cli kubectl get events -n flux-system --field-selector type=Warning ``` Flux CLI (check for `Ready=True` and `Suspend=False`) ```cli flux get sources all -A ``` See ... | https://github.com/fluxcd/website/blob/main/content/en/flux/cheatsheets/troubleshooting.md | main | fluxcd | [
-0.009217849001288414,
-0.019834695383906364,
0.007463644724339247,
0.00355550367385149,
0.08940901607275009,
-0.040944717824459076,
0.026275433599948883,
-0.007463562302291393,
0.03689587861299515,
-0.0011446905555203557,
0.0025632521137595177,
-0.15071244537830353,
0.010418442077934742,
... | 0.18348 |
error during Helm install or upgrade? This error is returned by Helm when the release that is attempted to be made does not fit in a `Secret`. Most of the time this is due to exceptionally large (umbrella) charts, as explained in [`helm/helm#8281`](https://github.com/helm/helm/issues/8281). If you are running into this... | https://github.com/fluxcd/website/blob/main/content/en/flux/cheatsheets/troubleshooting.md | main | fluxcd | [
0.01486247219145298,
0.019238552078604698,
0.060710806399583817,
-0.01196112297475338,
0.1341906636953354,
-0.021592415869235992,
-0.09514547884464264,
0.04644792526960373,
0.018744762986898422,
0.0758296400308609,
0.03531934693455696,
-0.05992912873625755,
0.005076044239103794,
-0.0044398... | 0.012324 |
## How does Flux OCI work? With Flux, you can distribute and reconcile Kubernetes configuration packaged as [OCI artifacts](https://github.com/opencontainers/artifacts/blob/main/artifact-authors.md). Instead of connecting Flux to a Git repository where the application desired state is defined, you can connect Flux to a... | https://github.com/fluxcd/website/blob/main/content/en/flux/cheatsheets/oci-artifacts.md | main | fluxcd | [
-0.038853444159030914,
-0.00393589586019516,
0.05004647374153137,
0.0084458589553833,
0.05344422534108162,
-0.09109862148761749,
0.04662856459617615,
0.0648522600531578,
0.09423716366291046,
-0.025494065135717392,
-0.03028084710240364,
-0.08464495837688446,
0.05368044972419739,
0.059068147... | 0.189877 |
production. When pushing changes to the main branch, a CI job generates the Kubernetes manifests for staging and pushes them to a container registry using the Flux CLI. Flux running on the staging cluster detects the new artifact digest, pulls the manifests and applies them. When cutting a release from the main branch ... | https://github.com/fluxcd/website/blob/main/content/en/flux/cheatsheets/oci-artifacts.md | main | fluxcd | [
0.023173872381448746,
-0.034250810742378235,
0.054021675139665604,
-0.005382052157074213,
0.05826015770435333,
-0.10877639055252075,
-0.002627863548696041,
0.015958450734615326,
0.09614188224077225,
-0.006050842814147472,
0.003584829391911626,
-0.08063875138759613,
0.027408091351389885,
-0... | 0.199195 |
metadata: name: podinfo namespace: flux-system spec: interval: 5m url: oci://ghcr.io/stefanprodan/manifests/podinfo provider: generic secretRef: name: ghcr-auth ``` ### Contextual Authorization When running Flux on managed Kubernetes clusters like EKS, AKS or GKE, you can set the `provider` field to `azure`, `aws` or `... | https://github.com/fluxcd/website/blob/main/content/en/flux/cheatsheets/oci-artifacts.md | main | fluxcd | [
-0.05234424024820328,
0.010378391481935978,
0.024921488016843796,
-0.009310373105108738,
0.0831243246793747,
-0.04453818127512932,
0.05620395019650459,
0.016632044687867165,
0.04489032179117203,
0.06408384442329407,
-0.0031819171272218227,
-0.12026320397853851,
0.09069210290908813,
0.07207... | 0.123754 |
--ca-cert-file= ``` Configure Flux to verify the artifacts using the Notary trust policy and certificate: ```yaml apiVersion: source.toolkit.fluxcd.io/v1 kind: OCIRepository metadata: name: app-manifests namespace: flux-system spec: interval: 5m url: oci://ghcr.io/org/app-manifests ref: semver: "\*" verify: provider: n... | https://github.com/fluxcd/website/blob/main/content/en/flux/cheatsheets/oci-artifacts.md | main | fluxcd | [
-0.08094479888677597,
0.03566117212176323,
0.011539389379322529,
0.008272499777376652,
0.10460611432790756,
-0.12703917920589447,
0.0211334228515625,
0.04756006971001625,
0.029317958280444145,
-0.024838726967573166,
0.011834077537059784,
-0.15281787514686584,
0.10856901109218597,
0.0563166... | 0.109419 |
SHA from it, and update the commit status on the Git provider. See the docs for configuring Git commit status updates [here](/flux/components/notification/providers/#git-commit-status-updates). ## Automated updates to Git If you wish to track the OCI artifacts revisions in Git, you can use Flux [image automation](/flux... | https://github.com/fluxcd/website/blob/main/content/en/flux/cheatsheets/oci-artifacts.md | main | fluxcd | [
-0.050866592675447464,
-0.0323241762816906,
0.03299267962574959,
0.007584068924188614,
0.13539986312389374,
-0.09559834003448486,
-0.020820491015911102,
0.03982606530189514,
0.03868594393134117,
0.006172739434987307,
0.023453641682863235,
-0.018355296924710274,
0.0374181792140007,
0.032759... | 0.098256 |
## About The Kustomization and HelmRelease APIs support defining custom logic for performing health checks on custom resources through the field `.spec.healthCheckExprs`. See the documentation for [Kustomization](/flux/components/kustomize/kustomizations/#health-check-expressions) and [HelmRelease](/flux/components/hel... | https://github.com/fluxcd/website/blob/main/content/en/flux/cheatsheets/cel-healthchecks.md | main | fluxcd | [
-0.0689111053943634,
0.07853920757770538,
0.02376515045762062,
-0.04442591965198517,
0.05418175458908081,
-0.02145092748105526,
0.027062082663178444,
0.048329778015613556,
0.06448997557163239,
0.006749576423317194,
-0.0017145455349236727,
-0.09301289170980453,
0.03533690422773361,
0.046261... | 0.216831 |
status.conditions.filter(e, e.type == 'Healthy').all(e, e.status == 'False') current: status.conditions.filter(e, e.type == 'Healthy').all(e, e.status == 'True') - apiVersion: iam.aws.crossplane.io/v1beta1 kind: Role failed: status.conditions.filter(e, e.type == 'Synced').all(e, e.status == 'False' && e.reason == 'Reco... | https://github.com/fluxcd/website/blob/main/content/en/flux/cheatsheets/cel-healthchecks.md | main | fluxcd | [
-0.002779461210593581,
0.07394318282604218,
0.03311694413423538,
0.0014023022959008813,
0.04175867885351181,
-0.04979295656085014,
0.038661424070596695,
-0.05846720561385155,
0.002931305905804038,
0.02398606576025486,
0.0042386287823319435,
-0.12073343247175217,
0.005622068885713816,
-0.07... | 0.028743 |
The Flux controllers follow the Kubernetes structured logging conventions. These logs can be collected and analyzed to monitor the operations of the controllers. The [fluxcd/flux2-monitoring-example][monitoring-example-repo] repository provides a ready-made example setup to get started with monitoring Flux, which inclu... | https://github.com/fluxcd/website/blob/main/content/en/flux/monitoring/logs.md | main | fluxcd | [
-0.047466568648815155,
-0.06831872463226318,
-0.01763121783733368,
-0.0005856102798134089,
0.04110093042254448,
-0.06996119022369385,
-0.03144754096865654,
0.03910886123776436,
0.03667965903878212,
0.06675755232572556,
-0.010263895615935326,
-0.08928956836462021,
-5.283445716486312e-7,
0.0... | 0.177101 |
be found in the [`monitoring/`](https://github.com/fluxcd/flux2-monitoring-example/tree/main/monitoring) directory. `monitoring/controllers/` directory contains the configurations for deploying kube-prometheus-stack and loki-stack. We'll discuss loki-stack below. For Flux metrics collection using Prometheus, refer to t... | https://github.com/fluxcd/website/blob/main/content/en/flux/monitoring/logs.md | main | fluxcd | [
-0.05438116565346718,
-0.05943748354911804,
0.0014019880909472704,
0.00019238122331444174,
0.02947572059929371,
-0.06946851313114166,
-0.03363367170095444,
0.06550674140453339,
0.055849380791187286,
0.018851324915885925,
-0.0048525528982281685,
-0.10831733047962189,
0.022076508030295372,
0... | 0.263404 |
By default, the standard installation of Flux exports a specific set of metrics about the controllers and their inner workings that may not serve the needs of all the users. Some of these metrics are common across all the Flux controllers, and some are very specific to a few controllers. It's not feasible to add all th... | https://github.com/fluxcd/website/blob/main/content/en/flux/monitoring/custom-metrics.md | main | fluxcd | [
-0.02825639396905899,
-0.034015897661447525,
-0.06084341183304787,
0.002931764116510749,
0.036585334688425064,
0.028368599712848663,
0.060255058109760284,
0.07838428765535355,
0.051836613565683365,
-0.01499867718666792,
-0.019718782976269722,
-0.11302831023931503,
0.037288933992385864,
0.0... | 0.20384 |
chartVersion] app\_version: [ status, history, "0", appVersion ] labelsFromPath: name: [metadata, name] exported\_namespace: [metadata, namespace] chart\_name: [spec, chart, spec, chart] ... ``` In the above, `gotk\_resource\_info` and `gotk\_helmrelease\_version\_info` metrics will be exported for HelmReleases. ``` # ... | https://github.com/fluxcd/website/blob/main/content/en/flux/monitoring/custom-metrics.md | main | fluxcd | [
0.00520072877407074,
0.03216979652643204,
-0.025309056043624878,
-0.012463347986340523,
0.02112860232591629,
-0.014010991901159286,
0.01530382502824068,
0.06589263677597046,
-0.005247511435300112,
0.04754489287734032,
0.002408859319984913,
-0.09431275725364685,
0.009718497283756733,
-0.043... | 0.126134 |
When operating a cluster, different teams may wish to receive notifications about the status of their GitOps pipelines. For example, the on-call team would receive alerts about reconciliation failures in the cluster, while the dev team may wish to be alerted when a new version of an app was deployed and if the deployme... | https://github.com/fluxcd/website/blob/main/content/en/flux/monitoring/alerts.md | main | fluxcd | [
0.011406298726797104,
-0.06736133247613907,
0.03386234492063522,
0.037928756326436996,
0.04747571423649788,
-0.012357987463474274,
0.031128311529755592,
0.019090760499238968,
0.08328622579574585,
0.05718628689646721,
-0.05705514922738075,
-0.07700076699256897,
0.00958168227225542,
0.057325... | 0.202788 |
for a specific commit. Allowing for custom automation tools that can automatically promote, commit to a new directory, after receiving a successful commit status. This can all be done without requiring any access to the Kubernetes cluster. As stated before the provider works by referencing the same git repository as th... | https://github.com/fluxcd/website/blob/main/content/en/flux/monitoring/alerts.md | main | fluxcd | [
-0.009476512670516968,
-0.04367693513631821,
0.025076033547520638,
0.03406970575451851,
0.0040308330208063126,
0.02463328093290329,
0.051142871379852295,
-0.043279435485601425,
0.13125263154506683,
0.07308939844369888,
0.026340259239077568,
-0.04660235717892647,
0.02697308547794819,
0.0073... | 0.135172 |
podinfo is deployed and the health checks pass you should get a successful status in your forked podinfo repository. If everything is setup correctly there should now be a green check-mark next to the latest commit. Clicking the check-mark should show a detailed view. | GitHub | GitLab | |------------------------------... | https://github.com/fluxcd/website/blob/main/content/en/flux/monitoring/alerts.md | main | fluxcd | [
0.02588585577905178,
-0.0011980939889326692,
0.04065556079149246,
-0.032945383340120316,
0.01840841956436634,
-0.10252583026885986,
-0.0030173936393111944,
-0.02728438377380371,
0.03741885721683502,
0.048962853848934174,
0.060302939265966415,
-0.04138603061437607,
0.008332118391990662,
-0.... | 0.004591 |
Flux has native support for [Prometheus][prometheus] metrics to provide insights into the state of the Flux components. These can be used to set up monitoring for the Flux controllers. In addition, Flux Custom Resource metrics can also be collected leveraging tools like [kube-state-metrics][kube-state-metrics]. This do... | https://github.com/fluxcd/website/blob/main/content/en/flux/monitoring/metrics.md | main | fluxcd | [
-0.08369936048984528,
-0.03270138427615166,
-0.017712969332933426,
0.023332644253969193,
0.027648426592350006,
-0.0777699425816536,
0.00831301137804985,
0.03322065249085426,
0.016858454793691635,
0.012881454080343246,
-0.04657355695962906,
-0.11016374081373215,
0.04480794817209244,
0.02288... | 0.257924 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.