Commit d14ff97e authored by Evan Read's avatar Evan Read

Merge branch 'docs-update-modsec-clarify-disablement' into 'master'

Clarify ModSecurity docs- rule engine disablement

See merge request gitlab-org/gitlab!21206
parents 72aa2d0b 83b8fa2e
...@@ -267,13 +267,19 @@ This feature: ...@@ -267,13 +267,19 @@ This feature:
kubectl -n gitlab-managed-apps exec -it $(kubectl get pods -n gitlab-managed-apps | grep 'ingress-controller' | awk '{print $1}') -- tail -f /var/log/modsec/audit.log kubectl -n gitlab-managed-apps exec -it $(kubectl get pods -n gitlab-managed-apps | grep 'ingress-controller' | awk '{print $1}') -- tail -f /var/log/modsec/audit.log
``` ```
There is a small performance overhead by enabling `modsecurity`. However, if this is There is a small performance overhead by enabling `modsecurity`. If this is
considered significant for your application, you can toggle the feature flag back to considered significant for your application, you can either:
false by running the following command within the Rails console:
- Disable ModSecurity's rule engine for your deployed application by setting
```ruby [the deployment variable](../../topics/autodevops/index.md)
Feature.disable(:ingress_modsecurity) `AUTO_DEVOPS_MODSECURITY_SEC_RULE_ENGINE` to `Off`. This will prevent ModSecurity from
``` processing any requests for the given application or environment.
- Toggle the feature flag to false by running the following command within your
instance's Rails console:
```ruby
Feature.disable(:ingress_modsecurity)
```
Once disabled, you must [uninstall](#uninstalling-applications) and reinstall your Ingress Once disabled, you must [uninstall](#uninstalling-applications) and reinstall your Ingress
application for the changes to take effect. application for the changes to take effect.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment