Describe the problem/challenge you have
Due to some preprocessing we're doing on rendered YAML files I discovered an issue with that process in combination with the helm-charts provided in this repository.
Is there a reason the fields shared and thinProvision of the LVMVolume resource are strings accepting yes/no instead of booleans?
This might be confusing when creating them manually as yes/no without quotes are automatically converted to booleans in YAML 1.1
Describe the solution you'd like
Change the type of the fields shared and thinProvision of the LVMVolume resource to boolean
Describe the problem/challenge you have Due to some preprocessing we're doing on rendered YAML files I discovered an issue with that process in combination with the helm-charts provided in this repository.
Is there a reason the fields
shared
andthinProvision
of theLVMVolume
resource are strings accepting yes/no instead of booleans? This might be confusing when creating them manually as yes/no without quotes are automatically converted to booleans in YAML 1.1Describe the solution you'd like Change the type of the fields
shared
andthinProvision
of theLVMVolume
resource to booleanEnvironment: