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 |
|---|---|---|---|---|---|
# 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.01168703380972147,
-0.06559596210718155,
-0.07453007996082306,
-0.006960208062082529,
-0.043322160840034485,
-0.03601624816656113,
0.02155623584985733,
0.01961185224354267,
0.07124621421098709,
0.08264283835887909,
0.011037780903279781,
-0.006642814259976149,
-0.03288193792104721,
-0.01... | 0.131981 |
# 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 types 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 en... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/installation.md | master | argo-cd | [
0.0204473827034235,
-0.05261184275150299,
-0.06439889967441559,
-0.04896094650030136,
-0.03871480002999306,
-0.07261118292808533,
0.04253386706113815,
0.007985701784491539,
0.001619100570678711,
0.07303481549024582,
0.04270476475358009,
0.030314244329929352,
-0.06185061112046242,
-0.011260... | 0.193755 |
recommended to 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... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/installation.md | master | argo-cd | [
-0.012833965942263603,
-0.012392104603350163,
-0.016170844435691833,
-0.07470478117465973,
-0.07263528555631638,
-0.038984015583992004,
0.061334408819675446,
-0.004554991144686937,
-0.038998816162347794,
0.0959266871213913,
0.0025436861906200647,
0.027101857587695122,
-0.06104632094502449,
... | 0.172841 |
# Ingress Configuration Argo CD API server runs both a gRPC server (used by the CLI), as well as an 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 to configure Ingress... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md | master | argo-cd | [
-0.02611716464161873,
0.04354009032249451,
-0.049928802996873856,
-0.04005665332078934,
-0.07521723955869675,
-0.08926315605640411,
0.009626639075577259,
-0.057965800166130066,
0.06664477288722992,
0.08102824538946152,
0.0021507719065994024,
-0.04439879208803177,
-0.016740847378969193,
0.0... | 0.169997 |
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 |
a single protocol per Ingress object, two Ingress objects need to be defined using the `nginx.ingress.kubernetes.io/backend-protocol` annotation, one for HTTP/HTTPS and the other for gRPC. Each ingress will be for a different domain (`argocd.example.com` and `grpc.argocd.example.com`). This requires that the Ingress re... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md | master | argo-cd | [
-0.051395777612924576,
0.025942431762814522,
-0.018304498866200447,
-0.02452324703335762,
-0.05576983839273453,
-0.08294226229190826,
0.0601193904876709,
-0.08388616144657135,
0.12829941511154175,
0.04132333770394325,
-0.03858581930398941,
-0.08300584554672241,
-0.011090051382780075,
0.048... | 0.108782 |
as L4 Load Balancers for both. When using an ALB, you'll want to create a second service for argocd-server. This is necessary because we need to tell the ALB to send the GRPC traffic to a different target group than the UI traffic, since the backend protocol is HTTP2 instead of HTTP1. ```yaml apiVersion: v1 kind: Servi... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md | master | argo-cd | [
-0.004613801371306181,
0.02564891427755356,
-0.055921100080013275,
-0.017632469534873962,
-0.03984178230166435,
-0.04990416765213013,
0.04094548150897026,
-0.0755368024110794,
0.05893487110733986,
0.07112669199705124,
-0.03373590111732483,
-0.061354923993349075,
-0.036192454397678375,
-0.0... | 0.107462 |
we create Istio Resources ```yaml apiVersion: networking.istio.io/v1alpha3 kind: Gateway metadata: name: argocd-gateway namespace: argocd spec: selector: istio: ingressgateway servers: - port: number: 80 name: http protocol: HTTP hosts: - "\*" tls: httpsRedirect: true - port: number: 443 name: https protocol: HTTPS hos... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md | master | argo-cd | [
-0.03988608717918396,
0.05739778280258179,
-0.08653544634580612,
-0.007677673362195492,
0.0015364033170044422,
-0.10241641849279404,
0.0322236642241478,
-0.035573314875364304,
0.07557890564203262,
0.012434595264494419,
-0.014282595366239548,
-0.10188373178243637,
-0.039929136633872986,
0.0... | 0.453254 |
And finally, to top it all, our Ingress. Note the reference to our frontend config, the service, and to the certificate secret. --- > [!NOTE] > GKE clusters running versions earlier than `1.21.3-gke.1600`, [the only supported value for the pathType field](https://cloud.google.com/kubernetes-engine/docs/how-to/load-bala... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md | master | argo-cd | [
-0.03968246653676033,
0.03613967075943947,
0.062485527247190475,
0.008771475404500961,
-0.007205303758382797,
-0.03603589907288551,
0.013235442340373993,
-0.026307540014386177,
0.05449908971786499,
0.05821125954389572,
-0.03470562398433685,
-0.1020902544260025,
0.03426008298993111,
-0.0262... | 0.092031 |
--basehref - /argo-cd ``` NOTE: The flag `--basehref` only changes the UI base URL. The API server will keep using the `/` path so you need to add a URL rewrite rule to the proxy config. Example nginx.conf with URL rewrite: ``` worker\_processes 1; events { worker\_connections 1024; } http { sendfile on; server { liste... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md | master | argo-cd | [
-0.06042025610804558,
0.05950753018260002,
-0.02512819878757,
-0.007405908312648535,
-0.07619895786046982,
-0.07562445849180222,
-0.0342487171292305,
-0.021541371941566467,
-0.031176192685961723,
0.08147745579481125,
-0.06910432875156403,
-0.021588586270809174,
-0.08562812209129333,
-0.011... | 0.078421 |
gateway, which is part of the [Experimental](https://gateway-api.sigs.k8s.io/reference/1.4/specx/) Gateway API CRDs. ```yaml kind: Gateway metadata: name: cluster-gateway namespace: gateway spec: gatewayClassName: example listeners: - name: tls port: 443 protocol: TLS hostname: "argocd.example.com" allowedRoutes: names... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/ingress.md | master | argo-cd | [
-0.04557475447654724,
-0.002391774905845523,
-0.0830053761601448,
0.02918081358075142,
-0.026392169296741486,
-0.06072361394762993,
0.027252739295363426,
-0.05247993767261505,
0.08569438010454178,
0.02275526337325573,
-0.00039594146073795855,
0.011925802566111088,
-0.014192535541951656,
-0... | 0.143346 |
# 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 |
is present in the `status` sub-resource, please use this field in the health check. Using this field in calculating the CRD health is important for preventing situations in which the health status in Argo CD may flap if Argo CD is evaluating the health status before the CRD controller finished reconciling the changed C... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/health.md | master | argo-cd | [
-0.04504859820008278,
0.0562962107360363,
-0.10211292654275894,
0.012892981991171837,
-0.017965011298656464,
-0.07779166102409363,
0.1189127266407013,
-0.012603415176272392,
-0.04187816381454468,
0.08913633227348328,
0.045364342629909515,
0.02506677433848381,
-0.02551397681236267,
-0.02452... | 0.166031 |
check must have tests defined in `health\_test.yaml` file. The `health\_test.yaml` is a YAML file with the following structure: ```yaml tests: - healthStatus: status: ExpectedStatus message: Expected message inputPath: testdata/test-resource-definition.yaml ``` For the files you add in `testdata` folder - please make s... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/health.md | master | argo-cd | [
0.024312570691108704,
0.036964889615774155,
-0.06050503998994827,
0.02872999757528305,
0.030811402946710587,
-0.08844240754842758,
0.03535947576165199,
-0.02301335148513317,
0.006896286271512508,
0.057825494557619095,
0.06300432235002518,
-0.060261063277721405,
-0.0434420108795166,
-0.0350... | 0.130613 |
Missing resource and a Degraded resource, the App's health will be \*\*Degraded\*\*. But the health of a resource is not inherited from child resources - it is calculated using only information about the resource itself. A resource's status field may or may not contain information about the health of a child resource, ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/health.md | master | argo-cd | [
-0.031078524887561798,
0.0763687789440155,
0.038688212633132935,
0.029056420549750328,
0.0632944256067276,
-0.03946434333920479,
0.03283672779798508,
-0.001648254576139152,
0.023120148107409477,
0.06079208850860596,
0.07138165831565857,
-0.013106504455208778,
0.07677391171455383,
0.0045464... | 0.129737 |
# 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 ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/security.md | master | argo-cd | [
-0.020811954513192177,
-0.0016688384348526597,
-0.06919856369495392,
0.07023416459560394,
-0.002958310302346945,
-0.013189392164349556,
0.09136450290679932,
-0.025907406583428383,
0.05435333400964737,
0.11318102478981018,
0.025351187214255333,
0.03121352754533291,
0.019456177949905396,
-0.... | 0.2121 |
| Level | Friendly Level | Description | Example | |-------|----------------|---------------------------------------------------------------------------------------------------|---------------------------------------------| | 1 | Low | Unexceptional, non-malicious events | Successful access | | 2 | Medium | Could indic... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/security.md | master | argo-cd | [
-0.02755771018564701,
-0.02073705568909645,
-0.041790325194597244,
-0.013341066427528858,
0.043643705546855927,
-0.05524060130119324,
0.048554375767707825,
0.03453397378325462,
-0.018054930493235588,
0.010371173731982708,
0.0789695531129837,
0.014242424629628658,
0.11212378740310669,
-0.00... | 0.109353 |
# 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 |
name: cluster-addons 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-gen... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Git.md | master | argo-cd | [
0.007067399565130472,
0.026552166789770126,
-0.05902126058936119,
0.05400681868195534,
0.04771435633301735,
0.007563543040305376,
0.028079437091946602,
-0.046277835965156555,
0.052175555378198624,
0.04715924710035324,
0.06281226128339767,
-0.07594920694828033,
-0.04470818117260933,
-0.0792... | 0.116913 |
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-generator-fil... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Git.md | master | argo-cd | [
-0.00047626550076529384,
0.01672629825770855,
-0.0406905896961689,
0.0297874603420496,
0.08034536242485046,
-0.04130314290523529,
0.02100961096584797,
-0.027091624215245247,
0.0966295599937439,
0.03685817867517471,
0.07898759841918945,
-0.050523173063993454,
0.03754817321896553,
-0.0544343... | 0.103756 |
see [Git File Generator 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: Applicatio... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Git.md | master | argo-cd | [
-0.019361278042197227,
0.0569857694208622,
-0.06463244557380676,
0.017710966989398003,
0.05633145198225975,
-0.042792510241270065,
0.04146667197346687,
-0.047606516629457474,
0.033612385392189026,
0.01358723547309637,
0.060518648475408554,
-0.002817467786371708,
0.008054303005337715,
-0.11... | 0.061778 |
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 should use the `/api... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Git.md | master | argo-cd | [
-0.07296454161405563,
-0.013822680339217186,
-0.07802945375442505,
0.026535438373684883,
-0.00830643530935049,
-0.04715634882450104,
0.0262688510119915,
0.019248200580477715,
0.0671001747250557,
0.034884627908468246,
0.04505693539977074,
-0.08879835903644562,
0.0624249093234539,
-0.0239895... | 0.12779 |
# 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.0238234531134367,
-0.04957316815853119,
-0.07201747596263885,
-0.016621176153421402,
-0.013238287530839443,
-0.03377191722393036,
0.11721305549144745,
-0.0429113395512104,
0.10048699378967285,
0.07596086710691452,
0.03373436629772186,
-0.018886903300881386,
0.0021030991338193417,
-0.079... | 0.182137 |
# 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 |
spec: 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/... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Plugin.md | master | argo-cd | [
0.02339073270559311,
0.031024442985653877,
-0.09096234291791916,
0.04042057320475578,
0.030991006642580032,
0.03630516678094864,
-0.05857245251536369,
0.027022043243050575,
0.0019511517602950335,
0.046416111290454865,
0.03873133286833763,
-0.07508426159620285,
0.0029951506294310093,
-0.057... | 0.003318 |
# 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 |
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.08551955968141556,
-0.06308837234973907,
-0.07666207104921341,
0.045954182744026184,
0.01769409514963627,
0.03156881034374237,
-0.04081755131483078,
-0.003278720658272505,
-0.024535024538636208,
0.034767668694257736,
0.08342573791742325,
-0.05616534873843193,
-0.000556098239030689,
-0.02... | 0.116557 |
# 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] > Please read this documentation carefully before you enable this feature. Misconfiguration could lead to potential security issues. ## Introduction As of version 2.8, Argo CD supports managing `ApplicationSet` resources in namespaces other than the control plane's namespa... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Appset-Any-Namespace.md | master | argo-cd | [
-0.026735156774520874,
-0.06463726609945297,
-0.10810340195894241,
0.00317971664480865,
-0.01680603250861168,
-0.037448443472385406,
0.12068959325551987,
0.010068478062748909,
-0.03161226212978363,
0.05308724194765091,
0.0082307243719697,
-0.033677879720926285,
0.017283029854297638,
-0.006... | 0.13078 |
`tokenRef`. When this mode is enabled, the referenced secret must have a label `argocd.argoproj.io/secret-type` with value `scm-creds`. To enable this mode, set the `ARGOCD\_APPLICATIONSET\_CONTROLLER\_TOKENREF\_STRICT\_MODE` environment variable to `true` in the `argocd-application-controller` deployment. You can do t... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Appset-Any-Namespace.md | master | argo-cd | [
-0.037991560995578766,
-0.07755948603153229,
-0.13758976757526398,
0.02365019917488098,
-0.002568959491327405,
-0.03187704086303711,
0.08165350556373596,
0.07415339350700378,
-0.07050695270299911,
0.11799158155918121,
0.04431185498833656,
-0.0583355650305748,
0.021778615191578865,
-0.01236... | 0.108005 |
to it. For example, the application names `argocd/someappset` and `someappset` are semantically the same and refer to the same application in the CLI and the UI. ### Applicationsets RBAC The RBAC syntax for Application objects has been changed from `/` to `//` to accommodate the need to restrict access based on the sou... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Appset-Any-Namespace.md | master | argo-cd | [
-0.07765594124794006,
-0.08459437638521194,
-0.1527957171201706,
-0.022569840773940086,
-0.042757462710142136,
-0.013993372209370136,
0.10407733917236328,
0.03884497284889221,
-0.020310938358306885,
0.01294032670557499,
-0.0194567684084177,
0.016565393656492233,
0.05300571769475937,
-0.004... | 0.129271 |
# ApplicationSet Web UI For end-user documentation of the UI itself, see [Managing ApplicationSets in the Web UI](../../user-guide/application-set-ui.md). The Web UI integrates with ApplicationSets through three layers: 1. \*\*The `ApplicationSetService` API\*\* exposed by the Argo CD API server (defined in [`server/ap... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Web-UI.md | master | argo-cd | [
-0.09013277292251587,
0.025018446147441864,
-0.16162924468517303,
-0.007970666512846947,
0.0077114347368478775,
-0.09626715630292892,
0.09228312969207764,
0.04969296604394913,
-0.01870541088283062,
0.04343041405081749,
-0.02092576026916504,
-0.00792981218546629,
-0.01126036886125803,
-0.06... | 0.255813 |
# 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.md#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 generator... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Cluster.md | master | argo-cd | [
-0.001683394075371325,
0.0009687033598311245,
-0.09679614007472992,
0.05632690340280533,
0.013903376646339893,
0.012809450738132,
0.06547240912914276,
-0.05963040515780449,
0.011035336181521416,
0.05288901552557945,
0.00499515188857913,
-0.10133906453847885,
0.025207044556736946,
-0.070022... | 0.185357 |
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 that secret). Any clu... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Cluster.md | master | argo-cd | [
-0.05036066845059395,
0.04294612258672714,
-0.07259486615657806,
0.07220590114593506,
0.04313080385327339,
0.012449678033590317,
0.043201036751270294,
-0.13506241142749786,
-0.021513834595680237,
-0.00829123891890049,
0.011787057854235172,
-0.11971358954906464,
0.0019331441726535559,
-0.07... | 0.115029 |
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 spec: goTemplate: true goTemplateOpti... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Cluster.md | master | argo-cd | [
0.026600239798426628,
0.1220044419169426,
0.01237744465470314,
0.054611220955848694,
0.047833219170570374,
0.05069799721240997,
0.009815523400902748,
-0.03808235004544258,
0.006283825263381004,
0.013918793760240078,
-0.0006224377430044115,
-0.10087277740240097,
-0.021116137504577637,
-0.00... | 0.068364 |
# 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 |
and 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"] generator... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Pull-Request.md | master | argo-cd | [
-0.0407988503575325,
0.005557348486036062,
-0.053885411471128464,
0.009967196732759476,
0.01653340645134449,
-0.0251559279859066,
0.07699563354253769,
-0.03519946709275246,
0.05304599180817604,
0.1081291064620018,
-0.007684899494051933,
-0.0898158848285675,
0.02809029631316662,
-0.01237914... | 0.096165 |
characters. \* `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 ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Pull-Request.md | master | argo-cd | [
-0.034084171056747437,
0.01411872822791338,
0.0606771856546402,
-0.06613200902938843,
-0.09866268187761307,
0.025613732635974884,
0.010996873490512371,
0.03355689346790314,
0.15054216980934143,
-0.010847494937479496,
0.0002787644334603101,
-0.058788497000932693,
-0.04377486929297447,
-0.02... | 0.1493 |
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 `template` when using it. In `v... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Pull-Request.md | master | argo-cd | [
-0.0003504882915876806,
0.032208990305662155,
-0.01643233746290207,
-0.00031959725311025977,
-0.09718243032693863,
0.03056451864540577,
-0.018360896036028862,
0.02510363608598709,
0.08538711816072464,
0.051453884690999985,
-0.05101926624774933,
-0.10147237032651901,
-0.07420974224805832,
-... | 0.052269 |
# 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 |
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/\*\*/config.json" # cluster generator, 'ch... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Matrix.md | master | argo-cd | [
-0.007677447982132435,
0.021407688036561012,
-0.09751173108816147,
0.03577250614762306,
0.03774135187268257,
0.043688882142305374,
0.01627432554960251,
-0.02764880284667015,
0.029866676777601242,
0.059739429503679276,
0.048272471874952316,
-0.09505126625299454,
-0.0316569060087204,
-0.0689... | 0.092439 |
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, given the following file structure/... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-Matrix.md | master | argo-cd | [
0.01897478476166725,
0.019387036561965942,
0.03159442916512489,
-0.023259753361344337,
0.04393194243311882,
-0.029226526618003845,
-0.0028186882846057415,
0.029008809477090836,
0.012104155495762825,
0.030194733291864395,
0.04912742227315903,
-0.021879753097891808,
0.017808066681027412,
0.0... | 0.035457 |
# 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 |
of every repository. If false, scan only the default branch. Defaults to false. allBranches: true # If true, recurses through subgroups. If false, it searches only in the base group. Defaults to false. includeSubgroups: true # If true and includeSubgroups is also true, include Shared Projects, which is gitlab API defau... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
-0.033596221357584,
-0.03773793205618858,
-0.03659619018435478,
0.03282378986477852,
0.0707310140132904,
-0.06030254065990448,
0.008490340784192085,
-0.06822885572910309,
0.03501132130622864,
0.013027924112975597,
0.027615845203399658,
0.01434638537466526,
0.13564231991767883,
0.0160880330... | -0.017581 |
kind: ApplicationSet metadata: name: myapps spec: generators: - scmProvider: gitea: # The Gitea owner to scan. owner: myorg # The Gitea instance url api: https://gitea.mydomain.com/ # If true, scan every branch of every repository. If false, scan only the default branch. Defaults to false. allBranches: true # Exclude r... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
0.006234121508896351,
0.014256598427891731,
-0.10459630191326141,
-0.027921006083488464,
0.027529709041118622,
-0.019504502415657043,
0.025102172046899796,
0.005721071269363165,
-0.001566064078360796,
0.0024450733326375484,
-0.010338903404772282,
-0.0219267625361681,
0.08986052870750427,
-... | 0.076798 |
requests. In case of Bitbucket App Token, go with `bearerToken` section. \* `tokenRef`: A `Secret` name and key containing the app token to use for requests. In case of self-signed BitBucket Server certificates, the following options can be useful: \* `insecure`: By default (false) - Skip checking the validity of the S... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
-0.06555648148059845,
-0.015981663018465042,
-0.06307805329561234,
0.026414502412080765,
0.010510792024433613,
-0.042471252381801605,
0.06382608413696289,
-0.045039329677820206,
0.0753764808177948,
0.12647010385990143,
0.025748897343873978,
-0.04585713893175125,
0.046056948602199554,
0.033... | 0.060933 |
us-east-1 # AWS role to assume to scan repos. # default to the environmental role from ApplicationSet controller. role: arn:aws:iam::111111111111:role/argocd-application-set-discovery # If true, scan every branch of every repository. If false, scan only the main branch. Defaults to false. allBranches: true # AWS resour... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
0.008887887001037598,
0.014029309153556824,
-0.11433076113462448,
-0.03538208454847336,
0.0699874758720398,
-0.063376784324646,
0.11116420477628708,
-0.08840777724981308,
0.01956877112388611,
0.07047317177057266,
0.021106133237481117,
-0.055229272693395615,
0.04204334691166878,
-0.00568522... | 0.069508 |
must exist. Can be a file or directory. \* `pathsDoNotExist`: An array of paths within the repository that must not exist. Can be a file or directory. \* `labelMatch`: A regexp matched against repository labels. If any label matches, the repository is included. \* `branchMatch`: A regexp matched against branch names. #... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Generators-SCM-Provider.md | master | argo-cd | [
-0.03077836148440838,
0.022877978160977364,
-0.06725811213254929,
-0.019205503165721893,
0.03406688943505287,
0.04294425621628761,
0.03149459883570671,
0.013463694602251053,
0.05707574635744095,
0.03478036820888519,
-0.002131815766915679,
-0.10546106845140457,
-0.03302774950861931,
-0.0233... | 0.137621 |
# 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.06773582100868225,
0.009024826809763908,
-0.07343929260969162,
-0.020740211009979248,
0.05222071334719658,
-0.07880973815917969,
0.12694169580936432,
-0.06357055902481079,
0.01950090005993843,
0.05084948614239693,
0.061289723962545395,
0.05601612478494644,
0.05609453469514847,
-0.044399... | 0.144496 |
# 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 v3.3.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.05536922812461853,
-0.07265356183052063,
-0.08448848128318787,
0.015332241542637348,
-0.002327396534383297,
-0.027781855314970016,
0.027824657037854195,
-0.06126561388373375,
-0.06606421619653702,
0.08891019970178604,
0.008485134690999985,
0.12139911204576492,
-0.013808202929794788,
-0.... | 0.152525 |
`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 |
# ApplicationSet Security ApplicationSet is a powerful tool, and it is crucial to understand its security implications before using it. ## Only admins may create/update/delete ApplicationSets ApplicationSets can create Applications under arbitrary [Projects](../../user-guide/projects.md). Argo CD setups often include P... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/applicationset/Security.md | master | argo-cd | [
-0.05485918000340462,
-0.013391646556556225,
-0.09587249904870987,
-0.034938301891088486,
0.0030509827192872763,
-0.06489871442317963,
0.10877437144517899,
0.017212696373462677,
0.04566609114408493,
0.046651192009449005,
-0.03202866390347481,
0.014797788113355637,
0.029273739084601402,
-0.... | 0.20066 |
# `argocd-repo-server` Command Reference ## argocd-repo-server Run ArgoCD Repository Server ### Synopsis ArgoCD Repository Server is an internal service which maintains a local cache of the Git repository holding the application manifests, and is responsible for generating and returning the Kubernetes manifests. This c... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-repo-server.md | master | argo-cd | [
-0.0008459624950774014,
-0.031130045652389526,
-0.06981215626001358,
-0.03915790468454361,
-0.03052072785794735,
-0.06300840526819229,
0.037716347724199295,
-0.04080434516072273,
0.0750967413187027,
0.098511703312397,
0.03168873488903046,
0.042906615883111954,
-0.07753463834524155,
-0.0539... | 0.190334 |
TLS connections. Use 'list' to list available ciphers. (default "TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384") --tlsmaxversion string The maximum SSL/TLS version that is acceptable (one of: 1.0|1.1|1.2|1.3) (default "1.3") --tlsminversion string The minimum SSL/TLS version that is acceptable (one of: 1.0|1.1|1.2|1.3) ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-repo-server.md | master | argo-cd | [
0.04959839582443237,
0.014079674147069454,
-0.04663408175110817,
-0.05012468621134758,
-0.049562931060791016,
0.0009913224494084716,
-0.04180256277322769,
-0.0618332177400589,
0.02288072183728218,
-0.04384324327111244,
-0.014468096196651459,
-0.052017681300640106,
0.004871169105172157,
0.0... | -0.054874 |
# `argocd-server version` Command Reference ## argocd-server version Print version information ``` argocd-server version [flags] ``` ### Options ``` -h, --help help for version --short print just the version number ``` ### Options inherited from parent commands ``` --as string Username to impersonate for the operation ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-server_version.md | master | argo-cd | [
-0.00229025655426085,
0.05497222766280174,
-0.09647124260663986,
-0.02535507269203663,
-0.02742539905011654,
-0.06120404228568077,
0.06845276802778244,
-0.05753569304943085,
0.004348995629698038,
0.004992785397917032,
0.04687980189919472,
-0.03335851430892944,
-0.00019133550813421607,
-0.0... | 0.135706 |
# `argocd-application-controller` Command Reference ## argocd-application-controller Run ArgoCD Application Controller ### Synopsis ArgoCD application controller is a Kubernetes controller that continuously monitors running applications and compares the current, live state against the desired target state (as specified... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-application-controller.md | master | argo-cd | [
-0.03903299197554588,
-0.04870746284723282,
-0.13864196836948395,
-0.03605087101459503,
-0.022499561309814453,
-0.05002279952168465,
0.05971214547753334,
0.006721094250679016,
0.04335132613778114,
0.08552824705839157,
0.021704206243157387,
0.013980439864099026,
-0.05246049165725708,
-0.090... | 0.192789 |
(e.g. argocd-redis:6379). --redis-ca-certificate string Path to Redis server CA certificate (e.g. /etc/certs/redis/ca.crt). If not specified, system trusted CAs will be used for server certificate validation. --redis-client-certificate string Path to Redis client certificate (e.g. /etc/certs/redis/client.crt). --redis-... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-application-controller.md | master | argo-cd | [
-0.07889366149902344,
0.017254436388611794,
-0.15115024149417877,
-0.0007415417931042612,
-0.04260297492146492,
-0.0950111448764801,
0.008482541888952255,
0.010223540477454662,
-0.006098111160099506,
-0.023972466588020325,
-0.026034168899059296,
-0.00919294822961092,
0.13089269399642944,
-... | 0.064359 |
# `argocd-applicationset-controller` Command Reference ## argocd-applicationset-controller Starts Argo CD ApplicationSet controller ``` argocd-applicationset-controller [flags] ``` ### Options ``` --allowed-scm-providers strings The list of allowed custom SCM provider API URLs. This restriction does not apply to SCM or... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-applicationset-controller.md | master | argo-cd | [
-0.028111623600125313,
-0.05495085194706917,
-0.12021076679229736,
-0.0356886126101017,
-0.058310847729444504,
0.0034289786126464605,
0.03831242397427559,
-0.01158947218209505,
-0.0000596496211073827,
0.10136805474758148,
0.035785309970378876,
0.003158178646117449,
-0.0005287929088808596,
... | 0.135441 |
the repo server --repo-server-timeout-seconds int Repo server RPC call timeout seconds. (default 60) --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-applicationset-controller.md | master | argo-cd | [
-0.025167381390929222,
-0.0031523637007921934,
-0.02964811399579048,
0.020198440179228783,
-0.042137570679187775,
0.0032237160485237837,
-0.0424509234726429,
-0.06142460182309151,
0.05959443375468254,
0.03670142963528633,
-0.0043076095171272755,
-0.0006934760021977127,
0.028442058712244034,
... | 0.028563 |
# `argocd-dex rundex` Command Reference ## argocd-dex rundex Runs dex generating a config using settings from the Argo CD configmap and secret ``` argocd-dex rundex [flags] ``` ### Options ``` --as string Username to impersonate for the operation --as-group stringArray Group to impersonate for the operation, this flag ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-dex_rundex.md | master | argo-cd | [
-0.05392272397875786,
0.031913094222545624,
-0.07075169682502747,
-0.0641588568687439,
-0.06426306068897247,
-0.08592963218688965,
0.09237435460090637,
-0.02505267597734928,
-0.025265617296099663,
-0.01837853156030178,
0.01832834631204605,
-0.030788807198405266,
0.04195345938205719,
-0.043... | 0.116735 |
## Additional configuration methods Additional configuration methods for configuring commands `argocd-server`, `argocd-repo-server` and `argocd-application-controller`. ### Synopsis The commands can also be configured by setting the respective flag of the available options in `argocd-cmd-params-cm.yaml`. Each component... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/additional-configuration-method.md | master | argo-cd | [
0.003926862962543964,
-0.08144218474626541,
-0.17061208188533783,
-0.042456939816474915,
-0.04173991084098816,
-0.07278516888618469,
0.052009351551532745,
0.005417447071522474,
-0.010087808594107628,
0.09518551081418991,
0.08420932292938232,
0.019003678113222122,
-0.02595713548362255,
0.01... | 0.063978 |
# `argocd-dex gendexcfg` Command Reference ## argocd-dex gendexcfg Generates a dex config from Argo CD settings ``` argocd-dex gendexcfg [flags] ``` ### Options ``` --as string Username to impersonate for the operation --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify m... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-dex_gendexcfg.md | master | argo-cd | [
-0.04840753972530365,
0.03991582989692688,
-0.06350752711296082,
-0.06001991033554077,
-0.06839630007743835,
-0.0688362792134285,
0.09708964824676514,
-0.023038361221551895,
-0.01709992252290249,
-0.024160470813512802,
0.018736235797405243,
-0.03921634331345558,
0.031152212992310524,
-0.03... | 0.098286 |
# `argocd-server` Command Reference ## argocd-server Run the ArgoCD API server ### Synopsis The API server is a gRPC/REST server which exposes the API consumed by the Web UI, CLI, and CI/CD systems. This command runs API server in the foreground. It can be configured by following options. ``` argocd-server [flags] ``` ... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-server.md | master | argo-cd | [
0.0116841159760952,
0.024317465722560883,
-0.13277266919612885,
-0.04482925683259964,
-0.026877041906118393,
-0.10024899244308472,
0.006705587264150381,
-0.023011252284049988,
-0.0070274886675179005,
0.09446708858013153,
0.03555138781666756,
0.010100423358380795,
-0.06980253756046295,
-0.0... | 0.154978 |
flag is unused and will be removed in a future version. (default 24h0m0s) --loglevel string Set the logging level. One of: debug|info|warn|error (default "info") --metrics-address string Listen for metrics on given address (default "0.0.0.0") --metrics-port int Start metrics on given port (default 8083) -n, --namespace... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-server.md | master | argo-cd | [
-0.021352725103497505,
0.03962506353855133,
-0.07817406207323074,
0.021389856934547424,
0.0604071281850338,
-0.11090730875730515,
0.09503854811191559,
-0.03817784786224365,
0.023954328149557114,
-0.05152377113699913,
0.02194569632411003,
-0.05581648275256157,
-0.017454316839575768,
0.00198... | 0.137993 |
used to validate server certificate. If this is not provided, hostname used to contact the server is used. --tlsciphers string The list of acceptable ciphers to be used when establishing TLS connections. Use 'list' to list available ciphers. (default "TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384") --tlsmaxversion strin... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/server-commands/argocd-server.md | master | argo-cd | [
-0.016755184158682823,
0.07919416576623917,
-0.04354584589600563,
-0.08947757631540298,
-0.08238034695386887,
-0.04288412258028984,
-0.04322025924921036,
-0.046694159507751465,
0.07741046696901321,
-0.01697905734181404,
-0.026772670447826385,
-0.13182376325130463,
0.03630049526691437,
-0.0... | 0.129902 |
# v3.4 to 3.5 ## Breaking Changes ### UI extensions must externalize `react/jsx-runtime` The Argo CD UI was upgraded from React 16 to React 19 in 3.5. UI extensions built against an older Argo CD UI may fail to load with a `TypeError` until they are rebuilt to externalize `react/jsx-runtime`. The host UI surfaces the f... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/upgrading/3.4-3.5.md | master | argo-cd | [
-0.06916972249746323,
-0.012351343408226967,
0.06927435845136642,
0.02223335951566696,
0.07329714298248291,
-0.027520006522536278,
-0.02785468101501465,
0.007764081005007029,
-0.05304575338959694,
0.007065629120916128,
0.03419553488492966,
-0.004895295016467571,
-0.1112743467092514,
0.0934... | 0.108774 |
used for repositories without configured credentials Argo CD upgraded `go-git` to v5.19.x, which tightens SSH host-key verification. To keep host-key validation working against the Argo CD–managed `argocd-ssh-known-hosts-cm` ConfigMap (and to avoid `knownhosts: key mismatch` handshake failures with the new go-git), Arg... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/upgrading/3.4-3.5.md | master | argo-cd | [
-0.023750200867652893,
0.02127792499959469,
-0.07499076426029205,
0.009700709022581577,
-0.028691168874502182,
-0.050706543028354645,
0.012170528061687946,
-0.05162370204925537,
0.013029990717768669,
0.06048808991909027,
0.05867123231291771,
0.03073926642537117,
-0.003920014016330242,
0.01... | 0.073143 |
# v3.1 to 3.2 > Users operating large monorepos may encounter repo-server lock contention requiring pod restarts. A [fix](https://github.com/argoproj/argo-cd/pull/25127) is under review and will be included in the next patch release. ## Breaking Changes ### Hydration paths must now be non-root Source hydration (with [S... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/upgrading/3.1-3.2.md | master | argo-cd | [
-0.08903199434280396,
-0.014472142793238163,
0.02789466828107834,
0.002507496625185013,
0.0339556485414505,
-0.08858774602413177,
0.01711677573621273,
0.034901849925518036,
0.038487110286951065,
0.056148409843444824,
-0.025152884423732758,
0.006687888875603676,
-0.050157275050878525,
0.015... | 0.071453 |
active job completes. > This may cause your application to go from `Degraded` to `Healthy` to `Degraded` again. The CronJob status does not contain enough > information to infer the health of the last completed job if there are active jobs. > > If the CronJob constantly has active jobs, the health will be constantly `H... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/upgrading/3.1-3.2.md | master | argo-cd | [
-0.08901538699865341,
0.002224096329882741,
-0.05371778830885887,
0.049601778388023376,
0.023946009576320648,
-0.04945965111255646,
0.05143134668469429,
-0.028428083285689354,
-0.10662566125392914,
0.02882949635386467,
-0.02016138844192028,
0.021894607692956924,
-0.008293169550597668,
-0.0... | 0.119001 |
# Overview > [!NOTE] > This section contains information on upgrading Argo CD. Before upgrading please make sure to read details about > the breaking changes between Argo CD versions. Argo CD uses semver-like versioning that ensures the following rules: - The patch release does not introduce any breaking changes. So if... | https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/upgrading/overview.md | master | argo-cd | [
-0.003206629538908601,
-0.0433991365134716,
0.056736499071121216,
-0.060582999140024185,
0.03518800064921379,
-0.10965533554553986,
-0.04115177318453789,
-0.06509024649858475,
-0.12521480023860931,
0.09733644127845764,
0.01765507273375988,
0.05371171608567238,
-0.12487289309501648,
-0.0513... | 0.03384 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.