Merge pull request #235 from felipecruz91/feature/add-statefulset-support

Add support to StatefulSet

Author: Michael Sauter

.github/workflows/ci.yml

@@ -27,7 +27,7 @@ jobs:
           make lint
       -
         name: Setup OpenShift
-        uses: manusa/actions-setup-openshift@v1.1.0
+        uses: manusa/actions-setup-openshift@v1.1.2
         with:
           oc version: 'v3.11.0'
           enable: 'centos-imagestreams,persistent-volumes,registry,router'

CHANGELOG.md

@@ -2,6 +2,8 @@
 
 ## Unreleased
 
+- Add support for `StatefulSet` resources ([#235](https://github.com/opendevstack/tailor/pull/235)).
+
 ## [1.3.0] - 2020-11-13
 
 - Use `oc get` without `--export` flag, which has been removed in Kubernetes 1.19 ([#230](https://github.com/opendevstack/tailor/pull/230)).

README.md

@@ -158,7 +158,7 @@ If you are a Tailor user wanting to migrate to Helm, check out the [migration gu
 
 ### Tailor does not recognize a certain resource kind
 
-Tailor currently supports `BuildConfig`, `CronJob`, `Job`, `Deployment`, `DeploymentConfig`, `ImageStream`, `LimitRange`, `PersistentVolumeClaim`, `ResourceQuota`, `RoleBinding`, `Route`, `Secret`, `Service`, `ServiceAccount`, `Template`, `HorizontalPodAutoscaler`. Some resources like `Build`, `Event`, `ImageStreamImage`, `ImageStreamTag`, `PersistentVolume`, `Pod`, `ReplicationController` are not supported by design as they are created and managed automatically by OpenShift. If you want to control a resource with Tailor that is not supported yet, but would be suitable, please [open an issue](https://github.com/opendevstack/tailor/issues/new).
+Tailor currently supports `BuildConfig`, `CronJob`, `Job`, `Deployment`, `DeploymentConfig`, `ImageStream`, `LimitRange`, `PersistentVolumeClaim`, `ResourceQuota`, `RoleBinding`, `Route`, `Secret`, `Service`, `ServiceAccount`, `Template`, `HorizontalPodAutoscaler`, and `StatefulSet`. Some resources like `Build`, `Event`, `ImageStreamImage`, `ImageStreamTag`, `PersistentVolume`, `Pod`, `ReplicationController` are not supported by design as they are created and managed automatically by OpenShift. If you want to control a resource with Tailor that is not supported yet, but would be suitable, please [open an issue](https://github.com/opendevstack/tailor/issues/new).
 
 ### Why is it required to specify fields which have server defaults?
 

pkg/openshift/change.go

@@ -23,6 +23,7 @@ var (
 		"LimitRange":              "limitrange",
 		"ResourceQuota":           "quota",
 		"HorizontalPodAutoscaler": "hpa",
+		"StatefulSet":             "statefulset",
 	}
 )
 

pkg/openshift/changeset.go

@@ -24,11 +24,12 @@ var (
 		"Job":                     "j",
 		"ImageStream":             "k",
 		"BuildConfig":             "l",
-		"DeploymentConfig":        "m",
-		"Deployment":              "n",
-		"HorizontalPodAutoscaler": "o",
-		"Service":                 "p",
-		"Route":                   "q",
+		"StatefulSet":             "m",
+		"DeploymentConfig":        "n",
+		"Deployment":              "o",
+		"HorizontalPodAutoscaler": "p",
+		"Service":                 "q",
+		"Route":                   "r",
 	}
 )
 

pkg/openshift/filter.go

@@ -27,6 +27,7 @@ var availableKinds = []string{
 	"limitrange",
 	"quota",
 	"hpa",
+	"statefulset",
 }
 
 type ResourceFilter struct {

pkg/openshift/filter_test.go

@@ -83,6 +83,16 @@ func TestNewResourceFilter(t *testing.T) {
 		t.Errorf("Kinds incorrect, got: %v, want: %v.", actual, expected)
 	}
 
+	actual, err = NewResourceFilter("statefulset", "", []string{})
+	expected = &ResourceFilter{
+		Kinds: []string{"StatefulSet"},
+		Name:  "",
+		Label: "",
+	}
+	if err != nil || !reflect.DeepEqual(actual, expected) {
+		t.Errorf("Kinds incorrect, got: %v, want: %v.", actual, expected)
+	}
+
 }
 
 func TestSatisfiedBy(t *testing.T) {

pkg/openshift/item.go

@@ -80,6 +80,7 @@ var (
 		"resourcequota":         "ResourceQuota",
 		"quota":                 "ResourceQuota",
 		"hpa":                   "HorizontalPodAutoscaler",
+		"statefulset":           "StatefulSet",
 	}
 )