-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Remove nop container and image #715
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dicarlo2 If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
Good call @dicarlo2 ! Now that you mention it, we should actually be able to completely get rid of the nop container now that we're not using init containers for the steps! afaik the reason we had this container was b/c we needed to have at least one container to actually run a pod. now that we're using actual containers, we should be able to completely remove it! im happy to do this in 2 phases if you want @dicarlo2 , we could merge this first, then in another PR remove the container (and the code for the image even!) but if you want to go straight to removing the container + image entirely that'd be cool too :D |
@bobcatfish went ahead and removed the nop container/image entirely. I realized that the workaround I was thinking of doesn't actually require the nop container at all. |
@dicarlo2: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/hold This image might actually be useful long-term for managing sidecars - working on a small PoC to show how. (The tests failed anyways, but just in case someone retests and they pass) |
See #728 |
Changes
The
nop-image
argument describes it as"The container image run at the end of the build to log build success"
, however currently it just runs immediately on pod start. I'm guessing this is due to the initContainer -> container change.This PR adds the nop image to the steps so that the entrypointer can apply to the nop container. Critically, this is required for the sidecar workaround described here: #701 (comment).This PR removes the nop image/container since it is no longer necessary.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide
for more details.
Release Notes
No? I don't think the nop container was really part of the user facing API/contract.