Swap volumeMount to set the deployment with both mountPath #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR simply swaps the volumeMount to trigger the deployment and set both volumeMount to the logrotate container.
A high-priority alert triggered for node Memory-Critical. While investigating, the modsec-controller has increased in the memory usage as shown in the grafana graph.
This is because the logrotate didnot perform the audit log cleanup from the controller container and the volumeMount to
var/log/auditon the logrotate container is missing in deployment of the modsec-controller.The reason is, during the terraform apply for removing the duplicate VolumeMounts, the helm_release terraform missed to check that this is duplicate and removed the existing one. But the code still refers to both the volumeMounts.