add markdownlint make targets

.github/ISSUE_TEMPLATE/feature_request.md

@@ -8,7 +8,7 @@ about: Suggest an idea for this project
 
 What new functionality do you want?
 
-# Who is the end user and what is the use case where this feature will be valuable?
+## Who is the end user and what is the use case where this feature will be valuable? ##
 
 Who is going to use this feature and under what circumstances?
 

.github/workflows/lint.yaml

@@ -76,10 +76,8 @@ jobs:
     - uses: actions/checkout@v4
       with:
         fetch-depth: 1
-    - uses: DavidAnson/markdownlint-cli2-action@v19
-      with:
-        config: .markdownlint.yaml
-        globs: 'docs/*.md'
+    -  name: run markdownlint
+       run: make markdownlint
 
   shellcheck:
     name: Shellcheck

Makefile

@@ -134,16 +134,25 @@ test-e2e:
 	go test ./test/e2e/ -v -ginkgo.v
 
 
+MARKDOWNLINT_IMAGE = docker.io/davidanson/markdownlint-cli2:v0.17.1
+.PHONY: markdownlint
+markdownlint:
+	@$(CONTAINER_TOOL) run --platform linux/amd64 -v .\:/workdir\:z  $(MARKDOWNLINT_IMAGE) markdownlint-cli2 "**.md" "#vendor/**"  --config .markdownlint.yaml
+
+.PHONY: markdownlint-fix
+markdownlint-fix:
+	@$(CONTAINER_TOOL) run --platform linux/amd64 -v .\:/workdir\:z  $(MARKDOWNLINT_IMAGE) markdownlint-cli2 "**.md" "#vendor/**"  --config .markdownlint.yaml --fix
+
 
 .PHONY:	golangci-lint-fix
 golangci-lint-fix: $(GOLANGCI_LINT) ## Run the golangci-lint linter and perform fixes
 	@$(GOLANGCI_LINT) --config=.golangci.yml -verbose run --fix
 
 
 .PHONY: lint
-lint: golangci-lint ## Run various linters
+lint: golangci-lint markdownlint ## Run various linters
 .PHONY: lint-fix
-lint-fix: golangci-lint-fix ## run linters and perform fixes
+lint-fix: golangci-lint-fix markdownlint-fix## run linters and perform fixes
 
 ##@ Build
 

docs/design/hostNetwork.md

@@ -1,7 +1,7 @@
 # Enabling host networking for controller plugin pods
 
 By default, the Ceph-CSI controller plugins operate on the pod network
-but under some circumstances, like setups with a dedicated storage network, 
+but under some circumstances, like setups with a dedicated storage network,
 where the pod network cannot connect to the ceph cluster,
 it is necessary to run the Ceph-CSI controller plugin pods on the host network.
 

docs/design/logrotate.md

@@ -2,7 +2,7 @@
 
 Log rotation involves managing log files by controlling their size. This feature will be added to the CephCSI and csi-addons containers in the CephCSI node-plugin and controller-plugin pods. When logrotate is used, it will generate a log file at the host path and run the logrotator sidecar container in CephCSI pods. The logrotator sidecar container will then ensure that log files are rotated based on predefined settings.
 
-Logroate configuration, 
+Logroate configuration,
 
 `OperatorConfig CRD`:
 

docs/design/operator.md

@@ -358,8 +358,8 @@ status: {}
 
 The ClientProfileMapping CR contains a mapping between pairs of Ceph
 CSI client profiles. The information in this CR helps Ceph CSI identify
-peered configuration between different k8s cluster. This information is 
-utilized in the management and consumption of volumes in backup and 
+peered configuration between different k8s cluster. This information is
+utilized in the management and consumption of volumes in backup and
 DR scenarios
 
 ```yaml