Rename shmVolume to enableShmVolume

docs/reference/cluster_manifest.md

@@ -97,17 +97,17 @@ Those are parameters grouped directly under  the `spec` key in the manifest.
    is taken from the `pod_priority_class_name` operator parameter, if not set
    then the default priority class is taken. The priority class itself must be defined in advance.
 
-* **shmVolume**
+* **enableShmVolume**
   Start a database pod without limitations on shm memory. By default docker
   limit `/dev/shm` to `64M` (see e.g. the [docker
   issue](https://github.com/docker-library/postgres/issues/416), which could be
   not enough if PostgreSQL uses parallel workers heavily. If this option is
   present and value is `true`, to the target database pod will be mounted a new
   tmpfs volume to remove this limitation. If it's not present, the decision
   about mounting a volume will be made based on operator configuration
-  (`shm_volume`, which is `true` by default). It it's present and value is
-  `false`, then no volume will be mounted no matter how operator was configured
-  (so you can override the operator configuration).
+  (`enable_shm_volume`, which is `true` by default). It it's present and value
+  is `false`, then no volume will be mounted no matter how operator was
+  configured (so you can override the operator configuration).
 
 ## Postgres parameters
 

docs/reference/operator_parameters.md

@@ -224,12 +224,12 @@ CRD-based configuration.
 * **set_memory_request_to_limit**
   Set `memory_request` to `memory_limit` for all Postgres clusters (the default value is also increased). This prevents certain cases of memory overcommitment at the cost of overprovisioning memory and potential scheduling problems for containers with high memory limits due to the lack of memory on Kubernetes cluster nodes. This affects all containers (Postgres, Scalyr sidecar, and other sidecars). The default is `false`.
 
-* **shm_volume**
+* **enable_shm_volume**
   Instruct operator to start any new database pod without limitations on shm
   memory. If this option is enabled, to the target database pod will be mounted
   a new tmpfs volume to remove shm memory limitation (see e.g. the [docker
   issue](https://github.com/docker-library/postgres/issues/416)). This option
-  is global for an operator object, and can be overwritten by `shmVolume`
+  is global for an operator object, and can be overwritten by `enableShmVolume`
   parameter from Postgres manifest. The default is `true`
 
 ## Operator timeouts

manifests/complete-postgres-manifest.yaml

@@ -19,7 +19,7 @@ spec:
   databases:
     foo: zalando
 #Expert section
-  shmVolume: true
+  enableShmVolume: true
   postgresql:
     version: "10"
     parameters:

pkg/apis/acid.zalan.do/v1/postgresql_type.go

@@ -51,7 +51,7 @@ type PostgresSpec struct {
 	Tolerations          []v1.Toleration      `json:"tolerations,omitempty"`
 	Sidecars             []Sidecar            `json:"sidecars,omitempty"`
 	PodPriorityClassName string               `json:"pod_priority_class_name,omitempty"`
-	ShmVolume            *bool                `json:"shmVolume,omitempty"`
+	ShmVolume            *bool                `json:"enableShmVolume,omitempty"`
 }
 
 // +k8s:deepcopy-gen:interfaces=k8s.io/apimachinery/pkg/runtime.Object

pkg/util/config/config.go

@@ -38,7 +38,7 @@ type Resources struct {
 	NodeReadinessLabel      map[string]string `name:"node_readiness_label" default:""`
 	MaxInstances            int32             `name:"max_instances" default:"-1"`
 	MinInstances            int32             `name:"min_instances" default:"-1"`
-	ShmVolume               bool              `name:"shm_volume" default:"true"`
+	ShmVolume               bool              `name:"enable_shm_volume" default:"true"`
 }
 
 // Auth describes authentication specific configuration parameters