In order to make Curieproxy work, the following changes have to be made:
the Module CR has to be extended with the necessary lua_scripts (note: this may change from version to version (Curiefense))
the image should be changed to an image containing Curieproxy
a sidecar container has to be added (Curiesync)
an emptyDir volume has to be mounted to both containers (Emissary, Curiesync)
In addition to the above, the Curiesync container needs a ConfigMap or a Secret containing credentials to the config store bucket.
Also, a LogService CR can optionally be created to send logs to Curielogger (although this may change in 1.6).
The Kubernetes YAML method either requires patched YAML files, or use Kustomize (see this repo).
The Helm chart provides all the necessary extension points, so it should be a matter of documentation.
Keep in mind that Curieproxy also requires Redis for features, like rate limiting. The credentials and information for that has to be injeceted.....probably to the Curieproxy (Emissary) container?
Emissary comes with two installation methods:
In order to make Curieproxy work, the following changes have to be made:
ModuleCR has to be extended with the necessarylua_scripts(note: this may change from version to version (Curiefense))In addition to the above, the Curiesync container needs a ConfigMap or a Secret containing credentials to the config store bucket.
Also, a
LogServiceCR can optionally be created to send logs to Curielogger (although this may change in 1.6).The Kubernetes YAML method either requires patched YAML files, or use Kustomize (see this repo).
The Helm chart provides all the necessary extension points, so it should be a matter of documentation.
Keep in mind that Curieproxy also requires Redis for features, like rate limiting. The credentials and information for that has to be injeceted.....probably to the Curieproxy (Emissary) container?