Environment variable name USERNAME is likely to be in use already

[mickvangelderen]

The USERNAME variable defaults to kubernetes which is great except when it is defined by something else on your system. I'm using a fairly new installation of ubuntu 24.04 and something has defined USERNAME already to be the same as USER.

This caused generation to fail and I had to look into why. This not a good user experience. My suggested solution would be to prefixing the variable names so they end up being a bit more unique.

[brendandburns]

Happy to take a PR for this, perhaps GITHUB_USERNAME

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale