> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/knowledge-base/LmMmmLqSszWn8sdGe7gH/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/knowledge-base/LmMmmLqSszWn8sdGe7gH/prerequisite-checklist-hub/self-host-installation-and-deployment-checklist.md). # Self-Host Installation and Deployment Checklist #### Introduction This page contains a comprehensive checklist of requirements and considerations for customers planning to perform a self-deployment of Immuta version 2024.2 and above on Kubernetes. It is crucial to review these items before initiating the installation process to ensure a successful deployment. This checklist includes system requirements, access validations, and configuration checks essential for a smooth setup. #### Self-Host Installation and Deployment Checklist 1. **System Requirements**: * For more detail go [here](https://documentation.immuta.com/2024.2/self-managed-deployment/getting-started#install-immuta). | Kubernetes distribution | Kubernetes versions | | ----------------------------------------- | ------------------- | | Elastic Kubernetes Service (EKS) | 1.25 - 1.29 | | Azure Kubernetes Service (AKS) | 1.27 - 1.29 | | Google Kubernetes Engine (GKE) | 1.26 - 1.29 | | Red Hat OpenShift | 1.25 - 1.29 | | SUSE Rancher Government (RKE2) | 1.25 - 1.29 | | SUSE K3s - *For evaluation purposes only* | 1.25 - 1.29 | 2. **Repository Access for Immuta Images**: * Helm 3.2.0+ * Validate access to the `ocir.immuta.com` repository. If access is not granted, acquire the necessary permissions by contacting your Immuta representative. * Command line to authenticate with the given token: example [here](https://documentation.immuta.com/2024.2/self-managed-deployment/getting-started#ocir.immuta.com). * Review IEHC - Immuta Enterprise Helm Chart. The deprecated IHC - Immuta Helm Chart is for legacy installation of Immuta 2024.1.x <= 3. **PostgreSQL Database Setup**: * Requires PostgreSQL **15.0+** * The `pgcrypto` extension must be enabled. * Ensure your PostgreSQL database is [set up and configured](https://documentation.immuta.com/2024.2/self-managed-deployment/install/managed-public-cloud#postgresql-1) for Immuta deployment. Verify the following: * The PostgreSQL instance's hostname/FQDN is [resolvable from within the Kubernetes cluster](https://documentation.immuta.com/2024.2/self-managed-deployment/troubleshooting#common). * The PostgreSQL instance is [accepting connections](https://documentation.immuta.com/2024.2/self-managed-deployment/troubleshooting#how-do-i-determine-if-the-database-is-accepting-connections). * Example options: * Amazon Web Services (AWS): [Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/rds/) * Microsoft Azure: [Azure Database for PostgreSQL](https://learn.microsoft.com/en-us/azure/postgresql/) * Google Cloud Platform (GCP): [Google Cloud SQL for PostgreSQL](https://cloud.google.com/sql/docs/postgres) 4. **ElasticSearch Configuration**: * ElasticSearch v7+ API * OpenSearch compatible with ElasticSearch v7 API or newer * Deploy and configure Elasticsearch, ensuring the connection is valid. Check the following: * The Elasticsearch instance's hostname/FQDN is [resolvable from within the Kubernetes cluster](https://documentation.immuta.com/2024.2/self-managed-deployment/troubleshooting#common). * The Elasticsearch instance is [accepting connections](https://documentation.immuta.com/2024.2/self-managed-deployment/troubleshooting#elasticsearch). * Example options: * [Amazon OpenSearch](https://docs.aws.amazon.com/opensearch-service/) * [Elastic Cloud on Azure](https://www.elastic.co/partners/microsoft-azure) * [Elastic Cloud on Google Cloud](https://www.elastic.co/partners/google-cloud) 5. **Ingress and TLS Configuration**: * Confirm that Ingress and TLS are configured correctly and that any network connectivity issues have been resolved. * Review [Ingress configuration](https://documentation.immuta.com/2024.2/self-managed-deployment/configure/ingress-configuration). * Review [TLS Configuration](https://documentation.immuta.com/2024.2/self-managed-deployment/configure/tls-configuration). * Validate Immuta deployment if these configurations are not set up properly, such as using port forwarding once Immuta installation is completed and LoadBalance is not set. For example: * `kubectl --namespace port-forward service/immuta-secure 8080:http` * Then test with `localhost:8080` via a browser. 6. **General Considerations**: * Ensure you have reviewed the Immuta installation documentation thoroughly. * Address any questions or concerns before proceeding with deployment. * If applicable, note any errors or issues encountered during previous attempts to deploy. * [Credentials management](https://documentation.immuta.com/2024.2/self-managed-deployment/configure/rotating-credentials) consideration if this is a requirement. * Review [FAQ](https://documentation.immuta.com/2024.2/self-managed-deployment/troubleshooting) for Immuta deployments. 7. **Official** [Immuta Self-Managed Deployment Documentation](https://documentation.immuta.com/2024.2/self-managed-deployment). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://documentation.immuta.com/knowledge-base/LmMmmLqSszWn8sdGe7gH/prerequisite-checklist-hub/self-host-installation-and-deployment-checklist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.