Skip to content
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

Unable to send declaration with R33 on Kubernetes with license.jwt as VolumeMount/Secret #75

Open
gelmistefano opened this issue Jan 22, 2025 · 0 comments

Comments

@gelmistefano
Copy link

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:

"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

  1. Deploy NGINX Plus R33 on Kubernetes.
  2. Mount the /etc/nginx/license.jwt file using a volumeMount from a Kubernetes Secret.
  3. Apply a configuration using the standard /config declaration version 5.2, with or without the output.license.token field.

Observed Behavior

The following error message is returned:

2025-01-22T11:27:12.776Z        INFO    b5828176-938b-4916-972b-518884deefad    placement/placement.go:535      acked (error=true): b5828176-938b-4916-972b-518884deefad [nim]:[acked created: 2025-01-22T11:27:12.503Z {init:1.840605ms placed:510.147µs queued:211.281797ms pending:15.712µs deployed:31.012µs dispatched:7.107479ms elapsed:272.036989ms}] [instance:4f34f73b-b575-3f59-be82-d95ea067db06: apply: 56.917428ms] {"instance:4f34f73b-b575-3f59-be82-d95ea067db06":"Config apply failed (write): open /etc/nginx/license.jwt: read-only file system"}

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant