fix: nginx read only file issue for ubi images for frontend images #3810
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change?
Mount an emptyDir to the /var/log/nginx directory in the frontend deployment to resolve access issues caused by a read-only file system in the new UBI-based frontend images.
Does this PR rely on any other PRs?
https://github.com/kubecost/kubecost-frontend/pull/2125/files
https://github.com/kubecost/kubecost-frontend/pull/2109
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Users would be able to deploy kubecost using the UBI frontend image which earlier went on a
CrashLoopBackOff
Links to Issues or tickets this PR addresses or fixes
What risks are associated with merging this PR? What is required to fully test this PR?
No
How was this PR tested?
Deployed kubecost using these changes and frontend UBI image.
Have you made an update to documentation? If so, please provide the corresponding PR.
NA