| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Kuryr CNI daemon is scalability improvement that moves watching K8s API
and VIF plugging into a separate entity called kuryr-daemon.
Kuryr-daemon will run in a container and serve requests from
kuryr-driver.
|
| |\
| |
| | |
Add readiness probe to kuryr controller pod
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This commits adds a readiness probe to the kuryr controller
when the kuryr ports pool functionality is enabled. This way
the controller will not be set as ready until all the pre-created
ports have been loaded into their respective pools and are ready
to be used by the pods.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Add external_svc_subnet field for k8s loadbalancer type service
in kuryr-kubernetes code support external service subnet
but openshift does not support yet
Signed-off-by: jihoon.o <jihoon.o@samsung.com>
|
| |/
|
|
|
|
|
|
| |
This commits enables the ports pool driver when deploying kuryr
networking on top of OpenShift in containers. It also exposes
some configuration options such as the maximum and minimum pool
sizes, as well as the bulk subports creation size and the time
between pools update actions.
|
|
|
This commit enables deploying Kuryr networking on top of OpenShift in
containers. kuryr-controller is a Deployment and kuryr-cni is deployed
as DaemonSet (container will drop all CNI configuration files).
Co-Authored-By: Antoni Segura Puimedon <celebdor@gmail.com>
|
