Skip to content

Commit fcc0cb4

Browse files
stevsmitSteven Smith
andauthored
Note removal (quay#1168)
Co-authored-by: Steven Smith <[email protected]>
1 parent 6dea09b commit fcc0cb4

File tree

3 files changed

+0
-21
lines changed

3 files changed

+0
-21
lines changed

modules/clair-clairctl-standalone.adoc

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,6 @@
88

99
Use the following procedures to set up a self-managed deployment of Clair for a disconnected {ocp} cluster.
1010

11-
[IMPORTANT]
12-
====
13-
Due to known issue link:https://issues.redhat.com/browse/PROJQUAY-6577[PROJQUAY-6577], the {productname} Operator does not properly render customized Clair `config.yaml` files. As a result, the following procedure does not currently work.
14-
15-
Users must create the entire Clair configuration themselves, from the beginning, instead of relying on the Operator to populate the fields. To do this, following the instructions at link:https://access.redhat.com/solutions/7051718[Procedure to enable Clair scanning of images in disconnected environments].
16-
====
17-
1811
[id="clair-clairctl-standalone"]
1912
== Installing the clairctl command line utility tool for a self-managed Clair deployment on {ocp}
2013

modules/clair-clairctl.adoc

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,6 @@
88

99
Use the following procedures to set up an {ocp} provisioned Clair pod in a disconnected {ocp} cluster.
1010

11-
[IMPORTANT]
12-
====
13-
Due to known issue link:https://issues.redhat.com/browse/PROJQUAY-6577[PROJQUAY-6577], the {productname} Operator does not properly render customized Clair `config.yaml` files. As a result, the following procedure does not currently work.
14-
15-
Users must create the entire Clair configuration themselves, from the beginning, instead of relying on the Operator to populate the fields. To do this, following the instructions at link:https://access.redhat.com/solutions/7051718[Procedure to enable Clair scanning of images in disconnected environments].
16-
====
17-
1811
[id="clair-clairctl-ocp"]
1912
== Installing the clairctl command line utility tool for {ocp} deployments
2013

modules/clair-disconnected.adoc

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,6 @@ Clair uses a set of components called _updaters_ to handle the fetching and pars
1515

1616
Use this guide to deploy Clair in a disconnected environment.
1717

18-
[IMPORTANT]
19-
====
20-
Due to known issue link:https://issues.redhat.com/browse/PROJQUAY-6577[PROJQUAY-6577], the {productname} Operator does not properly render customized Clair `config.yaml` files. As a result, the following procedure does not currently work.
21-
22-
Users must create the entire Clair configuration themselves, from the beginning, instead of relying on the Operator to populate the fields. To do this, following the instructions at link:https://access.redhat.com/solutions/7051718[Procedure to enable Clair scanning of images in disconnected environments].
23-
====
24-
2518
[NOTE]
2619
====
2720
Currently, Clair enrichment data is CVSS data. Enrichment data is currently unsupported in disconnected environments.

0 commit comments

Comments
 (0)