![]() ![]() After the pipeline is successful, your application is upgraded.XDB_INITIALIZE or the XDB_MIGRATE to effectively disable them. Remove the variables, or rename the variables temporarily to If you have set the DB_INITIALIZE or DB_MIGRATE variables, either.Minimum PostgreSQL version supported by Auto DevOps. If you have a POSTGRES_VERSION set, make sure it is set to 9.6.16 or later.Safeguard to prevent accidental deletion of databases. Set AUTO_DEVOPS_POSTGRES_DELETE_V1 to a non-empty value.Newer 8.2.1-based PostgreSQL, and removes the older 0.7.1-based Set AUTO_DEVOPS_POSTGRES_CHANNEL to 2.POSTGRES_VERSION variables to specific environments, for example, staging. For more information, seeĭetected an existing PostgreSQL database.ĪUTO_DEVOPS_POSTGRES_CHANNEL, AUTO_DEVOPS_POSTGRES_DELETE_V1 and Ensure you have not set POSTGRES_ENABLED to false, as this setting deletesĪny existing channel 1 database.So that the in-cluster database does not get modified after the database dump is created. The steps below include taking the application offline This varies based on Kubernetes providers. Ensure that you can access your Kubernetes cluster using kubectl.Restoring the database dump into the new PostgreSQL.Installing a new PostgreSQL database using the newer version 8.2.1 of the chartĪnd removing the old PostgreSQL installation.This guide provides instructions on how to migrate your PostgreSQL database, which GitLab encourages users to migrate their database to the newer PostgreSQL chart. Can be set to from 0.7.1 to 8.2.1 in GitLab 12.9 and later.The version of the chart used to provision PostgreSQL: In-cluster PostgreSQL database for your application. When POSTGRES_ENABLED is true, Auto DevOps provides an ![]() Reinstate your application Upgrading PostgreSQL for Auto DevOps. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |