Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Add notes on IAM Auth for workflow persistence #11668

Merged
merged 2 commits into from
Aug 24, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .spelling
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,7 @@ Couler
ClusterRoleBinding
CRD
CRDs
CloudSQL
DataDog
Dataflow
DeleteObject
Expand All @@ -61,6 +62,7 @@ Homebrew
InitContainer
InsideBoard
Invocators
IAM-based
Istio
J.P.
Jemison
Expand Down
4 changes: 4 additions & 0 deletions docs/workflow-archive.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,10 @@ Example:

kubectl create secret generic argo-postgres-config -n argo --from-literal=password=mypassword --from-literal=username=argodbuser

Note that IAM-based authentication is not currently supported. However, you can start your database proxy as a sidecar
(e.g. via [CloudSQL Proxy](https://github.com/GoogleCloudPlatform/cloud-sql-proxy) on GCP) and then specify your local
proxy address, IAM username, and an empty string as your password in the persistence configuration to connect to it.

The following tables will be created in the database when you start the workflow controller with enabled archive:

* `argo_workflows`
Expand Down