Anatomy of Abuse Shield Pods
wforce Pods
Both the wforce and syncdb deployments consist of Pods of this type; the syncdb deployment is simply a special case of
a wforce deployment.
A wforce pod consists of the following containers:
- Init Containers
- wforce-init - A container that runs a templating engine on the configuration file for wforce
- Containers
- wforce - The
wforceimage, that answers REST API queries and replicates statsdb messages etc. - wforce-agent - An agent that monitors the wforce-replication service endpoints, and loads any changes into
wforceusing the REST API.
- wforce - The
This is shown in the following diagram:
replfwd Pods
The replfwd pod is very similar to the wforce pod, and consists of the following containers:
- Init Containers
- wforce-init - A container that runs a templating engine on the configuration file for
replfwd
- wforce-init - A container that runs a templating engine on the configuration file for
- Containers
- replfwd - The
replfwdimage, that forwards statsdb and block/allow list messages to/from other clusters. - wforce-agent - An agent that monitors the
wforce-replicationservice endpoints and loads any changes intoreplfwdusing the REST API
- replfwd - The
This is shown in the following diagram:
