OK, thanks for the pointers, I think we will eventually move to an OVN CNI
But for now I need to get this working.
On 06/08/2020 16:49, Girish Moodalbail wrote:
On Thu, Aug 6, 2020 at 8:23 AM Brendan Doyle <[email protected]
<mailto:[email protected]>> wrote:
On 06/08/2020 16:19, Girish Moodalbail wrote:
On Thu, Aug 6, 2020 at 7:36 AM Brendan Doyle
<[email protected] <mailto:[email protected]>> wrote:
OK thanks, perhaps Girish can comment, I thinking that the
steps are
|# Create OVN namespace, service accounts, ovnkube-db
headless service, configmap, and policies kubectl create -f
$HOME/work/src/github.com/ovn-org/ovn-kubernetes/dist/yaml/ovn-setup.yaml
<http://github.com/ovn-org/ovn-kubernetes/dist/yaml/ovn-setup.yaml>
# Run ovnkube-db deployment. kubectl apply -f
$HOME/work/src/github.com/ovn-org/ovn-kubernetes/dist/yaml/
<http://github.com/ovn-org/ovn-kubernetes/dist/yaml/>||ovnkube-db-raft.yaml #
Run ovnkube-master deployment.
kubectl create -f
$HOME/work/src/github.com/ovn-org/ovn-kubernetes/dist/yaml/ovnkube-master.yaml
<http://github.com/ovn-org/ovn-kubernetes/dist/yaml/ovnkube-master.yaml>
# Run ovnkube daemonset for nodes kubectl create -f
$HOME/work/src/github.com/ovn-org/ovn-kubernetes/dist/yaml/ovnkube-node.yaml
<http://github.com/ovn-org/ovn-kubernetes/dist/yaml/ovnkube-node.yaml>|
Yes, those are the steps to get OVN K8s CNI up and running with
OVN DB running in clustered mode.
However, you also say below
Note I don't want to replace flannel with OVN as the CNI, I just want to
run OVN central in a k8
StatefulSet, that use flannel as the CNI.
So, my question is - What are you trying to do? How are you
mixing Flannel and OVN DBs?
Do you want to run OVN DBs in clustered mode as a service (or K8s
application) using Flannel as the CNI for your K8s cluster?
Yes I want to use Flannel as the CNI, and just have the clustered
OVN DBs as a k8s Service. providing
a HA OVN Central for ovn-controllers on hypervisors in my network.
So it sounds like the above steps
won't work for me and I have to hand craft/modify the raft yaml to
start northd, but not use the
rest of the yamls ?
Providing Clustered OVN DBs as a service is not the goal of the
ovn-kubernetes project. However, you can re-use a lot of the project's
yamls and container entrypoint scripts to achieve what you want to do.
1. Apply the ovn-setup.yaml and ovnkube-db-raft.yaml like you captured
above
2. Edit the ovnkube-master.yaml to only have ovn-northd container and
nothing else and name it ovn-north.yaml. Apply this ovn-north.yaml.
3. Have all the ovn-controller instances in your network point to the
OVN SB DB instances. The OVN DB Pods run with hostNetwork set to
`true`, so they will not be on a flannel network and therefore will be
accessible from your hypervisors directly.
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
