Skip to content

Commit 510e771

Browse files
committed
Update docs
1 parent 2be11ff commit 510e771

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/Images.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ The Splunk Operator requires these docker images to be present or available to y
55
* `splunk/splunk-operator`: The Splunk Operator image built by this repository or the [official release](https://hub.docker.com/r/splunk/splunk-operator)
66
* `splunk/splunk:<version>`: The [Splunk Enterprise image](https://github.com/splunk/docker-splunk)
77

8-
All of these images are publicly available, and published on [Docker Hub](https://hub.docker.com/). Starting with release 2.7.2, the base image for the released image is registry.access.redhat.com/ubi8/ubi-minimal, which minimizes security risks and reduces unneeded packages in the image. A released image based on the distroless base image is also available under the `-distroless` suffix tag on Docker Hub.
8+
All of these images are publicly available, and published on [Docker Hub](https://hub.docker.com/). Starting with release 2.8.0, the base image for the released image is registry.access.redhat.com/ubi8/ubi-minimal, which minimizes security risks and reduces unneeded packages in the image. A released image based on the distroless base image is also available under the `-distroless` suffix tag on Docker Hub.
99

1010
If your cluster does not have access to pull directly from Docker Hub, you will need to manually download and push these images to an accessible registry. You will also need to specify the location of these images by using an environment variable passed to the Operator, or by adding additional `spec` parameters to your
1111
custom resource definition.

0 commit comments

Comments
 (0)