500mCPU, the non-scalable one has
300m, the images server has
1000m. 2 Cores is recommended for the basic setup.
256MiBof memory, the non-scalable one has
64MiB, the images server have a limit of
1GiBof memory. 1 GB of memory is recommended for the basic setup.
pg_partmaninstalled, the version must be >= 4.0.
pg_partman>=4.0, at least 5GB storage
kubectlwith a version matching the Kubernetes server version. For example, if the server is 1.21, then you should be using the latest version of
This step is optional if you do not enable profile image.
Local. The caveat of this approach is that if the request is routed to a node without any NGINX ingress controller running on, the request is dropped. The simplest way to ensure one NGINX ingress controller running on a node is to use DaemonSet.
authgear: Install the helm chart in this namespace
authgear-apps: Authgear-generated resources are in this namespace.
helm create authgear-deploy. Remove the generated boilerplate
This step is optional if you do not enable Elasticsearch.
authgear.secrets.yamlshared by all apps.
authgear.yaml. Save the output to
authgear.secrets.yaml. Save the output to
resources/authgear/authgear.secrets.yaml. You must remove the
"elasticsearch"items from it. These items are included in the Secret you created in the previous step.
authgear.portalServer.imageto a newer value.
helm upgrade. We try hard to make sure the modification to the database is backward-compatible, which means older version of Authgear can run with a higher version of database schema.
false. You can then study the source code of this Helm chart, and create the Ingresses to suit your needs.