has anyone seen spurious `urn` name conflicts when...
# kubernetes
has anyone seen spurious
name conflicts when creating a brand new resource…where there DEFINITELY isn’t an existing resource with that name?
Are you creating this resource in some kind of function or loop that is created multiple times? Can you share the code, please?
hey @quiet-wolf-18467 - sorry about the wait. it turns out - you were absolutely right, this was because we used a constant name for resources created in a loop 🤦‍♂️ thank you!
😅 1