| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Updating the CNI and plugins to 0.7.x series.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
Updating the cni plugins to match k8s and cri-o. We also filter out
the windows plugins, since they use a different build infrastructure
than the other variants .. and are not currently needed. This can
be revisted in the future as needed.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Updating the latest plugins.
We have to make some minor build adjustments, but otherwise, this is
a simple update.
We also drop the ptest build, since it is not used and is causing
build errors.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
| |
Many distros make a 'kubernetes-cni' package available. This is no
more than a binary extracted set of 'cni' plugins. We already have
'cni' available in the build system, so we make sure it rprovides
kubernetes-cni to keep conflicts and confusion at a minimum.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
|
Introducing the CNI framework to allow platforms such as
kubernetes + cri-o to use thm for networking configuration.
The networking plugins are installed, but are not configured
by default to create any specific networking interfaces, which
are the responsibility of the image and distribution.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
