@@ -24,11 +24,14 @@ How the `GODEBUG` environment variable is set depends on how the operator is ins
2424[NOTE]
2525====
2626Although the Coherence Operator image can easily be installed in a FIPS compliant mode, none of the default
27- Oracle Coherence images used by the operator are FIPS complaint.
27+ Oracle Coherence images used by the operator are FIPS compliant.
28+
2829The Oracle Coherence team does not currently publish FIPS compliant Coherence images.
29- Coherence is FIPS compatible and correctly configured applications running in an image that has a FIPS
30- compliant JDK and FIPS compliant base O/S will be FIPS complaint.
3130Customers must build their own FIPS complaint Java and Coherence images, which the operator will then manage.
31+
32+ Coherence is FIPS _compatible_ so a correctly configured application running in an image that has a FIPS
33+ compliant JDK and FIPS compliant base O/S will be FIPS complaint. To be fully FIPS compliant these images must then
34+ be run in a container runtime on a FIPS compliant host.
3235====
3336
3437=== Install Using Yaml Manifests
@@ -61,6 +64,21 @@ then add the required `GODEBUG` value, for example
6164 value: fips140=on
6265----
6366
67+
68+ === Install Using Kustomize
69+
70+ If <<docs/installation/013_install_kustomize.adoc,installing the operator using Kustomize>> (or using `kubectl -k`)
71+ the Coherence manifest yaml files contain a FIPS overlay that adds the `GODEBUG` environment variable
72+ to the Operator container.
73+
74+ The following command will generate a yaml manifest that installs the operator with FIPS enabled:
75+
76+ [source,bash]
77+ ----
78+ kustomize build manifests/overlays/fips
79+ ----
80+
81+
6482=== Install Using Helm
6583
6684If <<docs/installation/012_install_helm.adoc,installing the operator using Helm>>
0 commit comments