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

Add documentaiton for service account #221

Merged
merged 2 commits into from
Dec 28, 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: 1 addition & 1 deletion charts/lakefs/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ apiVersion: v2
name: lakefs
description: A Helm chart for running LakeFS on Kubernetes
type: application
version: 1.0.8
version: 1.0.9
appVersion: 1.4.0

home: https://lakefs.io
Expand Down
2 changes: 1 addition & 1 deletion charts/lakefs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -131,4 +131,4 @@ helm upgrade -f my-values.yaml my-lakefs lakefs/lakefs --set kv_upgrade=true
| `s3Fallback.aws_access_key` | An AWS access key to be used by the S3Proxy for authentication | |
| `s3Fallback.aws_secret_key` | An AWS secret key to be used by the S3Proxy for authentication | |
| `committedLocalCacheVolume` | A volume definition to be mounted by lakeFS and used for caching committed metadata. See [here](https://kubernetes.io/docs/concepts/storage/volumes/#volume-types) for a list of supported volume types. The default values.yaml file shows an example of how to use this parameter. | |

| `serviceAccount.name` | Name of the service account to use for the lakeFS pods. If not set, use the `default` service account. | |
4 changes: 4 additions & 0 deletions charts/lakefs/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,10 @@ lakefsConfig: |

serviceAccount: {}

# to use an existing service account, replace the serviceAccount map above with the following:
# serviceAccount:
# name: "my-serviceaccount"

# Extra Environment Values - allows yaml definitions
extraEnvVars:
# - name: VALUE_FROM_SECRET
Expand Down
Loading