charts
charts copied to clipboard
Helm charts
We currently configure the chart to use local service names `fluffy-sso` and `fluffy-rbac`. In some cases users need a way to use FQDN (i.e ..svc.cluster.local) or in general case, set...
lakefs deployment currently does not have resources set. This can be a problem in case namespaces have quotas defined in order to allocate resources for different namespaces. It would be...
It would be great to be able to set custom labels to the pods via HelmChart. Those can help a lot when doing node scheduling (like sometimes adding a label...
The `deployment.yaml` file does not support specification of `imagePullSecrets`. This is useful for scenarios where this chart is used as a dependency by another chart that includes altering the target...
## Red Hat certification requirements and process for Kubernetes applications In order to have lakeFS chart listed, it first needs to get certified: https://redhat-connect.gitbook.io/partner-guide-for-red-hat-openshift-and-container/helm-chart-certification/overview Following a pull-request that verified the...
... with Helm. Relevant Slack: https://lakefs.slack.com/archives/C016726JLJW/p1606932878152800
To configure the KV when using enterprise we must do it twice (i.e duplicate places to configure postgres). There should be single source of truth that lakeFS/fluffy both use. Regardless...