content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
approach, Prometheus preserved its data model of simple timestamped floating point values and mapped this multitude of values into one time series each, distinguished by specific labels. In this way, summaries and classic histograms were created. In both, the count and sum of observations are each tracked in a separate... | https://github.com/prometheus/docs/blob/main/docs/practices/histograms.md | main | prometheus | [
-0.07281013578176498,
0.026576515287160873,
-0.00702680042013526,
-0.01110552717000246,
-0.06747164577245712,
-0.06525984406471252,
0.017055541276931763,
0.0014309084508568048,
0.0501309409737587,
-0.01819772459566593,
-0.01529387105256319,
-0.0689135193824768,
0.0021469355560839176,
0.030... | 0.225635 |
typically request durations or response sizes. In all variants (even quantile-less summaries), they track the number of observations \*and\* the sum of the observed values, allowing you to calculate the \*average\* of the observed values. To do so, you generally first take a `rate` over the desired duration and then di... | https://github.com/prometheus/docs/blob/main/docs/practices/histograms.md | main | prometheus | [
0.035426344722509384,
0.02209259755909443,
-0.04109957441687584,
0.009542771615087986,
-0.05312249809503555,
-0.04368411377072334,
-0.02071150578558445,
0.047333311289548874,
0.049488332122564316,
-0.010538513772189617,
-0.07386430352926254,
-0.138316348195076,
0.019168658182024956,
0.0199... | 0.150691 |
the bucket is populated or not. More buckets give you more options and accuracy in the various queries (see below), but the “one series per bucket” cost is quite significant. If you ingest the classic histograms as NHCBs, unpopulated buckets have a negligible cost, and even populated ones are handled in a more efficien... | https://github.com/prometheus/docs/blob/main/docs/practices/histograms.md | main | prometheus | [
0.0554012767970562,
0.02683667279779911,
-0.00031537481117993593,
-0.04813370853662491,
-0.022284917533397675,
-0.029671266674995422,
-0.02245519496500492,
0.01966431550681591,
0.024449674412608147,
0.033972591161727905,
-0.10888432711362839,
-0.09604667872190475,
0.033273905515670776,
-0.... | 0.046486 |
exactly 0.3, but with a decent resolution, the interpolated estimate will still be quite accurate. In return, you gain the freedom of changing the range boundaries at will, which is not only helpful if your SLO changes, but also to explore questions like “Could we maintain a stricter SLO based on the data of the last q... | https://github.com/prometheus/docs/blob/main/docs/practices/histograms.md | main | prometheus | [
-0.055077895522117615,
0.04475417360663414,
-0.018361316993832588,
-0.019713526591658592,
-0.04106198251247406,
-0.0493309311568737,
-0.040150634944438934,
0.04088997468352318,
-0.028102362528443336,
-0.007518923841416836,
-0.060946863144636154,
-0.06321228295564651,
0.05102590471506119,
-... | 0.11755 |
of the different approaches. | | Native Histogram | Classic Histogram | Summary |---|------------------|-------------------|--------- | Required configuration during instrumentation | Pick a desired resolution and maybe a strategy to limit the bucket count. | Pick buckets suitable for the expected range of observed val... | https://github.com/prometheus/docs/blob/main/docs/practices/histograms.md | main | prometheus | [
-0.026985282078385353,
0.034166544675827026,
-0.030438590794801712,
-0.034563079476356506,
-0.07180827111005783,
-0.0796109214425087,
0.034588657319545746,
0.03717748075723648,
-0.006323649547994137,
0.028877224773168564,
-0.041591230779886246,
-0.10411922633647919,
0.0685403048992157,
0.0... | 0.152324 |
`{le="0.45"}`. If your service runs replicated with a number of instances, you will collect request durations from every single one of them, and then you want to aggregate everything into an overall 95th percentile. However, aggregating the precomputed quantiles from a summary rarely makes sense. In this particular cas... | https://github.com/prometheus/docs/blob/main/docs/practices/histograms.md | main | prometheus | [
-0.014042817987501621,
0.06428118050098419,
0.025775395333766937,
-0.0033072365913540125,
-0.06411294639110565,
-0.08554403483867645,
0.011555144563317299,
0.019652992486953735,
0.03574073687195778,
-0.02092754654586315,
-0.0459011010825634,
-0.11648155748844147,
0.027424659579992294,
0.03... | 0.109887 |
an almost perfect guess. The classic histogram, however, will see almost all observations in the bucket from 300ms to 450ms. The 95th percentile is estimated to be 443ms, far away from the correct value close to 320ms. While you are only a tiny bit outside of your SLO, the estimated 95th quantile looks much worse. A su... | https://github.com/prometheus/docs/blob/main/docs/practices/histograms.md | main | prometheus | [
0.028463970869779587,
0.008392908610403538,
0.015718521550297737,
-0.03078877553343773,
0.0038331905379891396,
-0.08068285137414932,
0.012846393510699272,
0.0675453394651413,
-0.017334651201963425,
-0.022311167791485786,
-0.00176306685898453,
-0.05395495519042015,
0.014184554107487202,
-0.... | -0.007488 |
If you have access to native histograms, use them with a resolution that matches your accuracy requirements. This combines the required accuracy with the ability to aggregate and to change parameters (percentile, sliding window) ad hoc via the PromQL expression. 2. If you cannot use native histograms, but you need aggr... | https://github.com/prometheus/docs/blob/main/docs/practices/histograms.md | main | prometheus | [
-0.02606121450662613,
0.04110795632004738,
0.012170510366559029,
-0.04151667281985283,
-0.06504788994789124,
0.01154532190412283,
-0.008337214589118958,
0.06304890662431717,
0.05937643721699715,
0.012379897758364677,
-0.04562981799244881,
-0.09259551763534546,
0.017664970830082893,
0.04955... | 0.091849 |
This page provides an opinionated set of guidelines for instrumenting your code. ## How to instrument The short answer is to instrument everything. Every library, subsystem and service should have at least a few metrics to give you a rough idea of how it is performing. Instrumentation should be an integral part of your... | https://github.com/prometheus/docs/blob/main/docs/practices/instrumentation.md | main | prometheus | [
-0.05810242146253586,
-0.03883606940507889,
-0.0821116641163826,
-0.007504737004637718,
-0.04096081852912903,
-0.07251296192407608,
0.05029921233654022,
0.05514949560165405,
-0.0038494900800287724,
0.012117601931095123,
-0.09764636307954788,
0.011236324906349182,
0.02809976600110531,
-0.04... | 0.160538 |
batch jobs that take more than a few minutes to run, it is useful to also scrape them using pull-based monitoring. This lets you track the same metrics over time as for other types of jobs, such as resource usage and latency when talking to other systems. This can aid debugging if the job starts to get slow. For batch ... | https://github.com/prometheus/docs/blob/main/docs/practices/instrumentation.md | main | prometheus | [
-0.07560916990041733,
-0.04326498880982399,
-0.06888870894908905,
-0.005298887845128775,
0.05065843462944031,
-0.02305210381746292,
0.05090181529521942,
0.023522814735770226,
0.006191854830831289,
-0.05535828322172165,
-0.09500358253717422,
0.02176378108561039,
-0.05380474030971527,
-0.005... | 0.183004 |
being batch job durations. This is because both represent information about that particular push/scrape, rather than tracking multiple durations over time. ## Things to watch out for There are some general things to be aware of when doing monitoring, and also Prometheus-specific ones in particular. ### Use labels Few m... | https://github.com/prometheus/docs/blob/main/docs/practices/instrumentation.md | main | prometheus | [
-0.1084587424993515,
-0.018917134031653404,
-0.059943534433841705,
0.04035313427448273,
-0.01018618606030941,
-0.12503628432750702,
-0.008138417266309261,
-0.009389077313244343,
0.05186905339360237,
-0.016719061881303787,
-0.03457745164632797,
-0.10994603484869003,
0.025659983977675438,
0.... | 0.193375 |
useful for snapshots of state, such as in-progress requests, free/total memory, or temperature. You should never take a `rate()` of a gauge. Summaries and histograms are more complex metric types discussed in [their own section](/docs/practices/histograms/). ### Timestamps, not time since If you want to track the amoun... | https://github.com/prometheus/docs/blob/main/docs/practices/instrumentation.md | main | prometheus | [
-0.08060932904481888,
0.05068068206310272,
-0.06878022104501724,
-0.004102279432117939,
-0.024634703993797302,
-0.042047400027513504,
0.0063273306004703045,
0.04097447171807289,
0.06221088767051697,
0.009304466657340527,
-0.026258444413542747,
-0.04190460219979286,
-0.033061433583498,
-0.0... | 0.221842 |
A consistent naming scheme for [recording rules](/docs/prometheus/latest/configuration/recording\_rules/) makes it easier to interpret the meaning of a rule at a glance. It also avoids mistakes by making incorrect or meaningless calculations stand out. This page documents proper naming conventions and aggregation for r... | https://github.com/prometheus/docs/blob/main/docs/practices/rules.md | main | prometheus | [
-0.10833407193422318,
0.003270357847213745,
-0.059481482952833176,
-0.010398929007351398,
-0.06277137994766235,
-0.08238214254379272,
0.01930384151637554,
0.03621946647763252,
0.043039388954639435,
0.005834827199578285,
0.03402178734540939,
-0.04167431220412254,
0.01964709348976612,
0.0121... | 0.230337 |
names. When there is no aggregation, the levels always match. If this is not the case a mistake has likely been made in the rules. | https://github.com/prometheus/docs/blob/main/docs/practices/rules.md | main | prometheus | [
-0.06585077196359634,
-0.021221406757831573,
0.01732475310564041,
0.016835952177643776,
-0.01274912804365158,
-0.007537319324910641,
-0.07160042971372604,
-0.035075489431619644,
0.06561124324798584,
-0.07749775797128677,
0.036353591829538345,
-0.08857043832540512,
0.05377952381968498,
0.01... | 0.015174 |
The metric and label conventions presented in this document are not required for using Prometheus, but can serve as both a style-guide and a collection of best practices. Individual organizations may want to approach some of these practices, e.g. naming conventions, differently. ## Metric names A metric name... \* ...M... | https://github.com/prometheus/docs/blob/main/docs/practices/naming.md | main | prometheus | [
-0.08469514548778534,
-0.021513808518648148,
-0.05067673325538635,
-0.03555374965071678,
-0.0830165445804596,
-0.10151277482509613,
0.02339746803045273,
0.02596425637602806,
0.06029897928237915,
-0.05160507559776306,
-0.006570294965058565,
-0.08581925928592682,
0.04816103354096413,
0.03397... | 0.216617 |
information are already defined somewhere else (e.g. schema, metadata, other labels, etc.). Prometheus strongly recommends including unit and type in a metric name, even if you store that information elsewhere, because of the following practical reasons: \* \*\*Metric consumption reliability and UX\*\*: When interactin... | https://github.com/prometheus/docs/blob/main/docs/practices/naming.md | main | prometheus | [
-0.04835262522101402,
-0.01592370867729187,
-0.09314723312854767,
0.04185884818434715,
-0.0674528181552887,
-0.05735577642917633,
0.07705824822187424,
0.023544611409306526,
0.0813988670706749,
-0.03473962843418121,
-0.02013777755200863,
-0.09281939268112183,
0.02696358971297741,
0.04147910... | 0.152018 |
In addition to [client libraries](/docs/instrumenting/clientlibs/) and [exporters and related libraries](/docs/instrumenting/exporters/), there are numerous other generic integration points in Prometheus. This page lists some of the integrations with these. Not all integrations are listed here, due to overlapping funct... | https://github.com/prometheus/docs/blob/main/docs/operating/integrations.md | main | prometheus | [
-0.11363324522972107,
0.008906511589884758,
-0.023022670298814774,
-0.03741167485713959,
0.01537413988262415,
-0.11434851586818695,
-0.03306856006383896,
0.0013537023914977908,
-0.006615861784666777,
0.02024315670132637,
-0.014861748553812504,
0.016754770651459694,
-0.0062821414321660995,
... | 0.248872 |
systems or build on top of it. \* [Prometheus Operator](https://github.com/coreos/prometheus-operator): Manages Prometheus on top of Kubernetes \* [Promgen](https://github.com/line/promgen): Web UI and configuration generator for Prometheus and Alertmanager ## Other \* [Alert analysis](https://github.com/m0nikasingh/am... | https://github.com/prometheus/docs/blob/main/docs/operating/integrations.md | main | prometheus | [
-0.07463034242391586,
0.004108554683625698,
0.003764611901715398,
0.009069441817700863,
0.021347885951399803,
-0.1033894494175911,
0.019691580906510353,
-0.007232449483126402,
0.05101003125309944,
0.017301496118307114,
-0.0176297165453434,
-0.05297680199146271,
0.0038784348871558905,
-0.01... | 0.289508 |
NOTE: Before we dive into the technical details below, we would like to emphasize that Prometheus, as a monitoring system, collects and serves information about the systems it is monitoring. Therefore, the HTTP endpoints provided by Prometheus components should not be exposed to publicly accessible networks like the in... | https://github.com/prometheus/docs/blob/main/docs/operating/security.md | main | prometheus | [
-0.06587506085634232,
0.05335148051381111,
-0.02097502537071705,
-0.027328507974743843,
0.002041097264736891,
-0.10420674830675125,
0.0007124757976271212,
0.014459004625678062,
-0.006020498927682638,
-0.0015585018554702401,
-0.013369197025895119,
-0.0013795677805319428,
0.012362179346382618,... | 0.195025 |
HTTP endpoint and logs. They have access to all time series information contained in the database, plus a variety of operational/debugging information. It is also presumed that only trusted users have the ability to change the command line, configuration file, rule files and other aspects of the runtime environment of ... | https://github.com/prometheus/docs/blob/main/docs/operating/security.md | main | prometheus | [
-0.09915172308683395,
0.029987191781401634,
-0.05403592064976692,
0.014905615709722042,
0.043343059718608856,
-0.13768179714679718,
0.01328761875629425,
-0.046433307230472565,
0.02201336994767189,
-0.00147820555139333,
0.008574265986680984,
-0.007310973014682531,
0.014516563154757023,
0.00... | 0.156052 |
all the existing metric groups. This is disabled by default. If enabled, administrative functionality will be accessible under the `/api/\*/admin/` paths. ## Exporters Exporters generally only talk to one configured instance with a preset set of commands/requests, which cannot be expanded via their HTTP endpoint. There... | https://github.com/prometheus/docs/blob/main/docs/operating/security.md | main | prometheus | [
-0.13671773672103882,
0.025667719542980194,
-0.08266819268465042,
-0.004947133827954531,
0.005639124661684036,
-0.05690912902355194,
-0.0021987969521433115,
-0.04427679628133774,
0.02948693558573723,
-0.014029432088136673,
-0.006595502607524395,
-0.053503695875406265,
0.02493172138929367,
... | 0.072411 |
`up{job=""}` would become `up{job=""} or some\_metric{zzz=""}` if the `` was `"} or some\_metric{zzz="`. For those using Grafana note that [dashboard permissions are not data source permissions](https://grafana.com/docs/grafana/latest/permissions/#data-source-permissions), so do not limit a user's ability to run arbitr... | https://github.com/prometheus/docs/blob/main/docs/operating/security.md | main | prometheus | [
-0.17660632729530334,
0.07153895497322083,
-0.08978372067213058,
-0.013814489357173443,
-0.04771992936730385,
-0.12989015877246857,
0.013097974471747875,
-0.05755448341369629,
-0.010625625029206276,
0.013920546509325504,
-0.009979113936424255,
-0.01373912114650011,
0.05944603309035301,
0.0... | 0.129938 |
# Deep Links Deep links allow users to quickly redirect to third-party systems, such as Splunk, Datadog, etc. from the Argo CD user interface. Argo CD administrator will be able to configure links to third-party systems by providing deep link templates configured in `argocd-cm`. The templates can be conditionally rende... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/deep_links.md | master | argo-cd | [
-0.0644453689455986,
-0.05487976223230362,
-0.010494858957827091,
0.01508379727602005,
0.007176340091973543,
-0.027446210384368896,
-0.016155757009983063,
0.01792391762137413,
-0.02610427886247635,
0.07153359055519104,
-0.033556465059518814,
0.025250360369682312,
-0.03584355115890503,
-0.0... | 0.213524 |
github.com/expr-lang/expr is used for evaluation of conditions - url: https://mycompany.splunk.com?search={{.app.spec.destination.namespace}} title: Splunk if: application.spec.project == "default" - url: https://{{.app.metadata.annotations.splunkhost}}?search={{.app.spec.destination.namespace}} title: Splunk if: app.m... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/deep_links.md | master | argo-cd | [
-0.03204105794429779,
0.08218932896852493,
0.013816493563354015,
0.03919801488518715,
0.11673428118228912,
-0.05234293267130852,
0.05318768694996834,
-0.0017954002832993865,
0.052740562707185745,
0.03217901661992073,
0.01624155603349209,
-0.06166282668709755,
0.013585529290139675,
0.072995... | 0.097944 |
- [apps/DaemonSet/restart](https://github.com/argoproj/argo-cd/blob/master/resource\_customizations/apps/DaemonSet/actions/restart/action.lua) - [apps/Deployment/pause](https://github.com/argoproj/argo-cd/blob/master/resource\_customizations/apps/Deployment/actions/pause/action.lua) - [apps/Deployment/restart](https://... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/resource_actions_builtin.md | master | argo-cd | [
-0.06524304300546646,
-0.06628420948982239,
-0.05959296599030495,
0.022877182811498642,
-0.030929215252399445,
-0.00786945503205061,
0.03865282982587814,
0.037157509475946426,
-0.057059455662965775,
0.042130693793296814,
0.07036729156970978,
0.03489137068390846,
-0.08063314110040665,
-0.02... | 0.157794 |
# Architectural Overview  ## Components ### API Server The API server is a gRPC/REST server which exposes the API consumed by the Web UI, CLI, and CI/CD systems. It has the following responsibilities: \* application management and status reporting \* invoking o... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/architecture.md | master | argo-cd | [
-0.0585024431347847,
0.016590533778071404,
-0.0797123834490776,
-0.017354046925902367,
-0.039338018745183945,
-0.07018882781267166,
0.07129060477018356,
-0.026033226400613785,
0.10707369446754456,
0.08633776009082794,
0.011146791279315948,
-0.02092180773615837,
-0.031703781336545944,
-0.06... | 0.291636 |
# Verification of Argo CD Artifacts ## Prerequisites - cosign `v2.0.0` or higher [installation instructions](https://docs.sigstore.dev/cosign/system\_config/installation/) - slsa-verifier [installation instructions](https://github.com/slsa-framework/slsa-verifier#installation) - crane [installation instructions](https:... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/signed-release-assets.md | master | argo-cd | [
-0.07380720227956772,
0.048015668988227844,
-0.09283072501420975,
-0.07863342016935349,
0.005461642984300852,
-0.08813771605491638,
0.0036508552730083466,
-0.0408330000936985,
-0.08766162395477295,
0.01871120184659958,
0.12185219675302505,
-0.04450917989015579,
-0.02967381291091442,
-0.044... | 0.100748 |
full tag), use the `--source-versioned-tag` which performs semantic versioning verification: ```shell slsa-verifier verify-artifact argocd-linux-amd64 \ --provenance-path argocd-cli.intoto.jsonl \ --source-uri github.com/argoproj/argo-cd \ --source-versioned-tag v2 # Note: May use v2.7 for minor version verification. `... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/signed-release-assets.md | master | argo-cd | [
-0.04981352761387825,
-0.0019182437099516392,
-0.10641827434301376,
-0.03211977332830429,
0.10945044457912445,
-0.08957281708717346,
-0.00563135975971818,
-0.02610677294433117,
-0.016802137717604637,
0.05682177469134331,
0.04547882452607155,
-0.03741338849067688,
-0.031561240553855896,
0.0... | 0.049835 |
# Cluster Management This guide is for operators looking to manage clusters on the CLI. If you want to use Kubernetes resources for this, check out [Declarative Setup](./declarative-setup.md#clusters). Not all commands are described here, see the [argocd cluster Command Reference](../user-guide/commands/argocd\_cluster... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/cluster-management.md | master | argo-cd | [
0.029489314183592796,
-0.06370317935943604,
-0.11958663165569305,
0.0009799848776310682,
0.00045176976709626615,
0.014779332093894482,
0.05818817764520645,
-0.06701000034809113,
0.05569400638341904,
0.0437624454498291,
0.003004911355674267,
-0.04597991704940796,
-0.03590988740324974,
-0.04... | 0.146241 |
# TLS configuration Argo CD provides three inbound TLS endpoints that can be configured: \* The user-facing endpoint of the `argocd-server` workload, which serves the UI and the API \* The endpoint of the `argocd-repo-server`, which is accessed by `argocd-server` and `argocd-application-controller` workloads to request... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/tls.md | master | argo-cd | [
-0.0919865220785141,
0.009719999507069588,
-0.10528473556041718,
-0.004178436938673258,
-0.08876169472932816,
-0.08812163770198822,
0.05981855094432831,
0.0003997264429926872,
0.05128249526023865,
0.01454800646752119,
-0.00776482280343771,
0.03715473413467407,
-0.010649643838405609,
-0.000... | 0.094497 |
contains only information for TLS configuration to be used by `argocd-server` and is safe to be managed via third-party tools such as `cert-manager` or `SealedSecrets` To create this secret manually from an existing key pair, you can use `kubectl`: ```shell kubectl create -n argocd secret tls argocd-server-tls \ --cert... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/tls.md | master | argo-cd | [
-0.03541472926735878,
0.010514582507312298,
-0.08042287081480026,
-0.027092715725302696,
-0.08770595490932465,
-0.041981130838394165,
0.03334865719079971,
-0.04254409298300743,
0.08647093921899796,
0.05814306065440178,
0.00973318051546812,
0.009751955047249794,
-0.02321024425327778,
-0.027... | 0.057953 |
to use for its gRPC endpoint on startup. Because the `argocd-repo-server` has no means to connect to the K8s control plane API, this certificate is not available to outside consumers for verification. These components will use a non-validating connection to the `argocd-repo-server` for this reason. To change this behav... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/tls.md | master | argo-cd | [
-0.02361220121383667,
-0.0033787700813263655,
-0.1222178190946579,
-0.03918297216296196,
-0.05248670652508736,
-0.050824154168367386,
0.05712587758898735,
-0.010207459330558777,
0.056414373219013214,
0.07914338260889053,
0.012812737375497818,
-0.0014145730528980494,
-0.029528722167015076,
... | 0.038288 |
handle all aspects of TLS to `argocd-repo-server`'s TLS sidecar proxy. ### Disabling TLS to argocd-dex-server In some scenarios where mTLS through sidecar proxies is involved (e.g. in a service mesh), you may want to configure the connections between `argocd-server` to `argocd-dex-server` to not use TLS at all. In this... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/tls.md | master | argo-cd | [
-0.03386267274618149,
0.0434284470975399,
-0.024811385199427605,
-0.01859356090426445,
-0.08759038895368576,
-0.09448359906673431,
0.025227459147572517,
-0.05501701310276985,
-0.0007744061294943094,
0.04401515796780586,
0.0001622432318981737,
0.02572767436504364,
-0.005339893512427807,
-0.... | -0.032064 |
# Custom Tooling Argo CD bundles preferred versions of its supported templating tools (helm, kustomize, ks, jsonnet) as part of its container images. Sometimes, it may be desired to use a specific version of a tool other than what Argo CD bundles. Some reasons to do this might be: \* To upgrade/downgrade to a specific ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/custom_tools.md | master | argo-cd | [
-0.042080916464328766,
0.04413945600390434,
0.0030757123604416847,
-0.03800203278660774,
-0.008475502952933311,
-0.0309456754475832,
0.02014816179871559,
-0.01455781888216734,
0.03604874759912491,
0.08091671019792557,
0.03536318987607956,
-0.040257833898067474,
-0.03917841985821724,
-0.030... | 0.116261 |
# Troubleshooting Tools The document describes how to use `argocd admin` subcommands to simplify Argo CD settings customizations and troubleshot connectivity issues. ## Settings Argo CD provides multiple ways to customize system behavior and has a lot of settings. It might be dangerous to modify settings on Argo CD use... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/troubleshooting.md | master | argo-cd | [
-0.006169790402054787,
0.017693866044282913,
-0.07389405369758606,
0.008932968601584435,
-0.04366099089384079,
-0.1320198029279709,
0.071260966360569,
-0.02570996806025505,
-0.1219044104218483,
0.06282982230186462,
0.03483681380748749,
0.020623575896024704,
-0.015451311133801937,
-0.038962... | 0.072626 |
# Disaster Recovery You can use `argocd admin` to import and export all Argo CD data. Make sure you have `~/.kube/config` pointing to your Argo CD cluster. Figure out what version of Argo CD you're running: ```bash argocd version | grep server # ... export VERSION=v1.0.1 ``` Export to a backup: ```bash docker run -v ~/... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/disaster_recovery.md | master | argo-cd | [
0.024650827050209045,
-0.020518483594059944,
-0.05840311944484711,
-0.031767718493938446,
0.02151261642575264,
-0.026826240122318268,
0.028102455660700798,
-0.025097230449318886,
-0.01728869043290615,
0.09327027201652527,
-0.02716575562953949,
-0.013031402602791786,
-0.02069779671728611,
-... | 0.084882 |
# Resource Actions ## Overview Argo CD allows operators to define custom actions which users can perform on specific resource types. This is used internally to provide actions like `restart` for a `DaemonSet`, or `retry` for an Argo Rollout. Operators can add actions to custom resources in form of a Lua script and expa... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/resource_actions.md | master | argo-cd | [
-0.05962533876299858,
-0.037995096296072006,
-0.07025322318077087,
0.032504551112651825,
-0.07386011630296707,
-0.023722657933831215,
0.07138300687074661,
0.011233159340918064,
-0.005242952611297369,
0.07782164961099625,
-0.0115117272362113,
0.028221802785992622,
-0.07281363010406494,
-0.0... | 0.271484 |
actions. ```yaml resource.customizations.actions.argoproj.io\_Rollout: | mergeBuiltinActions: true discovery.lua: | actions = {} actions["do-things"] = {} return actions definitions: - name: do-things action.lua: | return obj ``` #### Creating new resources with a custom action > [!IMPORTANT] > Creating resources via t... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/resource_actions.md | master | argo-cd | [
-0.11516625434160233,
-0.07148426026105881,
-0.05206884443759918,
0.03337813913822174,
-0.03449356555938721,
-0.06875338405370712,
0.10839350521564484,
0.0145671796053648,
-0.013506368733942509,
0.12770892679691315,
0.03656068071722984,
0.009975324384868145,
-0.04394051432609558,
0.0282488... | 0.094988 |
so it does not get deleted cm1.metadata.annotations["argocd.argoproj.io/sync-options"] = "Prune=false" -- Keep the App synced even though it has a resource that is not in Git cm1.metadata.annotations["argocd.argoproj.io/compare-options"] = "IgnoreExtraneous" cm1.data = {} cm1.data.myKey1 = "myValue1" impactedResource1 ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/resource_actions.md | master | argo-cd | [
-0.056589409708976746,
0.0031610189471393824,
-0.028404248878359795,
0.0890674814581871,
0.04165700823068619,
-0.0701148733496666,
0.11003430932760239,
-0.041209835559129715,
-0.001072598504833877,
0.03876474127173424,
0.0484725646674633,
-0.009446612559258938,
0.01935991644859314,
-0.0595... | 0.067593 |
# Reconcile Optimization By default, an Argo CD Application is refreshed every time a resource that belongs to it changes. Kubernetes controllers often update the resources they watch periodically, causing continuous reconcile operation on the Application and a high CPU usage on the `argocd-application-controller`. Arg... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/reconcile.md | master | argo-cd | [
-0.004405757412314415,
0.038102034479379654,
-0.011882714927196503,
0.04743354767560959,
0.02802743762731552,
-0.07331067323684692,
0.06198399141430855,
-0.08621157705783844,
0.08157984167337418,
0.07266721874475479,
-0.042788341641426086,
0.034930575639009476,
-0.05027887597680092,
-0.079... | 0.149868 |
to confirm that your resource ignore rules are being applied. > [!NOTE] > These logs are at the `debug` level. Configure the application-controller's log level to `debug`. ## Examples ### argoproj.io/Application ```yaml apiVersion: v1 kind: ConfigMap metadata: name: argocd-cm data: resource.customizations.ignoreResourc... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/reconcile.md | master | argo-cd | [
-0.08398199081420898,
0.0299371387809515,
-0.012576578184962273,
0.028695233166217804,
0.05875756964087486,
-0.08111798763275146,
0.06829657405614853,
-0.08830258250236511,
-0.008752101100981236,
0.04909490421414375,
0.0122408801689744,
-0.01392615307122469,
-0.0029639217536896467,
0.01750... | 0.104766 |
# High Availability Argo CD is largely stateless. All data is persisted as Kubernetes objects, which in turn is stored in Kubernetes' etcd. Redis is only used as a disposable cache and can be safely rebuilt without service disruption. A set of [HA manifests](https://github.com/argoproj/argo-cd/tree/stable/manifests/ha)... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/high_availability.md | master | argo-cd | [
0.009942149743437767,
-0.018314192071557045,
-0.05150102823972702,
-0.0002910913899540901,
-0.02101173624396324,
-0.026490895077586174,
-0.016017567366361618,
-0.0075659481808543205,
-0.019190151244401932,
0.07546735554933548,
-0.010905550792813301,
0.05819486826658249,
-0.08895682543516159,... | 0.18955 |
repository (or only the files specified via the `argocd.argoproj.io/manifest-generate-paths` annotation) into a separate directory for each plugin. This can place a heavy load on disk resources for a \*\*argocd-repo-server\*\*, especially if the repository contains large files. To mitigate this, consider disabling `dis... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/high_availability.md | master | argo-cd | [
-0.029049601405858994,
-0.054100967943668365,
-0.09510168433189392,
0.04999971017241478,
0.03836534917354584,
-0.10594949871301651,
0.05171847715973854,
0.015779487788677216,
0.029352283105254173,
0.0992726981639862,
-0.00018694288155529648,
0.01578674465417862,
-0.047460272908210754,
0.03... | 0.094543 |
by the application controller. \* The shard distribution algorithm of the `argocd-application-controller` can be set by using the `--sharding-method` parameter. Supported sharding methods are: - `legacy` mode uses an `uid` based distribution (non-uniform). - `round-robin` uses an equal distribution across all shards. -... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/high_availability.md | master | argo-cd | [
0.0417715348303318,
-0.024880705401301384,
-0.08675744384527206,
-0.007390487473458052,
-0.027311019599437714,
-0.07852136343717575,
-0.021168682724237442,
-0.052151914685964584,
0.015508131124079227,
0.04680252820253372,
0.001246571890078485,
0.07550842314958572,
0.03390224650502205,
-0.0... | 0.049596 |
`1m`, `1h`. The default value is `100ms`. The variable is used only when `ARGOCD\_CLUSTER\_CACHE\_BATCH\_EVENTS\_PROCESSING` is set to `true`. \* `ARGOCD\_APPLICATION\_TREE\_SHARD\_SIZE` - environment variable controlling the max number of resources stored in one Redis key. Splitting application tree into multiple keys... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/high_availability.md | master | argo-cd | [
0.018404899165034294,
-0.007792588323354721,
-0.11446382850408554,
0.018541350960731506,
-0.04431965574622154,
-0.06981872022151947,
0.026819998398423195,
0.03148633614182472,
0.06590725481510162,
0.04542708396911621,
0.005603555589914322,
-0.03372294083237648,
0.001612756634131074,
-0.098... | 0.216394 |
``` \*\*Common fully qualified reference formats:\*\* \* \*\*Branches\*\*: `refs/heads/` (e.g., `refs/heads/main`, `refs/heads/develop`) \* \*\*Tags\*\*: `refs/tags/` (e.g., `refs/tags/v1.0.0`) \* \*\*Pull requests\*\* (GitHub): `refs/pull//head` (e.g., `refs/pull/123/head`) \* \*\*Merge requests\*\* (GitLab): `refs/me... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/high_availability.md | master | argo-cd | [
-0.08937810361385345,
-0.021485697478055954,
-0.031215805560350418,
-0.048023052513599396,
0.049282003194093704,
-0.13967365026474,
-0.008991687558591366,
-0.007408516947180033,
0.04342540353536606,
0.04267541319131851,
0.03509620949625969,
0.009927082806825638,
0.008154780603945255,
-0.04... | 0.099586 |
https://github.com/argoproj/argocd-example-apps.git targetRevision: HEAD path: guestbook # ... ``` \* \*\*Multiple paths\*\* It is possible to put multiple paths into the annotation. Paths must be separated with a semicolon (`;`): ```yaml apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: guestbook anno... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/high_availability.md | master | argo-cd | [
0.02202717587351799,
-0.002338823163881898,
-0.06777849793434143,
-0.026895200833678246,
0.06359009444713593,
-0.004550781566649675,
0.03682756423950195,
-0.009772744961082935,
0.042259424924850464,
0.03575265035033226,
-0.03414427489042282,
-0.05223795771598816,
-0.04289121925830841,
0.02... | 0.09936 |
following environment variable on `argocd-server`: ``` ARGOCD\_WEBHOOK\_MANIFEST\_CACHE\_WARM\_DISABLED=true ``` ### Application Sync Timeout & Jitter Argo CD has a timeout for application syncs. It will trigger a refresh for each application periodically when the timeout expires. With a large number of applications, t... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/high_availability.md | master | argo-cd | [
-0.07766485214233398,
-0.017191894352436066,
-0.06044532358646393,
0.033584609627723694,
-0.029048621654510498,
-0.11226632446050644,
0.055109500885009766,
-0.07263360172510147,
-0.0064854612573981285,
0.053807832300662994,
0.0019472709391266108,
0.04557923972606659,
-0.04202096536755562,
... | 0.115068 |
the time at which the item was last queued: - When `WORKQUEUE\_FAILURE\_COOLDOWN\_NS` != 0 : ``` backoff = time.Since(lastRequeueTime) >= WORKQUEUE\_FAILURE\_COOLDOWN\_NS ? WORKQUEUE\_BASE\_DELAY\_NS : min( WORKQUEUE\_MAX\_DELAY\_NS, WORKQUEUE\_BASE\_DELAY\_NS \* WORKQUEUE\_BACKOFF\_FACTOR ^ (numRequeue) ) ``` - When `... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/high_availability.md | master | argo-cd | [
-0.0725998505949974,
0.02771080657839775,
-0.051746949553489685,
0.06218844652175903,
-0.029389966279268265,
-0.07254523783922195,
0.04311647638678551,
-0.022586647421121597,
0.02384209632873535,
0.03993821144104004,
0.024178989231586456,
0.03133334964513779,
0.02729831077158451,
-0.097247... | 0.133198 |
# Dynamic Cluster Distribution > [!WARNING] > \*\*Alpha Feature (Since v2.9.0)\*\* > > This is an experimental, [alpha-quality](https://github.com/argoproj/argoproj/blob/main/community/feature-status.md#alpha) feature. > It may be removed in future releases or modified in backwards-incompatible ways. \*Current Status: ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/dynamic-cluster-distribution.md | master | argo-cd | [
0.004859904292970896,
-0.03804651275277138,
-0.024852484464645386,
0.03064982034265995,
-0.007653703447431326,
-0.05450699105858803,
-0.015338176861405373,
-0.03944425284862518,
-0.017172079533338547,
0.03241407126188278,
-0.018006734549999237,
0.04627498611807823,
-0.0345723032951355,
0.0... | 0.121643 |
instead reads the replica count directly from the Application Controller Deployment. The controller identifies the change in the number of replicas by comparing the replica count in the Application Controller Deployment and the number of mappings in the `argocd-app-controller-shard-cm` ConfigMap. In the scenario when t... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/dynamic-cluster-distribution.md | master | argo-cd | [
0.036302391439676285,
-0.09925195574760437,
-0.0728602409362793,
0.027489420026540756,
0.007787507493048906,
-0.02458682842552662,
0.03281412646174431,
-0.03731539472937584,
0.037691131234169006,
0.0712357610464096,
0.10180587321519852,
0.017364656552672386,
0.08007307350635529,
-0.0861421... | 0.099349 |
# Webhook Configuration ## Overview Argo CD polls Git/OCI/Helm repositories every three minutes to detect changes to the manifests. To eliminate this delay from polling, the API server can be configured to receive webhook events. ### Git Webhooks Argo CD supports Git webhook notifications from GitHub, GitLab, Bitbucket... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/webhook.md | master | argo-cd | [
-0.07456958293914795,
-0.011390733532607555,
-0.054574739187955856,
0.020220257341861725,
0.02265799604356289,
-0.1365024447441101,
0.052530135959386826,
-0.048502057790756226,
0.06297960877418518,
0.052590496838092804,
0.010460589081048965,
-0.042000848799943924,
0.0028767776675522327,
-0... | 0.1592 |
the trouble of base64 encoding the values and copying it to the `data` field. Simply copy the shared webhook secret created in step 1, to the corresponding GitHub/GitLab/BitBucket key under the `stringData` field: ```yaml apiVersion: v1 kind: Secret metadata: name: argocd-secret namespace: argocd type: Opaque data: ...... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/webhook.md | master | argo-cd | [
-0.053266629576683044,
0.049565501511096954,
-0.10557828098535538,
0.017034508287906647,
0.006493080873042345,
-0.1052800640463829,
0.0026594027876853943,
-0.06497181951999664,
0.02386537566781044,
0.0627274438738823,
0.03824354708194733,
-0.05927838757634163,
0.0671331137418747,
-0.080718... | -0.037082 |
events for artifacts with unknown media types. If your OCI artifact uses a custom or non-standard media type, the webhook will not be triggered. See [GitHub documentation on supported package types](https://docs.github.com/en/packages/learn-github-packages/about-permissions-for-github-packages). #### Configure the Webh... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/webhook.md | master | argo-cd | [
-0.07656117528676987,
0.027359168976545334,
-0.036158524453639984,
-0.016906462609767914,
0.06414621323347092,
-0.16679245233535767,
0.007032372988760471,
-0.03439459949731827,
0.058121826499700546,
-0.011282567866146564,
0.04305698722600937,
-0.08151920139789581,
-0.026607751846313477,
-0... | 0.118155 |
# Secret Management There are two general ways to populate secrets when doing GitOps: on the destination cluster, or in Argo CD during manifest generation. We strongly recommend the former, as it is more secure and provides a better user experience. For further discussion, see [#1364](https://github.com/argoproj/argo-c... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/secret-management.md | master | argo-cd | [
-0.07298282533884048,
-0.010777129791676998,
-0.02597903646528721,
0.04499034583568573,
-0.01670246385037899,
-0.007850020192563534,
0.04915313050150871,
0.024331163614988327,
0.05842016637325287,
0.098200723528862,
0.023366013541817665,
0.03146803379058838,
-0.01665925420820713,
-0.080706... | 0.224366 |
# Declarative Setup Argo CD applications, projects and settings can be defined declaratively using Kubernetes manifests. These can be updated using `kubectl apply`, without needing to touch the `argocd` command-line tool. ## Quick Reference All resources, including `Application` and `AppProject` specs, have to be insta... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
0.004411245230585337,
-0.017645129933953285,
-0.039430469274520874,
-0.043529216200113297,
-0.06358867138624191,
-0.03483472764492035,
0.02541244961321354,
0.017670942470431328,
0.009519657120108604,
0.07286752760410309,
0.009052547626197338,
-0.07585958391427994,
-0.04057663679122925,
-0.... | 0.142178 |
specified instead of the `path` attribute within `spec.source`. ```yaml spec: project: default source: repoURL: https://argoproj.github.io/argo-helm chart: argo ``` > [!WARNING] > Without the `resources-finalizer.argocd.argoproj.io` finalizer, deleting an application will not delete the resources it manages. To perform... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.026006875559687614,
-0.014226432889699936,
-0.048867784440517426,
-0.014532140456140041,
0.07824517786502838,
-0.07074116915464401,
0.04573504254221916,
-0.007265528663992882,
0.02180406264960766,
0.08040014654397964,
0.011253643780946732,
-0.005977623164653778,
0.007534130476415157,
0.... | 0.145098 |
with `.git`. Repository details are stored in secrets. To configure a repo, create a secret which contains repository details. Consider using [bitnami-labs/sealed-secrets](https://github.com/bitnami-labs/sealed-secrets) to store an encrypted secret definition as a Kubernetes manifest. Each repository must have a `url` ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.03896032273769379,
-0.040778208523988724,
-0.03634927421808243,
0.02212122082710266,
-0.08296790719032288,
0.04100392758846283,
0.02600393444299698,
0.000999651150777936,
0.11080574989318848,
0.08882888406515121,
0.022106168791651726,
-0.05469967797398567,
0.08233300596475601,
0.0547925... | 0.046753 |
repository must either not be configured at all, or if configured, must not contain any credential information (i.e. contain none of `sshPrivateKey`, `username`, `password` ) \* The URL configured for a credential template (e.g. `https://github.com/argoproj`) must match as prefix for the repository URL (e.g. `https://g... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.06635072082281113,
-0.036457400768995285,
-0.07853791862726212,
-0.05931009724736214,
-0.05304946377873421,
0.00510577904060483,
0.009044772014021873,
0.004649407230317593,
0.04285409301519394,
0.04085294157266617,
0.026910539716482162,
-0.018932612612843513,
0.028804589062929153,
0.038... | 0.035095 |
might take a while for changes in the ConfigMap to be reflected in your pods, depending on your Kubernetes configuration. ### SSH known host public keys If you are configuring repositories to use SSH, Argo CD will need to know their SSH public keys. In order for Argo CD to connect via SSH the public key(s) for each rep... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
0.06679820269346237,
-0.0101311719045043,
-0.011017649434506893,
0.030825236812233925,
-0.06624770164489746,
-0.015454974956810474,
0.03493015468120575,
-0.06405793875455856,
0.03277818486094475,
0.10495749115943909,
-0.022128330543637276,
-0.05681202933192253,
-0.01716596633195877,
-0.062... | 0.140185 |
`server` - cluster api server url \* `namespaces` - optional comma-separated list of namespaces which are accessible in that cluster. Setting namespace values will cause cluster-level resources to be ignored unless `clusterResources` is set to `true`. \* `clusterResources` - optional boolean string (`"true"` or `"false... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.04752562940120697,
0.004789162427186966,
-0.09150508791208267,
0.08680735528469086,
-0.0077904341742396355,
-0.007476004771888256,
0.03268871083855629,
-0.05863771215081215,
0.007174902595579624,
0.036258988082408905,
-0.02734924666583538,
-0.07354241609573364,
0.0070882681757211685,
0.... | 0.16743 |
"arn:aws:iam:::role/" }, "tlsClientConfig": { "insecure": false, "caData": "" } } ``` This setup requires: 1. [IRSA enabled](https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html) or [Pod Identity agent](https://docs.aws.amazon.com/eks/latest/userguide/pod-id-agent-setup.html) on y... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.01288817822933197,
0.04287613555788994,
-0.07507859170436859,
0.05034764111042023,
-0.01725396141409874,
-0.028737764805555344,
0.06968659162521362,
-0.06903629004955292,
0.0740651935338974,
0.08663113415241241,
0.02824874222278595,
-0.07541979104280472,
0.05263799801468849,
-0.00836872... | 0.172026 |
``` This allows the Argo CD management role to assume the cluster role. You can add permissions like above to the Argo CD management role for each cluster being managed by Argo CD (assuming you create a new role per cluster). #### Cluster Role Trust Policies As stated, each EKS cluster being added to Argo CD should hav... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.023756427690386772,
0.01176150981336832,
-0.05863983929157257,
0.043759897351264954,
-0.020668629556894302,
-0.0053540924564003944,
0.09161653369665146,
-0.05414709076285362,
0.03420369327068329,
0.09941184520721436,
0.008415916003286839,
-0.037422746419906616,
0.031287774443626404,
-0.... | 0.201956 |
- "groups": - "" "rolearn": "arn:aws:iam:::role/" "username": "arn:aws:iam:::role/" ``` Use the role ARN for both `rolearn` and `username`. #### Alternative EKS Authentication Methods In some scenarios it may not be possible to use IRSA, such as when the Argo CD cluster is running on a different cloud provider's platfo... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.04590163379907608,
0.028179286047816277,
-0.11083914339542389,
0.03403500095009804,
-0.038311660289764404,
0.005727847572416067,
0.09540501981973648,
-0.013747403398156166,
0.025943120941519737,
0.0783960148692131,
0.020855313166975975,
-0.10030559450387955,
0.014219578355550766,
-0.000... | 0.086432 |
"tlsClientConfig": { "insecure": false, "caData": "" } } ``` Note that you must enable Workload Identity on your GKE cluster, create GCP service account with appropriate IAM role and bind it to Kubernetes service account for argocd-application-controller and argocd-server (showing Pod logs on UI). See [Use Workload Ide... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.05024057999253273,
0.04834403470158577,
-0.03243868425488472,
-0.008361096493899822,
-0.06337687373161316,
-0.021473852917551994,
0.06998219341039658,
-0.06581635773181915,
0.07525716722011566,
0.1121567115187645,
0.004995038732886314,
-0.08238882571458817,
0.05368201807141304,
0.002816... | 0.06237 |
in your service principal client secret", "AZURE\_TENANT\_ID": "fill in tenant id", "AZURE\_CLIENT\_ID": "fill in your service principal client id", "AAD\_LOGIN\_METHOD": "spn" }, "args": ["azure"], "apiVersion": "client.authentication.k8s.io/v1beta1" }, "tlsClientConfig": { "insecure": false, "caData": "" } } ``` ## H... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.04937613755464554,
0.05731527879834175,
-0.03388434275984764,
-0.03671925887465477,
-0.02620057389140129,
-0.002568452153354883,
-0.004431537818163633,
-0.03367050364613533,
0.09331130981445312,
0.11168058216571808,
0.04267473891377449,
-0.04857037588953972,
0.07673796266317368,
0.02912... | -0.000834 |
Some excluded objects may already be in the controller cache. A restart of the controller will be necessary to remove them from the Application View. ## Mask sensitive Annotations on Secrets An optional comma-separated list of `metadata.annotations` keys can be configured with `resource.sensitive.mask.annotations` to m... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.030458133667707443,
0.03419461473822594,
-0.17734935879707336,
0.05167916417121887,
0.04857277870178223,
-0.03581056743860245,
0.07663498818874359,
-0.07113753259181976,
0.0269563477486372,
0.0414419062435627,
0.049452219158411026,
0.010349695570766926,
0.00333365797996521,
-0.018223699... | 0.102696 |
live example of self managed Argo CD config is available at [https://cd.apps.argoproj.io](https://cd.apps.argoproj.io) and with configuration stored at [argoproj/argoproj-deployments](https://github.com/argoproj/argoproj-deployments/tree/master/argocd). > [!NOTE] > You will need to sign-in using your GitHub account to ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.022561337798833847,
-0.07359009981155396,
-0.07050000131130219,
0.01616063341498375,
-0.029222527518868446,
-0.0811198502779007,
0.015018043108284473,
-0.0014182914746925235,
-0.026604903861880302,
0.12450059503316879,
0.05382011458277702,
0.03664787858724594,
-0.023729892447590828,
-0.... | 0.136364 |
# Config Management Plugins Argo CD's "native" config management tools are Helm, Jsonnet, and Kustomize. If you want to use a different config management tool, or if Argo CD's native tool support does not include a feature you need, you might need to turn to a Config Management Plugin (CMP). The Argo CD "repo server" c... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/config-management-plugins.md | master | argo-cd | [
-0.02029692381620407,
-0.044572215527296066,
-0.03261873126029968,
-0.012739810161292553,
-0.04456464201211929,
-0.033793020993471146,
0.06221546232700348,
-0.01259294617921114,
-0.03289678692817688,
0.08795329928398132,
0.027942772954702377,
-0.034893784672021866,
-0.049846962094306946,
0... | 0.166175 |
directory) glob patterns. glob: "\*\*/Chart.yaml" # The find command runs in the repository's root directory. To match, it must exit with status code 0 \_and\_ # produce non-empty output to standard out. command: [sh, -c, find . -name env.yaml] # The parameters config describes what parameters the UI should display for... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/config-management-plugins.md | master | argo-cd | [
-0.08386661112308502,
-0.0003844322054646909,
-0.0152781642973423,
0.0387655571103096,
0.01701573096215725,
-0.01807706244289875,
0.0477568618953228,
0.041532743722200394,
0.033601827919483185,
-0.01754259504377842,
0.07287921756505966,
-0.02548402175307274,
0.029943525791168213,
0.0061447... | 0.09907 |
only follows kubernetes-style spec conventions. The `generate` command must print a valid Kubernetes YAML or JSON object stream to stdout. Both `init` and `generate` commands are executed inside the application source directory. The `discover.fileName` is used as [glob](https://pkg.go.dev/path/filepath#Glob) pattern to... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/config-management-plugins.md | master | argo-cd | [
-0.07602176070213318,
0.01809803582727909,
-0.013319948688149452,
0.020345648750662804,
-0.0006510224775411189,
0.00431050593033433,
0.00007994893530849367,
-0.020159799605607986,
0.01975305937230587,
0.06169460341334343,
0.0911780595779419,
-0.05772271379828453,
-0.06514974683523178,
0.00... | 0.117223 |
This prevents users from directly setting potentially-sensitive environment variables. 4. Parameters in the Application spec: apiVersion: argoproj.io/v1alpha1 kind: Application spec: source: plugin: parameters: - name: values-files array: [values-dev.yaml] - name: helm-parameters map: image.tag: v1.2.3 The parameters a... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/config-management-plugins.md | master | argo-cd | [
0.009920363314449787,
0.049240246415138245,
-0.04170004650950432,
0.0162555780261755,
0.03662658855319023,
-0.016522007063031197,
0.028605373576283455,
0.04109102860093117,
-0.02467401511967182,
0.031152458861470222,
0.019445454701781273,
-0.031170861795544624,
-0.04004831239581108,
0.0457... | 0.087497 |
If a CMP command fails to gracefully exit on `ARGOCD\_EXEC\_TIMEOUT`, it will be forcefully killed after an additional timeout of `ARGOCD\_EXEC\_FATAL\_TIMEOUT`. ## Debugging a CMP If you are actively developing a sidecar-installed CMP, keep a few things in mind: 1. If you are mounting plugin.yaml from a ConfigMap, you... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/config-management-plugins.md | master | argo-cd | [
0.016198549419641495,
0.01162643451243639,
0.00838978961110115,
0.02310025319457054,
0.04604514315724373,
-0.05133388936519623,
-0.03940565139055252,
0.00938271451741457,
-0.052743956446647644,
0.06844178587198257,
0.11031319946050644,
0.002633767668157816,
-0.04510638117790222,
-0.0268392... | 0.069335 |
ConfigMap entry into a config file First, copy the plugin's configuration into its own YAML file. Take for example the following ConfigMap entry: ```yaml data: configManagementPlugins: | - name: pluginName init: # Optional command to initialize application source directory command: ["sample command"] args: ["sample arg... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/config-management-plugins.md | master | argo-cd | [
-0.04284024238586426,
-0.04701869934797287,
-0.037099841982126236,
0.03170761466026306,
-0.018614286556839943,
-0.005657500121742487,
0.03913770243525505,
0.003809182206168771,
-0.012147190049290657,
0.07136524468660355,
0.037088435143232346,
-0.07921378314495087,
-0.01704704388976097,
-0.... | 0.124148 |
files mode By default, config management plugin receives source repository files with reset file mode. This is done for security reasons. If you want to preserve original file mode, you can set `preserveFileMode` to `true` in the plugin spec: > [!WARNING] > Make sure you trust the plugin you are using. If you set `pres... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/config-management-plugins.md | master | argo-cd | [
-0.0925079733133316,
-0.05592474341392517,
-0.0584590919315815,
0.06465063244104385,
0.026742177084088326,
-0.037066422402858734,
0.07130119949579239,
-0.0057813627645373344,
0.004026744980365038,
0.06918056309223175,
0.05932701751589775,
0.05879499390721321,
-0.013593641109764576,
-0.0021... | 0.097544 |
# Git Configuration ## System Configuration Argo CD uses the Git installation from its base image (Ubuntu), which includes a standard system configuration file located at `/etc/gitconfig`. This file is minimal, just defining filters necessary for Git LFS functionality. You can customize Git's system configuration by mo... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/git_configuration.md | master | argo-cd | [
0.0015988359227776527,
-0.08761071413755417,
0.0031310529448091984,
0.0233160350471735,
0.03504610061645508,
-0.07888877391815186,
0.055139366537332535,
0.013229157775640488,
-0.024249276146292686,
0.07028815150260925,
0.037682872265577316,
0.04413807764649391,
-0.02229379676282406,
-0.002... | 0.071458 |
# Metrics Argo CD exposes different sets of Prometheus metrics per server. ## Application Controller Metrics Metrics about applications. Scraped at the `argocd-metrics:8082/metrics` endpoint. | Metric | Type | Description | | ------------------------------------------------- | :-------: | ------------------------------... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/metrics.md | master | argo-cd | [
-0.01434520073235035,
-0.033417779952287674,
-0.1306128054857254,
-0.001258153235539794,
-0.07882332056760788,
-0.09337541460990906,
0.02284395508468151,
0.014273015782237053,
-0.0007099167560227215,
0.013515637256205082,
-0.002411563415080309,
-0.07292257994413376,
-0.036504171788692474,
... | 0.158705 |
apps | Group name of a Kubernetes resource being monitored. | | host | example.com | Hostname of the Kubernetes API to which the request was made. | | hostname | argocd-application-controller-0 | Hostname of the Argo CD component that initiated the request to Redis. | | initiator | argocd-server | Name of the Argo CD c... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/metrics.md | master | argo-cd | [
-0.025390371680259705,
-0.024242931976914406,
-0.10700982809066772,
-0.0024144132621586323,
-0.034507010132074356,
-0.05428299680352211,
0.06662292778491974,
-0.02150052599608898,
0.08303830772638321,
0.08030673116445541,
-0.0003862191515509039,
-0.04690426588058472,
-0.004907801281660795,
... | 0.245556 |
- ExcludedResourceWarning ``` ## Application Set Controller metrics The Application Set controller exposes the following metrics for application sets. | Metric | Type | Description | | ------------------------------------------------- | :-------: | -----------------------------------------------------------------------... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/metrics.md | master | argo-cd | [
0.0005947704776190221,
-0.02293200045824051,
-0.08057655394077301,
-0.030799625441432,
-0.0470808744430542,
0.033854689449071884,
0.10990255326032639,
0.03511456027626991,
0.03527500480413437,
-0.03428009897470474,
-0.004855197388678789,
-0.08047207444906235,
0.060419730842113495,
-0.08264... | 0.064712 |
Description | | ----------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | call\_status | no\_error | Status of the kubectl exec plugin call. Possible values are: no\_error, plugin\_execution\_error, plu... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/metrics.md | master | argo-cd | [
-0.023527273908257484,
0.022602546960115433,
-0.05176302045583725,
-0.05872451141476631,
-0.06897067278623581,
-0.0127418152987957,
-0.03579309582710266,
-0.010135031305253506,
0.07492107152938843,
0.024896757677197456,
0.04252104088664055,
-0.13162516057491302,
-0.04534798488020897,
-0.07... | 0.119651 |
plugin\_execution\_error, plugin\_not\_found\_error, client\_internal\_error. | | code | 200 | HTTP status code returned by the request or exit code of a command. kubectl metrics produced by client-go use `code` for HTTP responses, while metrics produced by Argo CD proxy extensions use `status`. | | extension | metrics... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/metrics.md | master | argo-cd | [
-0.0004385739448480308,
-0.011461514979600906,
-0.06048024818301201,
-0.005615632049739361,
-0.10029903799295425,
-0.02728307619690895,
0.029076827690005302,
-0.0009578703320585191,
0.0798742026090622,
0.09367862343788147,
-0.03655330091714859,
-0.052251268178224564,
-0.056941647082567215,
... | 0.151402 |
## Prometheus Operator If using Prometheus Operator, the following ServiceMonitor example manifests can be used. Add a namespace where Argo CD is installed and change `metadata.labels.release` to the name of label selected by your Prometheus. ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: n... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/metrics.md | master | argo-cd | [
-0.010818611830472946,
0.00010007142554968596,
-0.027177637442946434,
-0.013032819144427776,
-0.0073006837628781796,
-0.052131667733192444,
0.0539361909031868,
-0.04117979109287262,
0.04704686254262924,
0.05490858480334282,
-0.006493734195828438,
-0.08733853697776794,
-0.035494834184646606,
... | 0.240394 |
# Argo CD Core ## Introduction Argo CD Core is a different installation that runs Argo CD in headless mode. With this installation, you will have a fully functional GitOps engine capable of getting the desired state from Git repositories and applying it in Kubernetes. The following groups of features won't be available... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/core.md | master | argo-cd | [
-0.02484075166285038,
-0.03219445422291756,
-0.052515387535095215,
0.0020940706599503756,
-0.03597867488861084,
-0.02654299885034561,
0.07653523981571198,
-0.004341659601777792,
-0.0034906957298517227,
0.07957440614700317,
0.01808626390993595,
-0.05117572098970413,
-0.027646450325846672,
-... | 0.176954 |
with Argo CD using this method. The Web UI can be started locally by running the following command: ``` argocd admin dashboard -n argocd ``` Argo CD Web UI will be available at `http://localhost:8080` | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/core.md | master | argo-cd | [
0.04109317064285278,
-0.004963895305991173,
-0.099606454372406,
-0.06230149045586586,
-0.011659679934382439,
-0.05603247508406639,
-0.0344909206032753,
0.006553054787218571,
-0.10666962713003159,
0.05238392576575279,
0.10186558961868286,
-0.001707754679955542,
-0.06130277365446091,
-0.0037... | 0.046294 |
# Managed By URL Annotation ## Overview The `argocd.argoproj.io/managed-by-url` annotation allows an Application resource to specify which Argo CD instance manages it. This is useful when you have multiple Argo CD instances and need application links in the UI to point to the correct managing instance. ## Use Case When... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/managed-by-url.md | master | argo-cd | [
-0.022166509181261063,
-0.024018079042434692,
-0.030497534200549126,
0.02269086055457592,
0.04364631325006485,
-0.059744540601968765,
0.07151492685079575,
-0.011485420167446136,
0.011762321926653385,
0.04771721363067627,
-0.009243450127542019,
0.019993605092167854,
0.008044091984629631,
0.... | 0.20903 |
port-forward -n namespace-b svc/argocd-server 8081:443 & # Wait for Argo CD to be ready kubectl wait --for=condition=available --timeout=300s deployment/argocd-server -n argocd # Get the admin password for primary instance kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/managed-by-url.md | master | argo-cd | [
-0.013162133283913136,
-0.020198503509163857,
-0.09723274409770966,
-0.06648779660463333,
-0.07637942582368851,
-0.042908843606710434,
-0.009871036745607853,
0.008990878239274025,
0.0637257769703865,
0.0771358534693718,
0.006223294883966446,
-0.06845349818468094,
-0.030642079189419746,
-0.... | 0.071424 |
# Applications in any namespace > [!WARNING] > Please read this documentation carefully before you enable this feature. Misconfiguration could lead to potential security issues. ## Introduction As of version 2.5, Argo CD supports managing `Application` resources in namespaces other than the control plane's namespace (w... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/app-any-namespace.md | master | argo-cd | [
-0.05034004524350166,
-0.06104487553238869,
-0.06982165575027466,
-0.00568024069070816,
-0.03688894957304001,
-0.062034327536821365,
0.11342722177505493,
-0.019120167940855026,
-0.038287412375211716,
0.06801165640354156,
-0.013807512819766998,
-0.0026432450395077467,
0.005594091489911079,
... | 0.149209 |
the `--application-namespaces` parameter to the container's startup command. The `--application-namespaces` parameter takes a comma-separated list of namespaces where `Applications` are to be allowed in. Each entry of the list supports: - shell-style wildcards such as `\*`, so for example the entry `app-team-\*` would ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/app-any-namespace.md | master | argo-cd | [
-0.0049645304679870605,
-0.06412562727928162,
-0.1026851013302803,
-0.029874883592128754,
-0.02564251609146595,
-0.030850471928715706,
0.04379240423440933,
-0.020937245339155197,
-0.04435519129037857,
0.04173655807971954,
0.028601450845599174,
-0.05043744295835495,
0.009060405194759369,
0.... | 0.125275 |
is a list that can contain an arbitrary amount of namespaces, and each entry supports shell-style wildcard, so that you can allow namespaces with patterns like `team-one-\*`. > [!WARNING] > Do not add user controlled namespaces in the `.spec.sourceNamespaces` field of any privileged AppProject like the `default` projec... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/app-any-namespace.md | master | argo-cd | [
-0.06214499846100807,
-0.038623277097940445,
-0.11245200037956238,
-0.005755223799496889,
-0.033534321933984756,
-0.03365422785282135,
0.10809136182069778,
0.014199432916939259,
-0.06085044518113136,
0.05735674500465393,
-0.02087339200079441,
-0.05826753377914429,
0.04364364966750145,
-0.0... | 0.072451 |
control plane's namespace. For example, to retrieve the `Application` named `foo` in the namespace `bar`, you can use the following CLI command: ```shell argocd app get foo/bar ``` Likewise, to manage this application, keep referring to it as `foo/bar`: ```bash # Create an application argocd app create foo/bar ... # Sy... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/app-any-namespace.md | master | argo-cd | [
-0.0433395579457283,
-0.08167142421007156,
-0.11513810604810715,
-0.029442479833960533,
-0.08048883825540543,
-0.06947554647922516,
0.1115754246711731,
0.017430076375603676,
0.018573028966784477,
0.02836489863693714,
0.04769022390246391,
-0.014349391683936119,
0.01399392168968916,
-0.04803... | 0.119289 |
# Application Sync using impersonation > [!WARNING] > \*\*Beta Feature (Since v3.5.0)\*\* > > This is a [beta-quality](https://github.com/argoproj/argoproj/blob/main/community/feature-status.md#beta) > feature that allows you to control the service account used for the sync operation. The configured service account > c... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/app-sync-using-impersonation.md | master | argo-cd | [
-0.07095887511968613,
-0.04248189553618431,
-0.07987385988235474,
-0.018282392993569374,
-0.05694121867418289,
-0.049319200217723846,
0.10056883841753006,
-0.05976256728172302,
-0.06961406767368317,
0.0701330378651619,
0.01616564579308033,
0.03933483362197876,
-0.0005416700732894242,
-0.01... | 0.082356 |
tenants can self-service their Argo applications in their respective tenant namespaces and no additional access needs to be provided for the control plane namespace. ## Implementation details ### Overview In order for an application to use a different service account for the application sync operation, the following st... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/app-sync-using-impersonation.md | master | argo-cd | [
-0.03025059960782528,
-0.10180257260799408,
-0.10914325714111328,
-0.04244206100702286,
-0.09479226917028427,
-0.061644457280635834,
0.11303988844156265,
-0.08873461186885834,
-0.03951387107372284,
0.07286272943019867,
0.031346775591373444,
-0.036278136074543,
-0.013725816272199154,
0.0530... | 0.036308 |
For example, to add a destination service account for `in-cluster` and `guestbook` namespace, you can use the following CLI command: ```shell argocd proj add-destination-service-account my-project https://kubernetes.default.svc guestbook guestbook-sa ``` Likewise, to remove the destination service account from an `AppP... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/app-sync-using-impersonation.md | master | argo-cd | [
-0.007059640716761351,
-0.041989535093307495,
-0.09525057673454285,
-0.04413939639925957,
-0.013824588619172573,
0.03147227317094803,
0.0926390290260315,
-0.05310098081827164,
0.06057232245802879,
0.09860904514789581,
0.004941707476973534,
-0.09989351034164429,
0.03127320110797882,
-0.0595... | 0.113598 |
# RBAC Configuration The RBAC feature enables restrictions of access to Argo CD resources. Argo CD does not have its own user management system and has only one built-in user, `admin`. The `admin` user is a superuser and it has unrestricted access to the system. RBAC requires [SSO configuration](user-management/index.m... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/rbac.md | master | argo-cd | [
-0.0036963948514312506,
-0.08313186466693878,
-0.18112212419509888,
0.050290580838918686,
-0.03272266685962677,
-0.007974052801728249,
0.08127940446138382,
0.01260586827993393,
-0.07120778411626816,
0.022095676511526108,
-0.024836042895913124,
0.053135860711336136,
0.03724006563425064,
0.0... | 0.142565 |
table that summarizes all possible resources and which actions are valid for each of them. | Resource\Action | get | create | update | delete | sync | action | override | invoke | | :------------------ | :-: | :----: | :----: | :----: | :--: | :----: | :------: | :----: | | \*\*applications\*\* | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/rbac.md | master | argo-cd | [
-0.030795125290751457,
-0.08088646084070206,
-0.120928093791008,
0.012581617571413517,
0.00810939073562622,
0.027596190571784973,
0.08754398673772812,
-0.0018616955494508147,
-0.05114983022212982,
0.07969673722982407,
0.01933414489030838,
-0.09467464685440063,
0.08161511272192001,
-0.02263... | 0.127457 |
be a problem, because resource kinds generally contain capital > letters, and namespaces cannot contain capital letters. However, it is possible for a resource kind to be lowercase. > So it is better to just always include all the parts of the resource in the pattern (in other words, always use four > slashes). If we w... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/rbac.md | master | argo-cd | [
-0.04664402827620506,
0.06311126053333282,
-0.0016127460403367877,
-0.04653656482696533,
-0.019568977877497673,
-0.049675244837999344,
0.04142368957400322,
-0.02376117929816246,
0.06219257786870003,
0.05412886664271355,
0.022617187350988388,
0.00786068756133318,
0.08458657562732697,
0.0415... | 0.111424 |
`override`, to prevent synchronizing to arbitrary revisions other than the revision(s) given in the `Application` object. Similar as syncing to an arbitrary yaml manifest, syncing to a different revision/branch/commit will also bring the controlled objects to a state differing, and thus OufOfSync from the state as defi... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/rbac.md | master | argo-cd | [
-0.08022364974021912,
-0.015897588804364204,
-0.016037527471780777,
-0.026142258197069168,
-0.00487126037478447,
-0.046602047979831696,
0.022685764357447624,
-0.022760525345802307,
0.03161701187491417,
0.05237753689289093,
-0.004010315518826246,
0.020934859290719032,
-0.01541502308100462,
... | 0.057448 |
configured group that the user is part of. The matching engine, configured in `policy.matchMode`, can use two different match modes to compare the values of tokens: - `glob`: based on the [`glob` package](https://pkg.go.dev/github.com/gobwas/glob). - `regex`: based on the [`regexp` package](https://pkg.go.dev/regexp). ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/rbac.md | master | argo-cd | [
-0.06849250197410583,
0.09056343138217926,
0.011636371724307537,
-0.05164355784654617,
0.012881307862699032,
-0.008747509680688381,
0.09444402158260345,
-0.024288441985845566,
0.00029610402998514473,
-0.05832541361451149,
0.0546589195728302,
0.015222093090415001,
0.017082352191209793,
0.03... | 0.069477 |
this may be a problem is if your SSO provider is an SCM, and org members are automatically > granted scopes named after the orgs. If a user can create or add themselves to an org in the SCM, they can gain the > permissions of the local user with the same name. > > To avoid ambiguity, if you are using local users and SS... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/rbac.md | master | argo-cd | [
-0.0030831072945147753,
-0.04179857298731804,
-0.13034705817699432,
0.010330366902053356,
-0.0355626717209816,
-0.020389363169670105,
0.08373839408159256,
-0.047693055123090744,
-0.051219772547483444,
0.07147430628538132,
0.0011056934017688036,
-0.015465601347386837,
0.029496248811483383,
... | -0.002814 |
# Feature Maturity Argo CD features may be marked with a certain [status](https://github.com/argoproj/argoproj/blob/main/community/feature-status.md) to indicate their stability and maturity. These are the statuses of non-stable features in Argo CD: > [!CAUTION] > \*\*Using Alpha/Beta features risks\*\* > > Alpha and B... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/feature-maturity.md | master | argo-cd | [
0.02383541315793991,
-0.0257852952927351,
-0.01462979894131422,
0.012533226050436497,
0.024985961616039276,
-0.04095396772027016,
-0.02589644119143486,
-0.04819951951503754,
-0.1406375765800476,
0.04053302854299545,
0.019058916717767715,
0.07681634277105331,
-0.13255693018436432,
-0.006377... | 0.102069 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.