You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Laravel initializes with a valid cache path (when the storage directory is mounted). The application connects to the MySQL database and Redis using the configured hostnames and ports.
Actual behaviour
Laravel throws the following error: production.ERROR: Please provide a valid cache path. The application logs indicate a connection timeout while trying to connect to MySQL: wait-for-it.sh: waiting 60 seconds for mysql:3306 wait-for-it.sh: timeout occurred after waiting 60 seconds for mysql:3306
Detailed description
The Mixpost application encounters two issues during deployment in a Kubernetes environment using a custom Helm chart:
Invalid Cache Path: Laravel throws an error stating that no valid cache path is provided, despite the storage directory being configured and mounted as well as a REDIS_HOST variable is configured.
Connection Timeout: The application fails to connect to the MySQL database, resulting in a connection timeout, even though the environment variables for database and Redis hosts are configured.
This report is based on the usage of the bjw-s Helm Chart, specifically the app-template chart v 3.5.1 and the following manifest:
Steps to reproduce the problem
app-template
from bjw-s) in a Kubernetes cluster using the following configuration:Expected behaviour
Laravel initializes with a valid cache path (when the storage directory is mounted). The application connects to the MySQL database and Redis using the configured hostnames and ports.
Actual behaviour
Laravel throws the following error: production.ERROR: Please provide a valid cache path. The application logs indicate a connection timeout while trying to connect to MySQL: wait-for-it.sh: waiting 60 seconds for mysql:3306 wait-for-it.sh: timeout occurred after waiting 60 seconds for mysql:3306
Detailed description
The Mixpost application encounters two issues during deployment in a Kubernetes environment using a custom Helm chart:
Invalid Cache Path: Laravel throws an error stating that no valid cache path is provided, despite the
storage
directory being configured and mounted as well as a REDIS_HOST variable is configured.Connection Timeout: The application fails to connect to the MySQL database, resulting in a connection timeout, even though the environment variables for database and Redis hosts are configured.
This report is based on the usage of the bjw-s Helm Chart, specifically the
app-template
chart v 3.5.1 and the following manifest:The text was updated successfully, but these errors were encountered: