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
When using NGINX Plus R33 and NIM 2.18 with the standard /config declaration version 5.2 (both with and without the "output.license.token" field), the following error occurs:
"Config apply failed (write): open /etc/nginx/license.jwt: read-only file system"
Environment
NGINX Plus Version: R33
NIM Version: 2.18
Config Declaration Version: 5.2
Deployment: Kubernetes
Steps to Reproduce
Deploy NGINX Plus R33 on Kubernetes.
Mount the /etc/nginx/license.jwt file using a volumeMount from a Kubernetes Secret.
Apply a configuration using the standard /config declaration version 5.2, with or without the output.license.token field.
The configuration should apply successfully without attempting to modify or overwrite the license file when it is already present and mounted as read-only.
Additional Context
The /etc/nginx/license.jwt file is loaded via a Kubernetes Secret and mounted as read-only. This setup should ensure that the license file remains unmodified. However, the current behavior attempts to write to the file, causing the error.
Relevant Logs/Screenshots
If needed, I can provide additional logs or screenshots to further clarify the issue.
The text was updated successfully, but these errors were encountered:
Issue Summary
When using NGINX Plus R33 and NIM 2.18 with the standard /config declaration version 5.2 (both with and without the "output.license.token" field), the following error occurs:
Environment
Steps to Reproduce
Observed Behavior
The following error message is returned:
Expected Behavior
The configuration should apply successfully without attempting to modify or overwrite the license file when it is already present and mounted as read-only.
Additional Context
The
/etc/nginx/license.jwt
file is loaded via a Kubernetes Secret and mounted as read-only. This setup should ensure that the license file remains unmodified. However, the current behavior attempts to write to the file, causing the error.Relevant Logs/Screenshots
If needed, I can provide additional logs or screenshots to further clarify the issue.
The text was updated successfully, but these errors were encountered: