-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ROX-19980 pre-built scanner-db image #1310
base: master
Are you sure you want to change the base?
Conversation
Images are ready for the commit at 4328d2f. To use the images, use the tag |
906063a
to
7e434d1
Compare
/retest |
echo "Creating /var/lib/postgresql/data/pgdata..." | ||
mkdir -p /var/lib/postgresql/data/pgdata | ||
|
||
echo "Moving archive to target directory..." | ||
mv /tmp/data.tar.gz /var/lib/postgresql/data/pgdata/data.tar.gz | ||
|
||
echo "Uncompressing into /var/lib/pgsql/data/pgdata..." | ||
tar -xzf /var/lib/postgresql/data/pgdata/data.tar.gz -C /var/lib/postgresql/data/pgdata | ||
|
||
echo "Removing archive..." | ||
rm /var/lib/postgresql/data/pgdata/data.tar.gz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jvdm @RTann Could we move these steps to build time instead of start-up time?
@ludydoo proposes this to save IO in the cloud service which prevents us from cluster upgrades and increases ACS upgrade complexity.
Every restart of ACS instances causes to write ~1.8GB per instance.
Additionally the manifest must be updated that the scanner-db pod can read the Postgres Password.
What do you think about this approach? It seems simple and scaleable to us.
cc @ludydoo
No description provided.