Change the wording for null values
This commit is contained in:
		
							parent
							
								
									fce75ca366
								
							
						
					
					
						commit
						df05c57da8
					
				|  | @ -75,7 +75,7 @@ flags. | |||
| 
 | ||||
| Manifest roles are defined as a dictionary, with a role name as a key and a | ||||
| list of role options as a value. For a role without any options it is best to supply the empty | ||||
| list `[]`. It is also possible to leave this field empty as in our example manifests, but in certain cases such empty field may removed by Kubernetes [due to the implicit `null` value it gets](https://kubernetes.io/docs/concepts/overview/object-management-kubectl/declarative-config/#how-apply-calculates-differences-and-merges-changes).  | ||||
| list `[]`. It is also possible to leave this field empty as in our example manifests, but in certain cases such empty field may removed by Kubernetes [due to the `null` value it gets](https://kubernetes.io/docs/concepts/overview/object-management-kubectl/declarative-config/#how-apply-calculates-differences-and-merges-changes) (`foobar_user:` is equivalent to `foobar_user: null`).  | ||||
| 
 | ||||
| The operator accepts the following options:  `superuser`, `inherit`, `login`, | ||||
| `nologin`, `createrole`, `createdb`, `replication`, `bypassrls`. | ||||
|  |  | |||
		Loading…
	
		Reference in New Issue