* feat: extraArgs allows same flag multiple times
Superseeds #244 (I messed up the rebase 🤦)
Relates to #232
This change allows ArgoCD chart to render multiple times the same flag with different values
Mainly, if not only, used to specify multiple Redis Sentinel addresses
5ec5aeb002/manifests/ha/base/overlays/argocd-application-controller-deployment.yaml (L16)aeb48b0a69/util/cache/cache.go (L33)
```
--sentinel
```
using this syntax
```
controller:
extraArgs:
- --sentinel
- argocd-redis-ha-announce-0
- --sentinel
- argocd-redis-ha-announce-1
- --sentinel
- argocd-redis-ha-announce-2
```
instead of
```
controller:
extraArgs:
sentinel=argocd-redis-ha-announce-0:
sentinel=argocd-redis-ha-announce-1:
sentinel=argocd-redis-ha-announce-2:
```
Basically same syntax as the flags documentation
```
docker run --rm argoproj/argocd:v1.4.2 argocd-server help
...
Flags:
--app-state-cache-expiration duration Cache expiration for app state (default 1h0m0s)
--as string Username to impersonate for the operation
--as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
--basehref string Value for base href in index.html. Used if Argo CD is running behind reverse proxy under subpath different from / (default "/")
--certificate-authority string Path to a cert file for the certificate authority
--client-certificate string Path to a client certificate file for TLS
--client-key string Path to a client key file for TLS
--cluster string The name of the kubeconfig cluster to use
--connection-status-cache-expiration duration Cache expiration for cluster/repo connection status (default 1h0m0s)
--context string The name of the kubeconfig context to use
--default-cache-expiration duration Cache expiration default (default 24h0m0s)
--dex-server string Dex server address (default "http://argocd-dex-server:5556")
--disable-auth Disable client authentication
--gloglevel int Set the glog logging level
-h, --help help for argocd-server
--insecure Run server without TLS
--insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
--kubeconfig string Path to a kube config. Only required if out-of-cluster
--loglevel string Set the logging level. One of: debug|info|warn|error (default "info")
--metrics-port int Start metrics on given port (default 8083)
-n, --namespace string If present, the namespace scope for this CLI request
--oidc-cache-expiration duration Cache expiration for OIDC state (default 3m0s)
--password string Password for basic authentication to the API server
--port int Listen on given port (default 8080)
--redis string Redis server hostname and port (e.g. argocd-redis:6379).
--redisdb int Redis database.
--repo-server string Repo server address (default "argocd-repo-server:8081")
--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. (default "0")
--sentinel stringArray Redis sentinel hostname and port (e.g. argocd-redis-ha-announce-0:6379).
--sentinelmaster string Redis sentinel master group name. (default "master")
--server string The address and port of the Kubernetes API server
--staticassets string Static assets directory path
--tlsmaxversion string The maximum SSL/TLS version that is acceptable (one of: 1.0|1.1|1.2)
--tlsminversion string The minimum SSL/TLS version that is acceptable (one of: 1.0|1.1|1.2)
--token string Bearer token for authentication to the API server
--user string The name of the kubeconfig user to use
--username string Username for basic authentication to the API server
--x-frame-options value Set X-Frame-Options header in HTTP responses to value. To disable, set to "". (default "sameorigin")
```
Signed-off-by: Carlos Juan Gómez Peñalver <carlosjuangp@gmail.com>
* fix: bump up chart version
* Better Helm chart NOTES.txt templating
Add some extra templating to NOTES.txt, which are displayed to the
user after a successful helm install command. These are really
helpful notes, but if you didn't specify a release name of argocd
or put it in a separate namespace, these commands weren't exactly
working with a copy paste. Now they should take into account
the release name and release namespace helm was given.
* Small CONTRIBUTING.md command line change
Instead of just doing `argocd version`, be a little more explicit
by passing in the server name and insecure flag. This will make
sure that you're doing the version of the instance you're
port-forwarding above, as opposed to some other argocd.
* Add application controller resources
First chart version for argo-cd
added the new labels recommeneded for k8
* Add repo server resources
Use legacy label and new one for application controller selectors
Set labels for deployment for easier discovery
* Configure git repositories, helm chart museums and dex connectors
This way argo-cd could be configured to update itself via helm
* Parameterize the rbac configmap
* Parameterize webhook secrets
* Parameterize server deployment and set services with the labels
* Add service account, role and rolebinding for server deployment
* Clean the old label, use only latest recommendations
Follow the ideas and changes of https://github.com/argoproj/argo-cd/pull/1035
* Fix var naming issues
* Fix server service incorrect ports
* Install crds with helm hook
* Enable cluster admin accessby default
Default installation will allow installing apps in the current cluster without
inputted credentials. For other clusters inputted credentials will be needed
* Parameterize the dex server
* Harcode resource names because code expects them this way
Some resource names and application urls are hardcoded in code with these
names. So they can't be parameterized.
* Create the ingress with tls passthrough support
Tls is terminated on the ArgoCD server, not on ingress
* Fix typo on application controller sa
* Add notes on how to connect to server UI after installation
