content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
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 |
of label selected by your Prometheus. ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: argocd-metrics labels: release: prometheus-operator spec: selector: matchLabels: app.kubernetes.io/name: argocd-metrics endpoints: - port: metrics ``` ```yaml apiVersion: monitoring.coreos.com/v1 kind... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/metrics.md | master | argo-cd | [
0.0030178858432918787,
0.005718938075006008,
-0.06504707783460617,
-0.020189722999930382,
0.035513944923877716,
-0.01957220584154129,
0.054387349635362625,
-0.04335371032357216,
0.08094337582588196,
0.04222797602415085,
0.008073095232248306,
-0.09673258662223816,
-0.041525207459926605,
-0.... | 0.215573 |
# 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.0073196860030293465,
-0.06489657610654831,
-0.10144712775945663,
-0.03243028372526169,
-0.025859860703349113,
-0.026137499138712883,
0.045357845723629,
-0.013965655118227005,
-0.041147418320178986,
0.042395275086164474,
0.022685715928673744,
-0.04664184898138046,
0.012760655023157597,
0... | 0.120435 |
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 |
previously, for applications in the Argo CD's control plane namespace, you can omit the namespace from the application name. ### Using the UI Similar to the CLI, you can refer to the application in the UI as `foo/bar`. For example, to create an application named `bar` in the namespace `foo` in the web UI, set the appli... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/app-any-namespace.md | master | argo-cd | [
-0.05707525461912155,
-0.030851691961288452,
-0.09482470154762268,
-0.023623231798410416,
-0.127988800406456,
-0.06436482816934586,
0.07140399515628815,
0.037045594304800034,
0.03740403428673744,
0.010214745998382568,
-0.024799834936857224,
-0.06865943968296051,
0.043622881174087524,
-0.00... | 0.115215 |
# Application Sync using impersonation > [!WARNING] > \*\*Alpha Feature (Since 2.13.0)\*\* > > This is an experimental, [alpha-quality](https://github.com/argoproj/argoproj/blob/main/community/feature-status.md#alpha) > feature that allows you to control the service account used for the sync operation. The configured s... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/app-sync-using-impersonation.md | master | argo-cd | [
-0.05255023390054703,
-0.03840773552656174,
-0.10197596251964569,
-0.032749492675065994,
-0.06310270726680756,
-0.05353833734989166,
0.10502855479717255,
-0.056484565138816833,
-0.06548189371824265,
0.05946185439825058,
0.02719924785196781,
0.03780028596520424,
-0.012497852556407452,
-0.01... | 0.078542 |
admin can choose to use either the [apps-in-any-namespace](./app-any-namespace.md) feature or provide access to tenants to create applications in the ArgoCD control plane namespace. 5. If the platform admin chooses apps-in-any-namespace feature, tenants can self-service their Argo applications in their respective tenan... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/app-sync-using-impersonation.md | master | argo-cd | [
-0.038210317492485046,
-0.11982274800539017,
-0.12443390488624573,
-0.0591428317129612,
-0.07411331683397293,
-0.05775710567831993,
0.10533349961042404,
-0.08439763635396957,
-0.03941923752427101,
0.07814063131809235,
0.030456213280558586,
-0.02711506560444832,
0.019598251208662987,
0.0496... | 0.008362 |
guestbook-stage defaultServiceAccount: guestbook-stage-deployer - server: https://kubernetes.default.svc # catch-all configuration namespace: '\*' defaultServiceAccount: default ``` ### Using the CLI Destination service accounts can be added to an `AppProject` using the ArgoCD CLI. For example, to add a destination ser... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/app-sync-using-impersonation.md | master | argo-cd | [
0.002536583226174116,
-0.04274750128388405,
-0.08822529762983322,
-0.05232490226626396,
-0.036347776651382446,
0.024361424148082733,
0.08277017623186111,
-0.04453374817967415,
0.06558390706777573,
0.09404507279396057,
0.01345647033303976,
-0.09490473568439484,
0.03841124102473259,
-0.04462... | 0.08139 |
# 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 |
| :------: | :----: | | \*\*applications\*\* | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | | \*\*applicationsets\*\* | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ | | \*\*clusters\*\* | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ | | \*\*projects\*\* | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ | | \*\*repositories\*\* | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ | | \*\*accounts\*\*... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/rbac.md | master | argo-cd | [
-0.04141738638281822,
-0.06395251303911209,
-0.1302173137664795,
-0.007555168587714434,
-0.008871146477758884,
-0.0062624444253742695,
0.12341982871294022,
0.021066149696707726,
-0.07220739871263504,
0.0440022237598896,
0.04535072669386864,
-0.07643700391054153,
0.10488034039735794,
-0.065... | 0.06321 |
words, always use four > slashes). If we want to grant access to the user to update all resources of an application, but not the application itself: ```csv p, example-user, applications, update/\*, default/prod-app, allow ``` If we want to explicitly deny delete of the application, but allow the user to delete Pods: ``... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/rbac.md | master | argo-cd | [
-0.03583787381649017,
0.032585371285676956,
-0.04415017366409302,
-0.06746325641870499,
-0.006228061392903328,
-0.045475054532289505,
0.046870335936546326,
-0.017859289422631264,
0.04501504451036453,
0.0784926563501358,
0.055574361234903336,
-0.03272739052772522,
0.05725134164094925,
0.032... | 0.120399 |
the `Application`. The default setting of this flag is 'false', to prevent breaking changes in existing installations. It is recommended to set this setting to 'true' and only grant the `override` privilege per AppProject to the users that actually need this behavior. ### The `applicationsets` resource The `application... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/rbac.md | master | argo-cd | [
-0.07248824834823608,
-0.0032273815013468266,
-0.05365409702062607,
-0.045756660401821136,
-0.0037442240864038467,
-0.006949617061764002,
0.016172921285033226,
0.041055694222450256,
-0.00014531747729051858,
0.05984419584274292,
-0.041688285768032074,
-0.0038407144602388144,
0.045846734195947... | 0.051998 |
effect will be returned. The evaluation will continue until all matching policies are evaluated, or until a policy with the `deny` effect matches. After all policies are evaluated, if there was at least one `allow` effect and no `deny`, access will be granted. ### Glob matching When `glob` is used, the policy tokens ar... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/rbac.md | master | argo-cd | [
-0.07266059517860413,
0.03325729817152023,
0.016749370843172073,
-0.03672875463962555,
0.041212134063243866,
-0.05386189743876457,
0.08108324557542801,
-0.002041201340034604,
-0.019213343039155006,
-0.011081942357122898,
0.08350895345211029,
0.009871987625956535,
0.03360805660486221,
0.019... | 0.114022 |
to assign policies directly to local > users, and not to assign roles to local users. In other words, instead of using `g, my-local-user, role:admin`, you > should explicitly assign policies to `my-local-user`: > > ```yaml > p, my-local-user, \*, \*, \*, allow > ``` ## Policy CSV Composition It is possible to provide a... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/rbac.md | master | argo-cd | [
-0.004984365310519934,
-0.001947899116203189,
-0.08215773105621338,
-0.0073096780106425285,
-0.03533653914928436,
-0.008442733436822891,
0.11501361429691315,
-0.01508922129869461,
-0.06136980652809143,
0.062340445816516876,
0.016295384615659714,
-0.06593828648328781,
0.0472865104675293,
-0... | 0.018626 |
# 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 |
../user-guide/source-hydrator.md | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/feature-maturity.md | master | argo-cd | [
-0.08032239228487015,
0.03734903782606125,
-0.026961125433444977,
-0.024726752191781998,
0.09154874086380005,
-0.05190147086977959,
0.03102654591202736,
0.038293857127428055,
0.01485099270939827,
-0.083952397108078,
-0.045045845210552216,
-0.01917511597275734,
-0.0035613160580396652,
0.008... | 0.032753 |
# Custom Styles Argo CD imports the majority of its UI stylesheets from the [argo-ui](https://github.com/argoproj/argo-ui) project. Sometimes, it may be desired to customize certain components of the UI for branding purposes or to help distinguish between multiple instances of Argo CD running in different environments.... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/custom-styles.md | master | argo-cd | [
-0.02643105573952198,
0.0021521716844290495,
-0.07452806830406189,
0.028709476813673973,
-0.015756648033857346,
-0.05717284977436066,
0.04421934857964516,
-0.016523361206054688,
-0.04279984533786774,
0.08032023161649704,
-0.025580888614058495,
0.021057194098830223,
-0.016539374366402626,
-... | 0.096505 |
# Web-based Terminal  Since v2.4, Argo CD has a web-based terminal that allows you to get a shell inside a running pod just like you would with `kubectl exec`. It's basically SSH from your browser, full ANSI color support and all! However, for security this feature is disabled... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/web_based_terminal.md | master | argo-cd | [
0.06846631318330765,
0.0035770044196397066,
-0.04523630440235138,
-0.023928236216306686,
-0.05035274848341942,
-0.026136038824915886,
0.055821508169174194,
0.022032614797353745,
0.07739121466875076,
0.08813495934009552,
-0.011807882227003574,
-0.02094532735645771,
-0.027416445314884186,
-0... | 0.215915 |
# Cluster Bootstrapping This guide is for operators who have already installed Argo CD, and have a new cluster and are looking to install many apps in that cluster. There's no one particular pattern to solve this problem, e.g. you could write a script to create your apps, or you could even manually create them. Our rec... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/cluster-bootstrapping.md | master | argo-cd | [
0.012626993469893932,
-0.04218960553407669,
-0.09139830619096756,
-0.02693472057580948,
-0.0037018454167991877,
0.01729998178780079,
0.022563207894563675,
0.009115876629948616,
-0.03820119425654411,
0.0315629206597805,
0.007928763516247272,
-0.08222400397062302,
0.03307339921593666,
-0.002... | 0.157703 |
you can set it to HEAD or a branch name. As you probably want to override the cluster server, this is a templated values. `values.yaml` contains the default values: ```yaml spec: destination: server: https://kubernetes.default.svc ``` Next, you need to create and sync your parent app, e.g. via the CLI: ```bash argocd a... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/cluster-bootstrapping.md | master | argo-cd | [
-0.006032008212059736,
-0.06685616821050644,
-0.07180025428533554,
-0.004835138563066721,
-0.04528270661830902,
-0.035517994314432144,
0.027482330799102783,
0.02006068080663681,
0.07339636981487274,
0.080581434071064,
0.009624805301427841,
-0.004496181849390268,
-0.03763327747583389,
-0.01... | 0.139663 |
# UI Customization ## Default Application Details View By default, the Application Details will show the `Tree` view. This can be configured on an Application basis, by setting the `pref.argocd.argoproj.io/default-view` annotation, accepting one of: `tree`, `pods`, `network`, `list` as values. For the Pods view, the de... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/ui-customization.md | master | argo-cd | [
0.028126303106546402,
-0.005149154458194971,
-0.030956020578742027,
0.02214425429701805,
0.01350704301148653,
0.026320403441786766,
0.010144567117094994,
0.021519623696804047,
0.020310884341597557,
0.07413528859615326,
-0.023182542994618416,
-0.04261472821235657,
-0.05814759433269501,
-0.0... | 0.194857 |
# Installation Argo CD has two type of installations: multi-tenant and core. ## Multi-Tenant The multi-tenant installation is the most common way to install Argo CD. This type of installation is typically used to service multiple application developer teams in the organization and maintained by a platform team. The end... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/installation.md | master | argo-cd | [
0.018396446481347084,
-0.058198943734169006,
-0.06990064680576324,
-0.060558851808309555,
-0.039464887231588364,
-0.07296203076839447,
0.0396808497607708,
0.012174179777503014,
-0.00010330935037927702,
0.06633797287940979,
0.04233158752322197,
0.02895023301243782,
-0.0631069615483284,
-0.0... | 0.19607 |
include the manifest as a remote resource and apply additional customizations using Kustomize patches. ```yaml apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization namespace: argocd resources: - https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml ``` For an example of this, see t... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/installation.md | master | argo-cd | [
0.008795120753347874,
-0.014360706321895123,
-0.01582796685397625,
-0.06015416607260704,
-0.06922446191310883,
-0.028630955144762993,
0.05480369180440903,
-0.008279712870717049,
-0.053160250186920166,
0.09889634698629379,
-0.014406479895114899,
0.004818149376660585,
-0.045679863542318344,
... | 0.17733 |
# Ingress Configuration Argo CD API server runs both a gRPC server (used by the CLI), as well as a HTTP/HTTPS server (used by the UI). Both protocols are exposed by the argocd-server service object on the following ports: \* 443 - gRPC/HTTPS \* 80 - HTTP (redirects to HTTPS) There are several ways how Ingress can be co... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/ingress.md | master | argo-cd | [
-0.027490342035889626,
0.04558444023132324,
-0.04877995327115059,
-0.0377364344894886,
-0.06850330531597137,
-0.08172160387039185,
0.015996290370821953,
-0.05971285700798035,
0.0676191970705986,
0.08373071998357773,
-0.000745279947295785,
-0.047004688531160355,
-0.01232096366584301,
0.0121... | 0.181414 |
host: internal.path.to.argocd.io http: paths: - path: / pathType: Prefix backend: service: name: argocd-server port: name: http tls: - hosts: - internal.path.to.argocd.io secretName: your-certificate-name ``` Internal gRPC Ingress: ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: argocd-server-grp... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/ingress.md | master | argo-cd | [
-0.01055455207824707,
0.014474468305706978,
-0.055705927312374115,
-0.02423548325896263,
-0.0001776835269993171,
-0.1028592512011528,
0.037503551691770554,
-0.024649551138281822,
0.09442273527383804,
0.07938141375780106,
0.02365395426750183,
-0.05995837599039078,
-0.06136952340602875,
0.03... | 0.157738 |
gRPC. Each ingress will be for a different domain (`argocd.example.com` and `grpc.argocd.example.com`). This requires that the Ingress resources use different TLS `secretName`s to avoid unexpected behavior. HTTP/HTTPS Ingress: ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: argocd-server-http-ing... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/ingress.md | master | argo-cd | [
-0.034247659146785736,
0.00325694028288126,
-0.020728081464767456,
-0.029259871691465378,
-0.05781462416052818,
-0.09808803349733353,
0.0506342314183712,
-0.09008379280567169,
0.12346354871988297,
0.04268011078238487,
-0.0350043922662735,
-0.053944673389196396,
-0.0015074691036716104,
0.04... | 0.078424 |
health check to return the gRPC health status code `OK - 0` from the argocd-server by setting the health check path to `/grpc.health.v1.Health/Check`. By default, the ALB health check for gRPC returns the status code `UNIMPLEMENTED - 12` on health check path `/AWS.ALB/healthcheck`. ```yaml apiVersion: networking.k8s.io... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/ingress.md | master | argo-cd | [
0.011883135885000229,
0.05189333111047745,
-0.0705086961388588,
-0.018675025552511215,
-0.026135418564081192,
-0.09047243744134903,
0.032579317688941956,
-0.07699743658304214,
0.0601075179874897,
0.07191968709230423,
-0.006158299744129181,
-0.04754111170768738,
-0.04993593692779541,
-0.040... | 0.104074 |
Google integrations, you can check the [Google docs on configuring Ingress features](https://cloud.google.com/kubernetes-engine/docs/how-to/ingress-features) ### Disable internal TLS First, to avoid internal redirection loops from HTTP to HTTPS, the API server should be run with TLS disabled. Edit the `--insecure` flag... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/ingress.md | master | argo-cd | [
-0.05543352663516998,
0.0025509661063551903,
0.003351053688675165,
-0.027322856709361076,
-0.07962384074926376,
-0.06379102915525436,
0.021294068545103073,
-0.051416315138339996,
0.003280197735875845,
0.07016728073358536,
-0.033982109278440475,
-0.04936007037758827,
0.006457366514950991,
-... | 0.100495 |
can take some minutes to deploy the load balancer and become ready to accept connections. Once it's ready, get the public IP address for your Load Balancer, go to your DNS server (Google or third party) and point your domain or subdomain (i.e. argocd.example.com) to that IP address. You can get that IP address describi... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/ingress.md | master | argo-cd | [
-0.07596935331821442,
-0.04441449046134949,
0.007438183296471834,
-0.061563536524772644,
-0.11909123510122299,
-0.0743384137749672,
0.05544891580939293,
-0.08026254177093506,
0.03422028198838234,
0.05542004108428955,
-0.04803488776087761,
-0.045470353215932846,
-0.0228028055280447,
-0.1019... | 0.048841 |
kind: Secret group: "" ``` To automate certificate management, `cert-manager` supports [gateway annotations](https://cert-manager.io/docs/usage/gateway/). #### Securing traffic between Argo CD and the gateway If your security requirements allow it, the Argo CD API server can be run with TLS disabled: pass the `--insecu... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/ingress.md | master | argo-cd | [
-0.0495421476662159,
0.0724782794713974,
-0.12027104198932648,
0.05334581062197685,
-0.042114224284887314,
-0.05929309129714966,
0.0404156818985939,
-0.007005379069596529,
0.0027029758784919977,
0.08087180554866791,
-0.011928694322705269,
-0.017025897279381752,
0.011501521803438663,
-0.012... | 0.099596 |
# Resource Health ## Overview Argo CD provides built-in health assessment for several standard Kubernetes types, which is then surfaced to the overall Application health status as a whole. The following checks are made for specific types of Kubernetes resources: ### Deployment, ReplicaSet, StatefulSet, DaemonSet \* Obs... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/health.md | master | argo-cd | [
-0.05982375890016556,
0.04853164777159691,
-0.004485638812184334,
0.006629785522818565,
-0.008004609495401382,
-0.040948934853076935,
0.05724130570888519,
-0.017664477229118347,
0.020992513746023178,
0.0689467117190361,
-0.038100313395261765,
-0.07684552669525146,
-0.013012164272367954,
-0... | 0.263807 |
do not work since wildcards (`\*`) are not supported in Kubernetes configmap keys. The `obj` is a global variable which contains the resource. The script must return an object with status and optional message field. The custom health check might return one of the following health statuses: \* `Healthy` - the resource i... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/health.md | master | argo-cd | [
-0.0005283425562083721,
0.0535699687898159,
0.009921344928443432,
0.02450648322701454,
0.02768206223845482,
-0.047820039093494415,
0.03114454075694084,
0.01441462617367506,
0.052445441484451294,
0.008304142393171787,
0.02039143070578575,
-0.05403873324394226,
-0.02340077795088291,
-0.00223... | 0.121958 |
checks: \* PersistentVolumeClaim \* Pod \* Service \* apiregistration.k8s.io/APIService \* apps/DaemonSet \* apps/Deployment \* apps/ReplicaSet \* apps/StatefulSet \* argoproj.io/Workflow \* autoscaling/HorizontalPodAutoscaler \* batch/Job \* extensions/Ingress \* networking.k8s.io/Ingress ## Health Checks Argo CD App ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/health.md | master | argo-cd | [
-0.058347318321466446,
0.07562389969825745,
-0.02194196730852127,
0.014055873267352581,
0.036165956407785416,
-0.05220281332731247,
0.1071339026093483,
0.010287458077073097,
-0.013283398933708668,
0.09762673079967499,
0.017321504652500153,
-0.03302079439163208,
0.02604203298687935,
0.00703... | 0.261093 |
# Security Argo CD has undergone rigorous internal security reviews and penetration testing to satisfy [PCI compliance](https://www.pcisecuritystandards.org) requirements. The following are some security topics and implementation details of Argo CD. ## Authentication Authentication to Argo CD API server is performed ex... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/security.md | master | argo-cd | [
-0.098058320581913,
0.019572945311665535,
-0.06895797699689865,
-0.003630260704085231,
-0.023477360606193542,
-0.07909422367811203,
0.05797109752893448,
-0.027038563042879105,
0.0334189273416996,
0.03958688676357269,
-0.012684183195233345,
0.0719728022813797,
-0.006496714893728495,
-0.0541... | 0.161923 |
config management tools, helm and kustomize. When rendering manifests, Argo CD executes these config management tools (i.e. `helm template`, `kustomize build`) to generate the manifests. It is possible that an attacker with write access to a trusted git repository may construct malicious helm charts or kustomizations t... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/security.md | master | argo-cd | [
-0.028988031670451164,
0.033639028668403625,
-0.016281789168715477,
0.009106470271945,
0.037933144718408585,
-0.055022601038217545,
0.07786015421152115,
0.000042396775825181976,
0.05426272377371788,
0.051910653710365295,
0.05029943585395813,
0.04193297028541565,
0.0404319129884243,
-0.0323... | 0.109918 |
NOTE: for AWS EKS clusters, the [get-token](https://docs.aws.amazon.com/cli/latest/reference/eks/get-token.html) command is used to authenticate to the external cluster, which uses IAM roles in lieu of locally stored tokens, so token rotation is not needed, and revocation is handled through IAM. ## Cluster RBAC By defa... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/security.md | master | argo-cd | [
-0.02206508070230484,
0.0009557898156344891,
-0.0666101947426796,
0.06437288224697113,
-0.015699006617069244,
-0.011580940335988998,
0.08970537036657333,
-0.01914609782397747,
0.05357036367058754,
0.11332683265209198,
0.027654021978378296,
0.03216294199228287,
0.030505722388625145,
-0.0713... | 0.199651 |
Level | Friendly Level | Description | Example | |-------|----------------|---------------------------------------------------------------------------------------------------|---------------------------------------------| | 1 | Low | Unexceptional, non-malicious events | Successful access | | 2 | Medium | Could indicat... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/security.md | master | argo-cd | [
-0.029161961749196053,
-0.021075984463095665,
-0.045414507389068604,
-0.012998350895941257,
0.04219450801610947,
-0.057230520993471146,
0.04992983490228653,
0.03524855896830559,
-0.01803326979279518,
0.0065713124349713326,
0.07716935127973557,
0.011110913008451462,
0.11160401254892349,
-0.... | 0.105257 |
# Git Generator The Git generator contains two subtypes: the Git directory generator, and Git file generator. > [!WARNING] > Git generators are often used to make it easier for (non-admin) developers to create Applications. > If the `project` field in your ApplicationSet is templated, developers may be able to create A... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Git.md | master | argo-cd | [
-0.09993907809257507,
-0.01591646485030651,
-0.08812226355075836,
-0.003351247403770685,
0.0026963192503899336,
-0.0791454017162323,
0.0527421198785305,
0.04766644164919853,
0.011414389126002789,
0.004375266842544079,
-0.009609665721654892,
-0.05245325714349747,
0.1259215772151947,
-0.0285... | 0.031214 |
namespace: argocd spec: goTemplate: true goTemplateOptions: ["missingkey=error"] generators: - git: repoURL: https://github.com/argoproj/argo-cd.git revision: HEAD directories: - path: applicationset/examples/git-generator-directory/excludes/cluster-addons/\* - path: applicationset/examples/git-generator-directory/excl... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Git.md | master | argo-cd | [
-0.0006363205029629171,
0.032498009502887726,
-0.06364364176988602,
0.03997042775154114,
0.042028944939374924,
-0.0011675350833684206,
0.025843506678938866,
-0.04438665136694908,
0.06399061530828476,
0.05053118243813515,
0.05479441210627556,
-0.07286322861909866,
-0.040729667991399765,
-0.... | 0.107858 |
a specified repository. Suppose you have a Git repository with the following directory structure: ``` ├── apps │ └── guestbook │ ├── guestbook-ui-deployment.yaml │ ├── guestbook-ui-svc.yaml │ └── kustomization.yaml ├── cluster-config │ └── engineering │ ├── dev │ │ └── config.json │ └── prod │ └── config.json └── git-g... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Git.md | master | argo-cd | [
-0.00979529321193695,
0.014724958688020706,
-0.039668843150138855,
0.02536872960627079,
0.08374389261007309,
-0.04559437930583954,
0.03344447910785675,
-0.029139941558241844,
0.09167465567588806,
0.02791452407836914,
0.08095470070838928,
-0.05133455991744995,
0.04728517308831215,
-0.045550... | 0.094099 |
Globbing](./Generators-Git-File-Globbing.md) for more information. ### Exclude files The Git file generator also supports an `exclude` option in order to exclude files in the repository from being scanned by the ApplicationSet controller: ```yaml apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: gue... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Git.md | master | argo-cd | [
-0.006179583724588156,
0.06461954861879349,
-0.0652027428150177,
0.012692508287727833,
0.06628229469060898,
-0.03749219328165054,
0.04752353951334953,
-0.05117198824882507,
0.032472189515829086,
0.010545309633016586,
0.06358115375041962,
-0.003824437502771616,
0.002592569449916482,
-0.1060... | 0.06586 |
as a service of type ClusterIP. An ApplicationSet specific Ingress resource needs to be created to expose this service to the webhook source. ### 1. Create the webhook in the Git provider In your Git provider, navigate to the settings page where webhooks can be configured. The payload URL configured in the Git provider... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Git.md | master | argo-cd | [
-0.08241603523492813,
0.0003172859433107078,
-0.09224157780408859,
0.02797936461865902,
-0.010077989660203457,
-0.0464114174246788,
0.029692599549889565,
0.02640657126903534,
0.0695875808596611,
0.022598205134272575,
0.03339991718530655,
-0.08380800485610962,
0.06961814314126968,
-0.025869... | 0.122603 |
# Templates The template fields of the ApplicationSet `spec` are used to generate Argo CD `Application` resources. ApplicationSet is using [fasttemplate](https://github.com/valyala/fasttemplate) but will be soon deprecated in favor of Go Template. ## Template fields An Argo CD Application is created by combining the pa... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Template.md | master | argo-cd | [
0.007774469908326864,
0.10525866597890854,
-0.08956032246351242,
0.012056355364620686,
0.03084806352853775,
0.0184367373585701,
0.006960485130548477,
0.04092349484562874,
-0.01306107733398676,
-0.0030440371483564377,
0.03039693459868431,
-0.03815096244215965,
-0.06118038669228554,
-0.05040... | 0.183888 |
thus be thought of as patches against the outer `spec`-level template fields. ```yaml apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: guestbook spec: generators: - list: elements: - cluster: engineering-dev url: https://kubernetes.default.svc template: metadata: {} spec: project: "default" source:... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Template.md | master | argo-cd | [
0.012623484246432781,
0.0682225376367569,
-0.03807438910007477,
0.0332261361181736,
0.018708067014813423,
0.008681842125952244,
0.013858099468052387,
0.0005262147169560194,
0.0388936884701252,
0.07959283888339996,
-0.01157869677990675,
-0.03278264030814171,
-0.09274214506149292,
-0.0722550... | 0.140284 |
# How ApplicationSet controller interacts with Argo CD When you create, update, or delete an `ApplicationSet` resource, the ApplicationSet controller responds by creating, updating, or deleting one or more corresponding Argo CD `Application` resources. In fact, the \*sole\* responsibility of the ApplicationSet controll... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Argo-CD-Integration.md | master | argo-cd | [
-0.023291051387786865,
-0.0426681749522686,
-0.06947380304336548,
-0.015183741226792336,
-0.012274542823433876,
-0.03287216275930405,
0.11675088107585907,
-0.03879870846867561,
0.10746452212333679,
0.07601708173751831,
0.034229159355163574,
-0.01574619673192501,
0.0016703229630365968,
-0.0... | 0.201568 |
# Plugin Generator The Plugin generator is a generator type which allows you to provide your own custom generator through a plugin. In contrast to other generators with predetermined logic (the [Cluster generator](Generators-Cluster.md) fetching clusters using a selector on ArgoCD secrets, [Git generator](Generators-Gi... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Plugin.md | master | argo-cd | [
-0.11671898514032364,
-0.03887180984020233,
-0.19908908009529114,
0.05530219152569771,
-0.03234037011861801,
-0.01794888637959957,
-0.027702676132321358,
-0.01500936783850193,
-0.08046237379312515,
0.05831589177250862,
0.03644378483295441,
-0.023076534271240234,
0.011461044661700726,
-0.04... | 0.169849 |
the functionality of the generator. ### Add a ConfigMap to configure the access of the plugin ```yaml apiVersion: v1 kind: ConfigMap metadata: name: my-plugin namespace: argocd data: token: "$plugin.myplugin.token" # Alternatively $:plugin.myplugin.token baseUrl: "http://myplugin.plugin-ns.svc.cluster.local." requestTi... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Plugin.md | master | argo-cd | [
-0.10265517234802246,
-0.011151377111673355,
-0.11039627343416214,
0.06490218639373779,
-0.029112208634614944,
-0.007796245161443949,
-0.005047375336289406,
-0.0276576429605484,
0.07465630769729614,
0.07482097297906876,
0.007955249398946762,
-0.056550342589616776,
-0.05355517193675041,
-0.... | 0.153265 |
goTemplate: true goTemplateOptions: ["missingkey=error"] generators: - matrix: generators: - pullRequest: github: ... requeueAfterSeconds: 30 - plugin: configMapRef: name: cm-plugin input: parameters: branch: "{{.branch}}" # provided by generator pull request values: branchLink: "https://git.example.com/org/repo/tree/{... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Plugin.md | master | argo-cd | [
0.023685947060585022,
0.031004291027784348,
-0.09492653608322144,
0.036648839712142944,
0.030673794448375702,
0.04528135433793068,
-0.06351911276578903,
0.028466658666729927,
0.0017442986136302352,
0.044592611491680145,
0.03278760612010956,
-0.07686018198728561,
0.001870273845270276,
-0.06... | -0.00095 |
# Cluster Decision Resource Generator The cluster decision resource generates a list of Argo CD clusters. This is done using [duck-typing](https://pkg.go.dev/knative.dev/pkg/apis/duck), which does not require knowledge of the full shape of the referenced Kubernetes resource. The following is an example of a cluster-dec... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Cluster-Decision-Resource.md | master | argo-cd | [
-0.01076908502727747,
0.019823463633656502,
-0.09951601177453995,
0.009860451333224773,
0.04408957436680794,
0.010550525039434433,
0.08779522776603699,
-0.06011499837040901,
0.061483997851610184,
0.04176309332251549,
-0.025109367445111275,
-0.10288073867559433,
-0.016951775178313255,
-0.04... | 0.133588 |
create clusters within Argo CD. > > The Default Cluster list key is `clusters`. | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Cluster-Decision-Resource.md | master | argo-cd | [
0.05758753791451454,
-0.12384583801031113,
-0.11732941120862961,
0.03493167832493782,
-0.0025905047077685595,
-0.030757885426282883,
-0.01797819323837757,
-0.0355420783162117,
-0.05567535385489464,
0.07150696963071823,
0.03883098438382149,
-0.05386538803577423,
-0.036636728793382645,
0.009... | 0.148456 |
# Generators Generators are responsible for generating \*parameters\*, which are then rendered into the `template:` fields of the ApplicationSet resource. See the [Introduction](index.md) for an example of how generators work with templates, to create Argo CD Applications. Generators are primarily based on the data sou... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators.md | master | argo-cd | [
-0.11348625272512436,
0.025345519185066223,
-0.06033260375261307,
0.06677751243114471,
0.026792820543050766,
-0.013533351942896843,
0.06253873556852341,
-0.020903445780277252,
-0.01406064908951521,
-0.011989227496087551,
-0.026922928169369698,
-0.022069737315177917,
0.07093744724988937,
-0... | 0.188941 |
# ApplicationSet in any namespace > [!WARNING] > \*\*Beta Feature (Since v2.8.0)\*\* > > This feature is in the [Beta](https://github.com/argoproj/argoproj/blob/main/community/feature-status.md#beta) stage. > It is generally considered stable, but there may be unhandled edge cases. > [!WARNING] > Please read this docum... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Appset-Any-Namespace.md | master | argo-cd | [
-0.06923230737447739,
-0.06521764397621155,
-0.062327753752470016,
0.035033777356147766,
-0.01735547184944153,
-0.05646953359246254,
0.1050058975815773,
0.014297631569206715,
-0.05739375948905945,
0.041343361139297485,
-0.013754650019109249,
0.010804654099047184,
-0.010703192092478275,
-0.... | 0.139078 |
applies even when AppSets-in-any-namespace is disabled, but is especially important when it is enabled, since non-Argo-admins may attempt to reference out-of-bounds secrets in the `argocd` namespace from an AppSet `tokenRef`. When this mode is enabled, the referenced secret must have a label `argocd.argoproj.io/secret-... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Appset-Any-Namespace.md | master | argo-cd | [
-0.059608399868011475,
-0.08108332008123398,
-0.12833558022975922,
0.002332541858777404,
0.00542221125215292,
-0.05083984136581421,
0.07581348717212677,
0.03882604092359543,
-0.021740073338150978,
0.0899658128619194,
0.05890844762325287,
-0.03751394897699356,
0.002299903193488717,
-0.01252... | 0.074192 |
format `/`. For backwards compatibility, if the namespace of the ApplicationSet is the control plane's namespace (i.e. `argocd`), the `` can be omitted from the applicationset name when referring to it. For example, the application names `argocd/someappset` and `someappset` are semantically the same and refer to the sa... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Appset-Any-Namespace.md | master | argo-cd | [
-0.06615135818719864,
-0.09036892652511597,
-0.15315133333206177,
-0.03779583424329758,
-0.03736421465873718,
-0.03588682413101196,
0.07795414328575134,
0.04444415494799614,
-0.021867413073778152,
-0.01695472188293934,
-0.02949252538383007,
0.007465264294296503,
0.05669579654932022,
0.0297... | 0.136162 |
# Post Selector all generators The `selector` field on a generator allows an `ApplicationSet` to post-filter results using [the Kubernetes common labelSelector format](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors) and the generated values. `matchLabels` is a map of `{key,val... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Post-Selector.md | master | argo-cd | [
-0.023359937593340874,
0.09605925530195236,
-0.016336524859070778,
-0.019112827256321907,
0.02492491900920868,
0.030356114730238914,
0.06618086993694305,
-0.06357990950345993,
0.052394747734069824,
-0.025189004838466644,
-0.008054036647081375,
-0.13772635161876678,
0.021085981279611588,
-0... | 0.125978 |
# List Generator The List generator generates parameters based on an arbitrary list of key/value pairs (as long as the values are string values). In this example, we're targeting a local cluster named `engineering-dev`: ```yaml apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: guestbook namespace: a... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-List.md | master | argo-cd | [
-0.0032043445389717817,
0.07424604147672653,
-0.054906927049160004,
0.04350849241018295,
0.03360559418797493,
0.013696499168872833,
0.024418814107775688,
-0.029346639290452003,
0.01627887785434723,
0.04838896170258522,
-0.0026170231867581606,
-0.10091447830200195,
-0.011863747611641884,
-0... | 0.087765 |
# Cluster Generator In Argo CD, managed clusters [are stored within Secrets](../../declarative-setup/#clusters) in the Argo CD namespace. The ApplicationSet controller uses those same Secrets to generate parameters to identify and target available clusters. For each cluster registered with Argo CD, the Cluster generato... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Cluster.md | master | argo-cd | [
-0.005205658730119467,
-0.0014232867397367954,
-0.09575824439525604,
0.05988648906350136,
0.012029440142214298,
0.007270677015185356,
0.06837637722492218,
-0.05507931858301163,
0.009164847433567047,
0.04903383553028107,
0.011774180456995964,
-0.10648685693740845,
0.018245995044708252,
-0.0... | 0.191915 |
cluster # The cluster generator also supports matchExpressions. #matchExpressions: # - key: staging # operator: In # values: # - "true" ``` This selector will not match the default local cluster, since the default local cluster does not have a Secret (and thus does not have the `argocd.argoproj.io/secret-type` label on... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Cluster.md | master | argo-cd | [
-0.016411105170845985,
0.018954990431666374,
-0.07704945653676987,
0.060181863605976105,
0.04738790541887283,
0.01408157404512167,
0.0550730936229229,
-0.11903629451990128,
-0.024784795939922333,
0.0014625234762206674,
0.025551360100507736,
-0.10371425747871399,
0.00077859777957201,
-0.034... | 0.140975 |
`name` - `nameNormalized` \*('name' but normalized to contain only lowercase alphanumeric characters, '-' or '.')\* - `server` - `metadata.labels.` \*(for each label in the Secret)\* - `metadata.annotations.` \*(for each annotation in the Secret)\* Extending the example above, we could do something like this: ```yaml s... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Cluster.md | master | argo-cd | [
0.0028807290364056826,
0.11967901140451431,
0.0029690784867852926,
0.05927123874425888,
0.0446990467607975,
0.032977912575006485,
0.02311990223824978,
-0.0350063219666481,
0.007792471442371607,
0.007804987020790577,
0.004683998879045248,
-0.10966142266988754,
-0.0007202955894172192,
-0.006... | 0.085212 |
# Pull Request Generator The Pull Request generator uses the API of an SCMaaS provider (GitHub, Gitea, or Bitbucket Server) to automatically discover open pull requests within a repository. This fits well with the style of building a test environment when you create a pull request. ```yaml apiVersion: argoproj.io/v1alp... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Pull-Request.md | master | argo-cd | [
-0.10188882052898407,
-0.03010883368551731,
-0.08352045714855194,
0.012940103188157082,
0.0295048039406538,
-0.051332298666238785,
-0.016216540709137917,
0.01885031908750534,
0.028068484738469124,
0.07230594009160995,
-0.0023025223053991795,
-0.032133396714925766,
-0.014815034344792366,
-0... | 0.143419 |
want to target. (Optional) \* `pullRequestState`: PullRequestState is an additional MRs filter to get only those with a certain state. By default all states. Default: "" (all states). Valid values: `""`, `opened`, `closed`, `merged` or `locked`. (Optional) \* `insecure`: By default (false) - Skip checking the validity ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Pull-Request.md | master | argo-cd | [
-0.08588964492082596,
-0.005092067178338766,
-0.11300382763147354,
0.019744843244552612,
-0.023602528497576714,
-0.08566481620073318,
0.047669667750597,
-0.0034363046288490295,
-0.009685549885034561,
0.008942141197621822,
-0.01759936846792698,
-0.05422345548868179,
0.11995475739240646,
0.0... | -0.043338 |
the only auth supported currently): \* `username`: The username to authenticate with. It only needs read access to the relevant repo. \* `passwordRef`: A `Secret` name and key containing the password or personal access token to use for requests. In case of Bitbucket App Token, go with `bearerToken` section. \* `tokenRe... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Pull-Request.md | master | argo-cd | [
-0.08747594803571701,
-0.028055420145392418,
-0.09025373309850693,
0.011268671602010727,
0.012411915697157383,
-0.01970321126282215,
0.056569699198007584,
0.021194107830524445,
-0.010321768932044506,
0.08032836765050888,
0.018305713310837746,
-0.051103685051202774,
0.07547152042388916,
-0.... | 0.011989 |
key containing the app token to use for requests. ## Azure DevOps Specify the organization, project and repository from which you want to fetch pull requests. ```yaml apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: myapps spec: goTemplate: true goTemplateOptions: ["missingkey=error"] generators: -... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Pull-Request.md | master | argo-cd | [
-0.03996103256940842,
0.00019473068823572248,
-0.04932534694671631,
0.00966055877506733,
0.013593015260994434,
-0.02504596672952175,
0.07085441797971725,
-0.02945500798523426,
0.059797026216983795,
0.1090763732790947,
-0.012141138315200806,
-0.09520187228918076,
0.02104276604950428,
-0.011... | 0.083148 |
\* `target\_branch`: The name of the target branch of the pull request. \* `target\_branch\_slug`: The target branch name will be cleaned to be conform to the DNS label standard as defined in [RFC 1123](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names), and truncated to 50 charac... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Pull-Request.md | master | argo-cd | [
-0.03767469525337219,
0.014700579456984997,
0.05487664043903351,
-0.07498800754547119,
-0.08848802745342255,
0.021776698529720306,
0.014931985177099705,
0.02864878624677658,
0.1390044391155243,
-0.009987671859562397,
0.001005789847113192,
-0.0575949102640152,
-0.045518383383750916,
-0.0271... | 0.159166 |
targetRevision: '{{ .branch }}' path: kubernetes/ project: default destination: server: https://kubernetes.default.svc namespace: default ``` > [!NOTE] > The `values.` prefix is always prepended to values provided via `generators.pullRequest.values` field. Ensure you include this prefix in the parameter name within the... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Pull-Request.md | master | argo-cd | [
0.03186437860131264,
0.025240181013941765,
0.010016950778663158,
0.019466210156679153,
-0.04389240965247154,
0.01804245449602604,
-0.020015748217701912,
0.026203710585832596,
0.08708230406045914,
0.04082553833723068,
-0.0728759616613388,
-0.08088485896587372,
-0.056742243468761444,
-0.0320... | 0.03358 |
# Controlling if/when the ApplicationSet controller modifies `Application` resources The ApplicationSet controller supports a number of settings that limit the ability of the controller to make changes to generated Applications, for example, preventing the controller from deleting child Applications. These settings all... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Controlling-Resource-Modification.md | master | argo-cd | [
-0.033990416675806046,
-0.02330886386334896,
-0.07448983192443848,
0.011085890233516693,
0.0331110842525959,
-0.046208444982767105,
0.07865934818983078,
0.010369853116571903,
0.04288892075419426,
0.035527829080820084,
0.003358330111950636,
0.018469715490937233,
0.021546291187405586,
-0.068... | 0.085635 |
are deleted according to ownerReferences to ApplicationSet. See [How to prevent Application controller from deleting Applications when deleting ApplicationSet](#how-to-prevent-application-controller-from-deleting-applications-when-deleting-applicationset) ``` --policy create-update ``` This may be useful to users looki... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Controlling-Resource-Modification.md | master | argo-cd | [
-0.06771614402532578,
-0.06837432831525803,
-0.08779670298099518,
-0.06731461733579636,
0.05764690414071083,
-0.037472497671842575,
0.07834960520267487,
-0.0710635557770729,
0.04111415520310402,
0.06110064312815666,
0.061136532574892044,
0.050684940069913864,
0.008353622630238533,
-0.03741... | 0.05247 |
[Future improvements](https://github.com/argoproj/argo-cd/issues/15975) to the ApplicationSet controller may > eliminate this problem. For example, the `ref` field might be made a merge key, allowing the ApplicationSet > controller to generate and use a StrategicMergePatch instead of a MergePatch. You could then target... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Controlling-Resource-Modification.md | master | argo-cd | [
-0.10457885265350342,
-0.005532677285373211,
-0.05091223493218422,
0.01191791333258152,
0.02678816393017769,
-0.04479477182030678,
0.08611354231834412,
-0.05781572312116623,
0.019570806995034218,
0.09314052015542984,
0.005135831423103809,
0.06484535336494446,
-0.005681514739990234,
-0.0608... | 0.073686 |
annotations and labels > [!NOTE] > The same behavior can be achieved on a per-app basis using the [`ignoreApplicationDifferences`](#ignore-certain-changes-to-applications) > feature described above. However, preserved fields may be configured globally, a feature that is not yet available > for `ignoreApplicationDiffere... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Controlling-Resource-Modification.md | master | argo-cd | [
-0.01990622654557228,
0.056314144283533096,
0.01938346028327942,
-0.023572007194161415,
0.04339860379695892,
0.03161955624818802,
0.10828247666358948,
-0.06120413541793823,
0.1327713429927826,
-0.012235350906848907,
-0.020761078223586082,
-0.06231650337576866,
-0.023915143683552742,
-0.022... | 0.164221 |
# Getting Started This guide assumes you are familiar with Argo CD and its basic concepts. See the [Argo CD documentation](../../core\_concepts.md) for more information. ## Requirements \* Installed [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) command-line tool \* Have a [kubeconfig](https://kuber... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Getting-Started.md | master | argo-cd | [
0.00895517785102129,
-0.058069076389074326,
-0.08675704896450043,
-0.029773376882076263,
-0.053573135286569595,
0.014034758321940899,
0.041864652186632156,
0.049962591379880905,
0.000736743095330894,
0.07098212093114853,
-0.01796884462237358,
-0.060553137212991714,
-0.02646128460764885,
-0... | 0.195383 |
# Go Template ## Introduction ApplicationSet is able to use [Go Text Template](https://pkg.go.dev/text/template). To activate this feature, add `goTemplate: true` to your ApplicationSet manifest. The [Sprig function library](https://masterminds.github.io/sprig/) (except for `env`, `expandenv` and `getHostByName`) is av... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/GoTemplate.md | master | argo-cd | [
-0.04207797348499298,
0.0425143837928772,
0.004370590206235647,
-0.09797023236751556,
-0.10904380679130554,
-0.021313628181815147,
0.020383328199386597,
0.09231411665678024,
-0.01001017913222313,
-0.050406888127326965,
0.01549032423645258,
0.0167554784566164,
-0.04098238795995712,
0.041934... | 0.085303 |
activating Go Templating, `{{ .path }}` becomes an object. Therefore, some changes must be made to the Git generators' templating: - `{{ path }}` becomes `{{ .path.path }}` - `{{ path.basename }}` becomes `{{ .path.basename }}` - `{{ path.basenameNormalized }}` becomes `{{ .path.basenameNormalized }}` - `{{ path.filena... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/GoTemplate.md | master | argo-cd | [
-0.02180703729391098,
0.061693381518125534,
-0.010746295563876629,
0.06425829976797104,
-0.021158650517463684,
-0.040336497128009796,
0.02721276320517063,
0.029062649235129356,
0.03369220346212387,
0.003995520528405905,
0.022715887054800987,
-0.014341422356665134,
-0.05819064378738403,
0.0... | 0.075656 |
prefer to have unset parameters default to zero, you can remove `goTemplateOptions: ["missingkey=error"]` or set it to `goTemplateOptions: ["missingkey=invalid"]` | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/GoTemplate.md | master | argo-cd | [
-0.011184650473296642,
0.04816160351037979,
-0.025213677436113358,
0.0514867939054966,
-0.05730829015374184,
0.05586826801300049,
-0.01742987148463726,
0.021814486011862755,
0.0005378185887821019,
0.006246526259928942,
0.07451359182596207,
-0.10324858874082565,
0.02378726564347744,
-0.0602... | -0.097431 |
# Merge Generator The Merge generator combines parameters produced by the base (first) generator with matching parameter sets produced by subsequent generators. A \_matching\_ parameter set has the same values for the configured \_merge keys\_. \_Non-matching\_ parameter sets are discarded. Override precedence is botto... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Merge.md | master | argo-cd | [
-0.07424617558717728,
-0.008829346857964993,
-0.010278210043907166,
-0.0007766195340082049,
-0.011937079951167107,
-0.045442551374435425,
0.007571419235318899,
-0.03257044777274132,
-0.05191927030682564,
-0.009209469892084599,
0.04154656454920769,
-0.060527123510837555,
0.03652486577630043,
... | 0.070514 |
as a selector. - git: repoURL: https://github.com/argoproj/argocd-example-apps/ revision: HEAD directories: - path: '\*' values: selector: '{{.path.path}}' template: metadata: name: '{{.name}}' spec: project: '{{index .metadata.labels "environment"}}' source: repoURL: https://github.com/argoproj/argocd-example-apps/ # ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Merge.md | master | argo-cd | [
-0.0016753224190324545,
0.03907504305243492,
-0.045679427683353424,
0.07621932774782181,
0.020689059048891068,
-0.0038728131912648678,
0.09429174661636353,
-0.025983095169067383,
0.030233580619096756,
0.01079554669559002,
0.022167647257447243,
-0.06804629415273666,
-0.004620684310793877,
-... | 0.102228 |
# Matrix Generator The Matrix generator combines the parameters generated by two child generators, iterating through every combination of each generator's generated parameters. By combining both generators parameters, to produce every possible combination, this allows you to gain the intrinsic properties of both genera... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Matrix.md | master | argo-cd | [
-0.049946170300245285,
-0.01890271157026291,
-0.16619662940502167,
0.03854711726307869,
0.03487468138337135,
0.015371005050837994,
-0.005488249938935041,
-0.04987567290663719,
-0.05517726019024849,
-0.0005238630692474544,
0.03183966502547264,
-0.055867522954940796,
0.09953051060438156,
-0.... | 0.158566 |
cluster-git spec: goTemplate: true goTemplateOptions: ["missingkey=error"] generators: # matrix 'parent' generator - matrix: generators: # git generator, 'child' #1 - git: repoURL: https://github.com/argoproj/applicationset.git revision: HEAD files: - path: "examples/git-generator-files-discovery/cluster-config/\*\*/co... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Matrix.md | master | argo-cd | [
0.01229919958859682,
0.017793672159314156,
-0.10579270124435425,
0.053832363337278366,
0.037770334631204605,
0.03243933245539665,
-0.0029387108515948057,
-0.03952426835894585,
0.03602694347500801,
0.060347072780132294,
0.05584624409675598,
-0.10014869272708893,
-0.013198081403970718,
-0.07... | 0.096928 |
git file generator referencing files containing details about # locations to which each app should deploy (e.g., `region` and # `clusterName`). - git: repoURL: https://github.com/some-org/some-repo.git revision: HEAD files: - path: "targets/{{.appName}}/\*.json" pathParamPrefix: target template: {} # ... ``` Then, give... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Matrix.md | master | argo-cd | [
-0.014299435541033745,
0.027780404314398766,
0.047051411122083664,
0.006991259753704071,
0.040861859917640686,
-0.012205015867948532,
0.01277537364512682,
0.021735182031989098,
0.03564486652612686,
0.0024007910396903753,
0.03336246684193611,
-0.03319151699542999,
0.03988853469491005,
0.014... | 0.032315 |
# Introduction to ApplicationSet controller ## Introduction The ApplicationSet controller is a [Kubernetes controller](https://kubernetes.io/docs/concepts/architecture/controller/) that adds support for an `ApplicationSet` [CustomResourceDefinition](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/cu... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/index.md | master | argo-cd | [
-0.08782792091369629,
-0.03910020366311073,
-0.035192493349313736,
-0.04856622591614723,
-0.046458855271339417,
-0.03092721477150917,
0.07357524335384369,
0.0930878221988678,
0.07679266482591629,
0.10205764323472977,
-0.014926317147910595,
-0.009763897396624088,
-0.008748240768909454,
-0.0... | 0.239562 |
generators combines the generated parameters of two other generators. See the [generator section](Generators.md) for more information about individual generators, and the other generators not listed above. ## Parameter substitution into templates Independent of which generator is used, parameters generated by a generat... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/index.md | master | argo-cd | [
-0.042352043092250824,
0.0585491843521595,
-0.05337049812078476,
0.04012784734368324,
0.02428283914923668,
0.026303810998797417,
0.011091574095189571,
-0.05142640322446823,
0.08817195147275925,
-0.008094608783721924,
-0.015138382092118263,
-0.0722975954413414,
0.03822076693177223,
-0.17432... | 0.17684 |
# SCM Provider Generator The SCM Provider generator uses the API of an SCMaaS provider (eg GitHub) to automatically discover repositories within an organization. This fits well with GitOps layout patterns that split microservices across many repositories. ```yaml apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet me... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
-0.07101329416036606,
-0.08162882179021835,
-0.1081293523311615,
-0.022728463634848595,
0.025207646191120148,
0.02336820960044861,
-0.020915064960718155,
-0.032138630747795105,
-0.04553208500146866,
0.06311208754777908,
0.025581683963537216,
-0.028547009453177452,
0.04532578960061073,
-0.0... | 0.12694 |
tokenRef: secretName: gitlab-token key: token # If true, skips validating the SCM provider's TLS certificate - useful for self-signed certificates. insecure: false # Reference to a ConfigMap containing trusted CA certs - useful for self-signed certificates. (optional) caRef: configMapName: argocd-tls-certs-cm key: gitl... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
-0.05504852905869484,
-0.009207374416291714,
-0.08820825070142746,
0.041514378041028976,
0.020814353600144386,
-0.07977098226547241,
0.033784836530685425,
-0.042339716106653214,
0.013209122233092785,
0.001527245156466961,
0.027082160115242004,
-0.07882991433143616,
0.12264811992645264,
-0.... | 0.020484 |
is true, every branch of every repository will be passed to the filters. If using this flag, you likely want to use a `branchMatch` filter. \* `tokenRef`: A `Secret` name and key containing the Gitea access token to use for requests. If not specified, will make anonymous requests which have a lower rate limit and can o... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
-0.03432527184486389,
-0.033484671264886856,
-0.07520025223493576,
0.0045767235569655895,
0.03045867383480072,
-0.026861360296607018,
0.07042977213859558,
-0.05301988124847412,
0.02363140881061554,
0.02770264260470867,
-0.008060420863330364,
-0.024043794721364975,
0.0785912573337555,
0.000... | 0.017062 |
field `azureDevOps.api`. ```yaml apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: myapps spec: generators: - scmProvider: azureDevOps: # The Azure DevOps organization. organization: myorg # URL to Azure DevOps. Optional. Defaults to https://dev.azure.com. api: https://dev.azure.com # If true, scan ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
0.008596467785537243,
-0.02190914750099182,
-0.02747703343629837,
0.017512556165456772,
0.07144314050674438,
-0.027336519211530685,
0.006444939412176609,
-0.10879945009946823,
0.05737246945500374,
0.11594521999359131,
0.006765691097825766,
-0.04582521691918373,
-0.002626307774335146,
0.027... | 0.069261 |
repositories. Default `false`. \* `tagFilters`: (Optional) A list of tagFilters to filter AWS CodeCommit repos with. See [AWS ResourceGroupsTagging API](https://docs.aws.amazon.com/resourcegroupstagging/latest/APIReference/API\_GetResources.html#resourcegrouptagging-GetResources-request-TagFilters) for details. By defa... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
-0.0439787358045578,
0.016188694164156914,
-0.08806402236223221,
-0.02241024747490883,
0.09727643430233002,
0.04226115345954895,
0.04606302082538605,
-0.08888033032417297,
0.01019236259162426,
0.030052248388528824,
0.036495812237262726,
-0.09102533757686615,
0.04652456194162369,
-0.0128159... | 0.05775 |
The id of the repository. \* `url`: The clone URL for the repository. \* `branch`: The default branch of the repository. \* `sha`: The Git commit SHA for the branch. \* `short\_sha`: The abbreviated Git commit SHA for the branch (8 chars or the length of the `sha` if it's shorter). \* `short\_sha\_7`: The abbreviated G... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
-0.03417230024933815,
-0.036491215229034424,
-0.034208349883556366,
0.020135289058089256,
0.002212745137512684,
0.010626459494233131,
0.03998458385467529,
-0.006440000142902136,
0.09461383521556854,
0.031030138954520226,
0.035333212465047836,
0.031240100041031837,
0.10191450268030167,
-0.0... | 0.077055 |
# Application Pruning & Resource Deletion All `Application` resources created by the ApplicationSet controller (from an ApplicationSet) will contain: - A `.metadata.ownerReferences` reference back to the \*parent\* `ApplicationSet` resource - An Argo CD `resources-finalizer.argocd.argoproj.io` finalizer in `.metadata.f... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Application-Deletion.md | master | argo-cd | [
-0.07030303031206131,
0.008428286761045456,
-0.0750289335846901,
-0.0220768004655838,
0.0517067015171051,
-0.07836759090423584,
0.1231057196855545,
-0.06065104901790619,
0.021340589970350266,
0.05316118523478508,
0.0625622421503067,
0.05903259292244911,
0.05385835841298103,
-0.043645780533... | 0.143462 |
# Git File Generator Globbing ## Problem Statement The original and default implementation of the Git file generator does very greedy globbing. This can trigger errors or catch users off-guard. For example, consider the following repository layout: ``` └── cluster-charts/ ├── cluster1 │ ├── mychart/ │ │ ├── charts/ │ │... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Generators-Git-File-Globbing.md | master | argo-cd | [
-0.013026461005210876,
-0.00566431088373065,
0.002551383338868618,
0.021224623546004295,
0.006658563856035471,
-0.04313261806964874,
0.05278879031538963,
0.08148223906755447,
0.014923878014087677,
-0.034733593463897705,
0.052725210785865784,
-0.029915736988186836,
0.0917566642165184,
-0.00... | 0.061697 |
# Progressive Syncs > [!WARNING] > \*\*Beta Feature (Since v2.6.0)\*\* > This feature is in the [Beta](https://github.com/argoproj/argoproj/blob/main/community/feature-status.md#beta) stage. It is generally considered stable, but there may be unhandled edge cases. This feature allows you to control the order in which t... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Progressive-Syncs.md | master | argo-cd | [
-0.0545797124505043,
-0.06925569474697113,
-0.08042536675930023,
0.018678933382034302,
-0.006985804066061974,
-0.02072938345372677,
0.02596275508403778,
-0.054675012826919556,
-0.06798440217971802,
0.08827226608991623,
0.005633339285850525,
0.12450262904167175,
-0.012644506059587002,
-0.04... | 0.150398 |
`operation` status field on the Application resource). This means that a RollingSync will respect sync windows just as if a user had clicked the "Sync" button in the Argo UI. - When a sync is triggered, the sync is performed with the same syncPolicy configured for the Application. For example, this preserves the Applic... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Progressive-Syncs.md | master | argo-cd | [
-0.10612506419420242,
-0.022018147632479668,
-0.12214162945747375,
-0.017848776653409004,
-0.04052523151040077,
-0.05470653250813484,
0.009213726036250591,
-0.06431092321872711,
-0.0020825155079364777,
0.03954028710722923,
0.04067547619342804,
0.07682056725025177,
-0.007221602369099855,
-0... | 0.124286 |
services in the correct sequence, such as deleting frontend services before backend dependencies. ### Example The following example illustrates how to stage a progressive sync over Applications with explicitly configured environment labels. Once a change is pushed, the following will happen in order. - All `env-dev` Ap... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Progressive-Syncs.md | master | argo-cd | [
-0.015446417033672333,
-0.027886047959327698,
-0.058610573410987854,
-0.08816494792699814,
0.040202438831329346,
-0.036528244614601135,
-0.028313903138041496,
-0.10725059360265732,
0.04641740769147873,
0.046606920659542084,
0.04885019734501839,
0.04734569787979126,
-0.03237302601337433,
-0... | 0.081647 |
# Use cases supported by the ApplicationSet controller With the concept of generators, the ApplicationSet controller provides a powerful set of tools to automate the templating and modification of Argo CD Applications. Generators produce template parameter data from a variety of sources, including Argo CD clusters and ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Use-Cases.md | master | argo-cd | [
-0.06164911761879921,
-0.022149676457047462,
-0.0654321163892746,
0.014856046065688133,
-0.01026726234704256,
-0.019714338704943657,
0.04908476024866104,
0.03955807909369469,
0.04377905651926994,
0.06437338888645172,
0.004969783592969179,
-0.024427475407719612,
0.011224385350942612,
-0.056... | 0.277696 |
file within a Git repository. Updates to the JSON file, through Git commits, cause new clusters to be added/removed. - Using the Git generator `directories` field: For each target cluster, a corresponding directory of that name exists in a Git repository. Adding/modifying a directory, through Git commits, would trigger... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Use-Cases.md | master | argo-cd | [
-0.08033991605043411,
-0.05678674206137657,
0.061067644506692886,
0.017113864421844482,
-0.007699671667069197,
-0.04857802018523216,
-0.013023857027292252,
0.011617790907621384,
0.14351080358028412,
0.047932542860507965,
0.05936775356531143,
-0.018140718340873718,
0.0150621198117733,
-0.02... | 0.232115 |
"applicationset/examples/git-generator-files-discovery/apps/guestbook" } (...) } ``` ```yaml kind: ApplicationSet # (...) spec: goTemplate: true goTemplateOptions: ["missingkey=error"] generators: - git: repoURL: https://github.com/argoproj/argo-cd.git files: - path: "apps/\*\*/config.json" template: spec: project: dev... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/applicationset/Use-Cases.md | master | argo-cd | [
-0.04621213674545288,
0.034278880804777145,
-0.07911688834428787,
0.0002127318293787539,
0.030516959726810455,
-0.02462954819202423,
0.0344933420419693,
0.013447433710098267,
-0.016208156943321228,
0.07189010828733444,
0.028012750670313835,
-0.037473466247320175,
-0.012597320601344109,
-0.... | 0.088216 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.