Open stanislav-zaprudskiy opened 5 years ago
This would make the chart more resilient to future Kubernetes API updates, which might be incompatible/incomplete with current defaults.
On top, cpu value must be a string, not an number according to schema specs (check https://kubernetesjsonschema.dev/ out).
cpu
At the end, it seems to be a common practice for all other charts.
This would make the chart more resilient to future Kubernetes API updates, which might be incompatible/incomplete with current defaults.
On top,
cpuvalue must be a string, not an number according to schema specs (check https://kubernetesjsonschema.dev/ out).At the end, it seems to be a common practice for all other charts.