This message was deleted.
# fleet
a
This message was deleted.
b
You need to create the namespace explicitly with a k8s resource
f
isn't that the whole point of having
defaultNamespace
defined in
fleet.yaml
that fleet creates the namespace for you
b
no. that just fills in the
namespace
field when it's not already specified in the manifests
f
or is that only when used together with helm?
and what about the
namespace
directive in
fleet.yaml
?
b
i think that enforces namespace, but not sure about auto-creating it
fwiw, on a dev cluster, I'm seeing defaultNamespace result in created namespaces
f
yes, I see that same behaviour sometimes
but not always, and I just can't seem to understand why
b
strange
fleet is not inspiring confidence
and i can't seem to get anyone from rancher to reply
well, they do in #k3s, but not here
f
also when adding PSS labels on the
ns
it sometimes gets into a loop where ns objects gets updated again and again
I have a support case open with SUSE. They should provide an answer beginning next week, but I think this affects more users than they might know
b
Yeaaaa... you should see my bug above
I can't get the official rancher addons to stop creating PSPs when run through fleet
fleet seems to completely remove
global.cattle.psp.enabled
every time I set it in the values. I have no idea wtf
f
there is a doc about that
πŸ‘€ 1
let me look it up
πŸ™Œ 1
b
haha dang i thought this was something new. Yeah its this doc that got me to set these values, but I swear, fleet just completely disregards the value, making this support article completely worthless
f
and I see you found the rendered helm chart in the secret right
b
but there doesn't seem to be a trace for why this is happening. All I can see is that the bundledeployment has a record of me setting
global.cattle.psp.enabled: false
, yet the helm json secret with all the deployment details shows that fleet didn't pass that one set on to the chart
it's extremely strange
f
which version of the helm charts are you using?
and which version of k8s are you working on?
any conditional in the helm chart?
b
v1.24.17+k3s1 and 102.0.2+up40.1.2
f
did you disable psp support already?
afk now - need food
b
did you disable psp support already
i haven't heard of a way of toggling it in any of the stuff I've read
yeah sorry had to deal with some contractors
b
well slap me with a wet noodle
πŸ˜‚ 1
i have no idea why, but after fully deleting the bundle and re-pushing, it's now correct. no psps
πŸ‘ 1
f
Glad it’s fixed πŸ˜‰
b
I think the deeper issue turns out to be that fleet holds on to values, even if the git repo has new contents. I'm now seeing this with another chart 😭
f
Ok, so I found the issue on my side. I was referencing the wrong path from my GitRepo so it wasn't looking at the fleet.yaml where I added the labels. 😞
b
no kidding! well glad you found it at least