Skip to content
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

deployment config image = " " should use a different token #14659

Closed
derekwaynecarr opened this issue Jun 14, 2017 · 1 comment
Closed

deployment config image = " " should use a different token #14659

derekwaynecarr opened this issue Jun 14, 2017 · 1 comment
Assignees
Labels
component/build kind/bug Categorizes issue or PR as related to a bug. priority/P2

Comments

@derekwaynecarr
Copy link
Member

upstream i wanted to update validation of containers to check for image with leading and trailing whitespace as i found events where pods like this got in our production system.

it came to my attention that deployment config was using a pod template spec in this manner.

i would like us to consider transitioning to another replacement token or phrase that does not violate leading and trailing whitespace validation.

Version

latest

Steps To Reproduce

n/a

Current Result

n/a

Expected Result

pod spec templates with image that has leading or trailing white space should fail validation.

Additional Information

kubernetes/kubernetes#47491
kubernetes/kubernetes#47490

@derekwaynecarr derekwaynecarr changed the title deployment config should transition away from image = " " deployment config image = " " should use a different token Jun 14, 2017
@derekwaynecarr
Copy link
Member Author

for reference, this came to my attention when debugging events in prod cluster.

xyz   5s        7d        46927     mongoxyz   Pod       spec.containers{mongodb}                  Warning   InspectFailed   {kubelet ip-removed}   Failed to apply default image tag " ": couldn't parse image reference " ": invalid reference format

we should verify that the controller will ensure this never sends a pod spec with this type of image when creating the final pod. i have the upstream pr to verify that that wont be allowed to happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/build kind/bug Categorizes issue or PR as related to a bug. priority/P2
Projects
None yet
Development

No branches or pull requests

3 participants