You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Much like v2plugin and netplugin binary tarball, netplugin artifacts for k8s container should be differentiated by SHA and available through dockerd so the contiv installer can execute the netplugin build for the container against any branch, which allows testing of any PR in CI
[CNTV-183] created by chris.plock
The text was updated successfully, but these errors were encountered:
the linked ticket
GH-26
Open
is the driver for this ticket. I think the netplugin docker image is probably the "netplugin artifact" that is needed, I can flesh the ticket out more when my focus can shift to this ticket and I've spent a little time with a k8s cluster.
netplugin/vagrant/k8s/Vagrantfile grabs netctl from a downloaded release version, that needs updating
install/k8s/contiv/contiv.yaml, contiv_devtest.yaml, and contiv_aci.yaml need to be updated to support passing in the container name, and need to make sure it's pulling from local dockerd
we'll need to build the container and push it based on branch build
I'm not sure how CI is getting the right container yet
#31
Much like v2plugin and netplugin binary tarball, netplugin artifacts for k8s container should be differentiated by SHA and available through dockerd so the contiv installer can execute the netplugin build for the container against any branch, which allows testing of any PR in CI
[CNTV-183] created by chris.plockThe text was updated successfully, but these errors were encountered: