-
Notifications
You must be signed in to change notification settings - Fork 27
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
Move publishing this container into an upstream build artifact. #4
Comments
+1 This would be great, as it's anyway now the default for upstream conformance testing. |
This does now live upstream but has not been released yet. https://github.com/kubernetes/kubernetes/tree/9c5cf3ccf77225fd38772a5a9162d6dc7f818d20/cluster/images/conformance Until we migrate to only using that image; I'm going to keep this open for tracking. |
vmware-tanzu/sonobuoy#617 would start phasing in the upstream release. It has been in since v1.13 (the previous comment was based on incorrect info). After a few more releases we should can remove the logic if we want. Shouldn't matter much either way though. Continuing to leave this in for tracking until we decide what to do with this repo. I suggest we archive it if we do not plan further releases. Any desired changes should be directed at the upstream. @stevesloka @timothysc agree to archiving this now that we know it is upstream and already being released routinely? If so, I will update the readme and finish closing out the issues as such. |
/cc @mml
The text was updated successfully, but these errors were encountered: