From 75ef5474b783085718f1a02b9c75e791cb2d07cc Mon Sep 17 00:00:00 2001 From: Hemant Kumar Date: Tue, 2 Jul 2024 15:42:11 -0400 Subject: [PATCH] Update enhancements/storage/csi-driver-operator-merge.md Co-authored-by: Jonathan Dobson --- enhancements/storage/csi-driver-operator-merge.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/enhancements/storage/csi-driver-operator-merge.md b/enhancements/storage/csi-driver-operator-merge.md index af1d470807..3ec64e04c4 100644 --- a/enhancements/storage/csi-driver-operator-merge.md +++ b/enhancements/storage/csi-driver-operator-merge.md @@ -528,7 +528,7 @@ So in previous section we merely copied existing code from operator’s own repo But once your operator has been changed to conform to new code in csi-operator repo, You need to perform following additional steps: -1. Make sure that `Dockerfile.` at top of the `csi-operator` tree refers to new location of code and not older `legacy/` location.See example of existing Dockerfiles. +1. Make sure that `Dockerfile.` at top of the `csi-operator` tree refers to new location of code and not older `legacy/` location. See example of existing Dockerfiles. 2. After your changes to `csi-operator` are merged, you should remove the old location from cachito - https://github.com/openshift-eng/ocp-build-data/pull/4219 Please note the changes to `ocp-build-data`should be merged almost same time as changes into `csi-operator`'s Dockerfile are merged, otherwise we risk builds from breaking.