anchor.diff:  |Limitations
   
   |FIPS compliant operating systems: RHEL 7 and {op-system}.
  -.3+|The FIPS implementations lacks use of single function computing hash and validating keys based on compliant run times and services. This limitation will continue to be evaluated and improved in future {product-title} releases.
  +.3+|The FIPS implementation does not offer a single function that both computes hash functions and validates the keys that are based on that hash. This limitation will continue to be evaluated and improved in future {product-title} releases.
   
   |FIPS compliant CRI-O runtimes.
   |FIPS compliant {product-title} services.
  
positive.code: [id="installation-about-fips-components-runtimes_{context}"]
  === Runtimes
  
  To ensure that containers know that they are running on a host that has is using FIPS validated cryptography modules, use CRI-O to manage your runtimes. mode. CRI-O supports FIPS-Mode, in that it configures the containers to know that they are running in FIPS mode.
  
  [id="installing-fips-mode_{context}"]
  ==  Installing a cluster in FIPS mode
  
negative.code: [id="installation-about-fips-components_{context}"]
  ==  FIPS compliance in components that the cluster uses
  
  Although the {product-title} cluster itself uses FIPS validated modules, ensure that the systems that support your {product-title} cluster use FIPS validated modules for cryptography.
  
  [id="installation-about-fips-components-etcd_{context}"]
  === etcd
  