This message was deleted.
# k3s
a
This message was deleted.
c
can you share what the manifest looks like? with as little redaction as possible
q
Not redacted at all, only changed some names. Original names are very similar 🙂
c
K3s actually uses a helper library to do the application: https://github.com/rancher/wrangler/blob/master/pkg/apply/desiredset.go It does use object names and namespaces to determine what needs to change. I’m not aware of anything that’s changed over there recently that would have broken use of resources with only the generateName set, and no name, but I wouldnt be surprised if it was never tested to work properly and either worked unreliably or was unintentionally regressed at some point.
if you have a moment, please create an issue in the K3s repo so that we can track it
that might be a tricky case to handle properly, given that it uses namespace and names as keys to track objects
q
I copied this runbook from the previously mentioned cluster, but I might not have had more than one service account at a time in that cluster, which would explain how it has worked then and not now. I can't remember why I needed
generateName
either, so I'll just use plain names for now. I'll create an issue for it anyway. Should I create it on the wrangler repo, or on k3s?
I had a feeling it would be something like that, it smelled like that kind of problem 😄
c
k3s
👍 1
at the very least we can document it
q
I guess this could hit any kind of resource, not just Secrets, since generateName is possible on all resources afaik ...
c
yep, any resource that supports GenerateName (which is all of them I think)