Hide Forgot
1. Proposed title of this feature request Integrate kubernetes objects like Jobs, PetSets and DemonSets with imagestreams 3. What is the nature and description of the request? Based on the following Trello ticket: https://trello.com/c/Q86cBR3R/688-daemonset-wrapper-like-deploymentconfig# We suggest to implement such a wrapper also for jobs and petsets. 4. Why does the customer need this? (List the business requirements here) So that I can build an image and have a new DaemonSet deployed with it 5. How would the customer like to achieve this? (List the functional requirements here) 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? https://trello.com/c/Q86cBR3R/688-daemonset-wrapper-like-deploymentconfig# 10. List any affected packages or components.
(In reply to Brendan Mchugh from comment #1) > 1. Proposed title of this feature request > Integrate kubernetes objects like Jobs, PetSets and DemonSets with > imagestreams > > 3. What is the nature and description of the request? > > Based on the following Trello ticket: > https://trello.com/c/Q86cBR3R/688-daemonset-wrapper-like-deploymentconfig# > > We suggest to implement such a wrapper also for jobs and petsets. > > 4. Why does the customer need this? (List the business requirements here) > So that I can build an image and have a new DaemonSet deployed with it > > 5. How would the customer like to achieve this? (List the functional > requirements here) > > > 6. For each functional requirement listed, specify how Red Hat and the > customer can test to confirm the requirement is successfully implemented. > > 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? > https://trello.com/c/Q86cBR3R/688-daemonset-wrapper-like-deploymentconfig# > > 10. List any affected packages or components. The workaround for now is to use the `oc set image` command that should resolve the image stream for all of these objects. This has to be done manually currently or by some pipeline process that will automatically update the image when a new image is available. The design of how this should be done natively (similar to DeploymentConfig) is still to be done.
*** Bug 1450717 has been marked as a duplicate of this bug. ***
1. Proposed title of this feature request Job container images sourced from an image stream 3. What is the nature and description of the request? When executed, a job constructs a pod definition that runs the docker file listed at job.spec.template.spec.containers.image. Ideally we would like to just specify and image stream when adding the job, and have that automatically map to a docker image. 4. Why does the customer need this? (List the business requirements here) We have a couple of processing jobs that are based off images produced by build configs... having to manually configure jobs with the output of an image stream is a pain and is error prone. Why not use Deployment-config with PodRestart set to "only on failure"? DeploymentConfigs conceptually are for controlling a number of pods that are always supposed to be running. Using a deployment config instead of a job for job processing means you are left with a growing number of single-shot deployment configs cluttering the namespace. Also we did use deployment configs for this purpose until somebody accidentally re-deployed an older job, corrupting state stored on persistent storage and causing a reasonably amount of work to fix up. 5. How would the customer like to achieve this? (List the functional requirements here) Be able to specify an images stream as part of the container spec when specifying a job - Upon creation of the job object, that image stream should be used to map to the current docker image for that image stream, and that value placed at job.spec.template.spec.containers[x].image. I am *NOT* suggesting that jobs should redeploy with an updated docker spec when an image stream updates. The mapping should only occur once - when the job is created. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Creating a job that mentions an image stream should automatically change job.spec.template.spec.containers[x].image to point to the current image stream docker image 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? Not aware 8. What information can you provide around timeframes and urgency? Average 9. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? Next version would be nice. 10. List any affected packages or components. Kubernetes, bc, dc 11. Would the customer be able to assist in testing this functionality if implemented? We can assist with testing
This bug has been identified as a dated (created more than 3 months ago) bug. This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, as it is currently not part of the products immediate priorities. Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.