From 82096746bba066e71a6418d7be859fa91ddc03f2 Mon Sep 17 00:00:00 2001 From: jiangjiang <86391540+googs1025@users.noreply.github.com> Date: Wed, 3 Apr 2024 01:14:11 +0800 Subject: [PATCH] fix for importer readme (#1932) --- cmd/importer/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/cmd/importer/README.md b/cmd/importer/README.md index 94eaf8651b..89f27ff371 100644 --- a/cmd/importer/README.md +++ b/cmd/importer/README.md @@ -31,15 +31,15 @@ The importer will perform following checks: - The LocalQueues involved in the import are using an existing ClusterQueue. - The ClusterQueues involved have at least one ResourceGroup using an existing ResourceFlavor. This ResourceFlavor is used when the importer creates the admission for the created workloads. -The are two ways the mapping from a pod to a LocalQueue can be specified: +There are two ways the mapping from a pod to a LocalQueue can be specified: #### Simple mapping -It's done by specifying a label name and any number of = a command line arguments eg. `--queuelabel=src.lbl --queuemapping=src-val=user-queue,src-val2=user-queue2`. +It's done by specifying a label name and any number of = a command line arguments e.g. `--queuelabel=src.lbl --queuemapping=src-val=user-queue,src-val2=user-queue2`. #### Advanced mapping -It's done providing an yaml mapping file name as `--queuemapping-file` argument, it's expected content being: +It's done providing a yaml mapping file name as `--queuemapping-file` argument, it's expected content being: ```yaml - match: