4 Commits

Author	SHA1	Message	Date
klagroix	28ab779a5c	[bitnami/mlflow] Remove string constraint from NetworkPolicy extraIngress/extraEgress (#24514) ... * Remove string constraint from NetworkPolicy extraIngress/extraEgress Signed-off-by: Kirby Lagroix <kirby@lagroix.com> * Bump chart version Signed-off-by: Kirby Lagroix <kirby@lagroix.com> --------- Signed-off-by: Kirby Lagroix <kirby@lagroix.com>	2024-03-18 17:44:50 +01:00
Thatcher	d2e8689147	[bitnami/mlflow] fix: allowed minAvailable to be percentage, updated schema (#23555) ... Signed-off-by: Thatcher Peskens <thatcher@t2studio.nl> Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>	2024-02-21 10:57:25 +01:00
Gösta	50c0de916e	[bitnami/mlflow] feat: 🔒 make S3 secret optional (#22699) ... Previously, enabling external S3 meant that the chart was setting the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment vari- ables with values from a kubernetes secret. However, users may want to use other means of providing these credentials, e.g. on EKS, where it's possible to use a web identity token file. This patch introduces a new value that lets users opt out of using the ID and access key mechanism. Signed-off-by: Gösta von Götz <goesta@aisight.de>	2024-01-26 15:00:25 +01:00
Javier J. Salmerón-García	be9324e370	[bitnami/mlflow] feat: 🎉 Add chart (#20069) ... ### Description of the change <!-- Describe the scope of your change - i.e. what the change does. --> ### Benefits <!-- What benefits will be realized by the code change? --> ### Possible drawbacks This PR adds a helm chart for MLflow. Has the following features: - TLS support - Network policies - Prometheus metrics - HPA and VPA - Bitnami standards --------- Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com> Signed-off-by: Javier J. Salmerón-García <jsalmeron@vmware.com> Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> Co-authored-by: Fran Mulero <fmulero@vmware.com> Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>	2023-10-16 10:50:20 +02:00