adutra commented on code in PR #3265: URL: https://github.com/apache/polaris/pull/3265#discussion_r2619262632
########## site/content/in-dev/unreleased/configuring-polaris-for-production/configuring-helm.md: ########## @@ -0,0 +1,132 @@ +--- +# +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. +# +title: Configuring Helm for Production +linkTitle: Configuring Helm +type: docs +weight: 601 +--- + +This guide provides instructions for configuring the Polaris Helm chart for a production environment. For full list of chart values, see the [main Helm chart documentation](../../helm/). + +The default Helm chart values are suitable for development and testing, but they are not recommended for production. Following are the key areas to consider for production deployment. + +## Persistence + +By default, the Polaris Helm chart uses an `in-memory` metastore, which is not suitable for production. A persistent backend must be configured to ensure data is not lost when pods restart. + +To use a persistent backend, `persistence.type` must be set to `relational-jdbc`, and a Kubernetes secret containing the database connection details must be provided. + +```yaml +persistence: + type: relational-jdbc + relationalJdbc: + secret: + name: "polaris-persistence-secret" # A secret containing db credentials + username: "username" + password: "password" + jdbcUrl: "jdbcUrl" +``` + +## Resource Management + +For a production environment, it is crucial to define resource requests and limits for the Polaris pods. Resource requests ensure that pods are allocated enough resources to run, while limits prevent them from consuming too many resources on the node. + +Resource requests and limits can be set in the `values.yaml` file: + +```yaml +resources: + requests: + memory: "1Gi" Review Comment: These are low values. Of course the right values depend on the use case, but I would suggest something higher as an example of "good" production setup: 8Gi - 4 cpus for instance. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
