Configuration using CRDs - special options for Large Scale Deployments

The advanced configuration options explained on this page require an existing helm-based deployment on K8s with CRD version v1beta2. See here for instructions: Install Using Helm - new flow (beta)

Specifically for usage in larger scale deployments on Kubernetes, open-appsec offers some advanced functionalities for declarative configurations:

appsecClassName property for custom resources

appsecClassName support allows having multiple, distinct sets of custom resources for the configuration of different, parallel open-appsec deployments on the same Kubernetes cluster. It is possible to link each custom resource using the optional appsecClassName property with one of your open-appsec deployments set to use that same appsec class, find the configuration details here:

Using appsec class for assigning separate custom resources to specific deployments

namespace-scoped CRDs

It is possible to create and manage the custom resources for open-appsec configuration in a specific namespace by using the new namespace-scoped CRDs instead of using cluster-scoped CRDs, find the configuration details here:

Using namespace-scoped custom resources