Merge pull request #46 from IBM/bha-priorityClass

Add priorityClassName to node pods

Author: Bhagyashreek8

Makefile

@@ -131,10 +131,18 @@ run: manifests generate fmt vet ## Run a controller from your host.
 docker-build: test ## Build docker image with the manager.
 	docker build -t ${IMG} . --platform linux/amd64
 
+.PHONY: podman-build
+podman-build: test ## Build docker image with the manager.
+	podman build -t ${IMG} . --platform linux/amd64
+
 .PHONY: docker-push
 docker-push: ## Push docker image with the manager.
 	docker push ${IMG}
 
+.PHONY: podman-push
+podman-push: ## Push docker image with the manager.
+	podman push ${IMG}
+
 # PLATFORMS defines the target platforms for  the manager image be build to provide support to multiple
 # architectures. (i.e. make docker-buildx IMG=myregistry/mypoperator:0.0.1). To use this option you need to:
 # - able to use docker buildx . More info: https://docs.docker.com/build/buildx/

README.md

@@ -1,8 +1,9 @@
 # ibm-object-csi-driver-operator
-// TODO(user): Add simple overview of use/purpose
+A CSI based object storage plugin with dynamic bucket provisioning and plugable mounters, like rclone, s3fs and other. The plugin should seamlessly work in IBM, AWS and GCP platforms.
 
 ## Description
-// TODO(user): An in-depth paragraph about your project and overview of use
+ibm-object-csi-driver-operator is a user defined storage controller extending K8S capability to manage COS Buckets as PV/PVC resource.
+This is designed and developed as per CSI specification. It enables the application workloads to dynamically provision volumes backed by COS buckets as per PVC/PV framework. As of now it supports s3fs & rclone mounters to mount the bucket as a fuse FileSystem inside the POD. 
 
 ## Getting Started
 You’ll need a Kubernetes cluster to run against. You can use [KIND](https://sigs.k8s.io/kind) to get a local cluster for testing, or run against a remote cluster.
@@ -13,13 +14,13 @@ You’ll need a Kubernetes cluster to run against. You can use [KIND](https://si
 1. Build and push your image to the location specified by `IMG`:
 
 ```sh
-make docker-build docker-push IMG=<some-registry>/ibm-object-csi-driver-operator:tag
+make docker-build docker-push IMG=<image-registry>/ibm-object-csi-driver-operator:<image-tag>
 ```
 
 2. Deploy the controller to the cluster with the image specified by `IMG`:
 
 ```sh
-make deploy IMG=<some-registry>/ibm-object-csi-driver-operator:tag
+make deploy IMG=<image-registry>/ibm-object-csi-driver-operator:<image-tag>
 ```
 
 3. Install Instances of Custom Resources:

config/manager/kustomization.yaml

@@ -5,7 +5,7 @@ kind: Kustomization
 images:
 - name: controller
   newName: icr.io/ibm/ibm-object-csi-driver-operator
-  newTag: v0.1.8
+  newTag: v0.1.11
 commonLabels:
   app.kubernetes.io/managed-by: kustomize
   app.kubernetes.io/part-of: ibm-object-csi-driver-operator

controllers/constants/constants.go

@@ -71,6 +71,7 @@ const (
 	CSIControllerSCCClusterRoleBinding    = "controller-scc-clusterrolebinding"
 	CSINodeSCCClusterRole                 = "node-scc-clusterrole"
 	CSINodeSCCClusterRoleBinding          = "node-scc-clusterrolebinding"
+	CSINodePriorityClassName              = "system-node-critical"
 
 	ResourceReqLimitsConfigMap = "cos-csi-driver-configmap"
 	ObjectCSIDriver            = "ibm-object-csi"

controllers/syncer/csi_node.go

@@ -95,6 +95,7 @@ func (s *csiNodeSyncer) ensurePodSpec() corev1.PodSpec {
 			RunAsUser:    func(uid int64) *int64 { return &uid }(2121),
 		},
 		ServiceAccountName: constants.GetResourceName(constants.CSINodeServiceAccount),
+		PriorityClassName:  constants.CSINodePriorityClassName,
 	}
 }