Closed TechDufus closed 7 months ago
As a workaround, you can click on "edit YAML", and remove the empty settings.memory
key.
This would be a good moment to revisit questions-ui.yml and add support for settings.memory.ignoreValues
and settings.cpu.ignoreValues
.
For testing, it may be useful to create an empty chart with the needed questions-ui.yml. If not, one needs to publish a fork of the policy into artifacthub.
Hi, pls how did you generate YAML in your description? There was a bug in previous UI versions, but it was fixed. When I create policy in UI extension v1.4.0 and switch to Edit YAML tab, I get this:
# Filled only CPU values in policy settings tab
settings:
cpu:
defaultRequest: '100'
defaultLimit: '100'
maxLimit: '100'
memory:
defaultRequest: ''
defaultLimit: ''
maxLimit: ''
I can't reproduce getting memory: {}
in YAML from UI 1.4.0.
I manually added your yaml and the policy is working.. I can no longer reproduce getting my initial issue either... 🤣
one and done I suppose.
Is there an existing issue for this?
Current Behavior
When deploying with the following settings via the UI:
I get this error from the new policy server trying to spin up:
Expected Behavior
I should be able to ONLY set CPU settings via the Rancher / Kubewarden UI and have the policy server successfully redeploy.
Steps To Reproduce
Steps provided above.
Environment
Anything else?
No response