New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pod suffix is b0110ck5 #49543
Comments
@jamesawebb1
Note: Method 1 will trigger an email to the group. You can find the group list here and label list here. |
My first github (k8s) issue. I've no idea which SIG would cover this topic. /sig product-management |
/sig api-machinery |
Previously we removed vowels in #37225. We can 3xt3nd the idea with 0, 1 (can stand for |
/assign jamesawebb1 |
@jamesawebb1 Reassign to me if you do not want to contribute a PR. |
Automatic merge from submit-queue (batch tested with PRs 46685, 49863, 50098, 50070, 50096) Remove 0,1,3 from rand.String to avoid 'bad words' **What this PR does / why we need it**: Remove 0,1,3 from the runes to prevent accidental bad words profanity **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #49543 **Special notes for your reviewer**: /cc @mml @jamesawebb1 @spiffxp **Release note**: ```release-note Remove 0,1,3 from rand.String, to avoid 'bad words' ```
/kind feature
What happened:
In playing with the nginx ingress controller deployment, I noticed the following pod name:
nginx-ingress-controller-1449474453-c0ck5
I figure we should possibly put something in place to prevent accidental l33t profanity ;-).
What you expected to happen:
The following pod name:
nginx-ingress-controller-1449474453-r0ck5
The text was updated successfully, but these errors were encountered: