Difference between revisions of "User:Naresh"
| Line 1: | Line 1: | ||
| − | + | Deploying ACP MariaDB and ACP Session to K8S | |
We have created custom images from the local system for the MariaDB and ACP to deploy pods on the GCP K8s Engine | We have created custom images from the local system for the MariaDB and ACP to deploy pods on the GCP K8s Engine | ||
| Line 30: | Line 30: | ||
| + | 2. We have used step 1 to create custom ACP docker image | ||
| − | |||
| Line 37: | Line 37: | ||
Below is screenshot where we are tagging the image as per the GCP repo , so that we can push the image to GCP | Below is screenshot where we are tagging the image as per the GCP repo , so that we can push the image to GCP | ||
| − | [[File:Acp session tagged images.png|center|thumb]] | + | [[File:Acp session tagged images.png|center|thumb]]As per below Screenshot we are tagging the image and pushing it to the GCP repo. |
| + | |||
| + | [[File:Custom Image tagging and Pushing to GCP.png|center|thumb]] | ||
Revision as of 07:14, 1 April 2025
Deploying ACP MariaDB and ACP Session to K8S
We have created custom images from the local system for the MariaDB and ACP to deploy pods on the GCP K8s Engine
MariadB docker file contains below Details:
The Docker file contains the Image used and we are installing the mariadb-client on the image , once the image is created this is pushed to GCP image repository
Mariadb-Client is installed to connect locally from HeidiSQL APP.
For ACP Session , we have created custom docker image with two steps
1. Created windows docker image with sql installed.
2. We have used step 1 to create custom ACP docker image
Below is screenshot where we are tagging the image as per the GCP repo , so that we can push the image to GCP
As per below Screenshot we are tagging the image and pushing it to the GCP repo.
