Do you need declarative node network configuration driven through Kubernetes API? No matter how you run your OpenShift environment, network management is one of those things that's hard to get right. In this episode, we look at the NMState and MetalLB operators which provide load-balancer implementation for bare metal Kubernetes clusters and a Kubernetes API for performing state-driven network configuration across the OpenShift Container Platform cluster's nodes. We'll cover using MetalLB L3/BGP mode and how the NMState Operator provides users with the functionality to configure various network interface types, DNS, and routing on cluster nodes and look at how the daemons on the cluster nodes periodically report on the state of each node's network interfaces to the API server. So join us to learn more about MetalLB L3/BGP and the NMState library.
Want to learn more?
[ Ссылка ]
[ Ссылка ]
Try Red Hat OpenShift: [ Ссылка ]
Follow us:
Andrew Sullivan [ Ссылка ]
Jonathan Rickard [ Ссылка ]
OpenShift [ Ссылка ]
Subscribe to Red Hat's YouTube channel: [ Ссылка ]
About Ask an OpenShift Admin:
Do you have questions? We want to answer them! Every Wednesday at 11am ET, hosts Andrew Sullivan and Jonathan Rickard sit down to answer your questions about Red Hat OpenShift.
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
OpenShift on redhat.com [ Ссылка ]
OpenShift on GitHub [ Ссылка ]
#RedHat #OpenShift #Kubernetes #ContainerPlatform
