Kubernetes Google Server-side tagging memory leak troubleshooting
Recently, we deployed a Kubernetes cluster of the server-side tagging solution provided by Google. They provide a docker image that we are using in our managed Kubernetes cluster that is deployed on DigitalOcean.
We started observing that the memory usage is gradually increasing overtime. By analysing this problem further and running some tests we suspect that the containers running the Docker image listed above are causing this problem. Below you can see that restarting the containers resulted in a significant drop in the memory usage. The memory usage given by kubectl top pods -A demonstrated the same drop.
We have already set the resource limits for deployments running this image to prevent it from growing till the nodes run out of resources. However, we did not expect this behavior from this image. Does anyone know if this is a common problem with this image? Could there be any other reasons such as cluster settings causing this problem? And what would be the best practise to handle this potential memory leak? One of the solutions we are currently thinking of is scheduling a rollout restart every 24 hours.
The problem has resolved itself. The problem seemed to occur along with the June 6/7, 2023 release of Google Tag Manager and was resolved with the June 13, 2023 release.
- Docker Compose wait for container X before starting Y
- How to use rules_oci to run an image local via Docker?
- Getting error "Get http://localhost:9443/metrics: dial tcp 127.0.0.1:9443: connect: connection refused"
- How to install pyarrow on an Alpine Docker image?
- Unable to push image to ACR from terraform - could not get auth config (the credentialhelper did not work or was not found):
- Docker returning Error 133: Failed to create temporary file with plenty of disk space
- Database's backup location that created by Azure Data Studio on Mac M1
- ubuntu wslregisterdistribution failed with error: 0x80041002
- System.InvalidOperationException: Failed to deploy distro docker-desktop to <localpath>: exit code: -1
- Installing specific version of NodeJS and NPM on Alpine docker image
- intellij idea wsl 2 can't load projet from \\WSL.LOCALHOST\[distrib]
- Docker "protocol not available" after context change
- How to configure different dockerfile for development and production
- Is it possible to convert the publish method of an App Service from Code to Docker?
- Jib create folder for temporary files and changing folder ownership
- Heroku: How to release an existing image in gitlab CI/CD?
- Access to full /proc in Docker container
- lookup registry-1.docker.io: no such host
- Nestjs doesn't handle request from nginx proxy_pass using docker-compose
- PackagesNotFoundError : The following packages are not available from current channels:
- Prisma openssl version issue
- why are alpine versions of node throwing an error that @jridgewell/gen-mapping module not found?
- Safe ways to specify postgres parameters for healthchecks in docker compose
- How to get a list of images on docker registry v2
- Docker is in volume in use, but there aren't any Docker containers
- PhpStorm inserts wrong client_host IP when trying to run debug session
- How to Properly Inject Service Account Credentials in Google Cloud Build for Cloud Run Deployment?
- Docker - COPY file from different working directory to another is not working
- starting container process caused: exec: "fastapi": executable file not found in $PATH: unknown
- docker login fails while using docker-credential-secretservice