Giter VIP home page Giter VIP logo

Comments (7)

kvaps avatar kvaps commented on June 2, 2024 1

Thank you for the report!
Some old apiVersions was removed in Kubernetes 1.16 release.
I've updated bridget.yaml to use newer apiVersions, so now it should work on 1.16 without any problems.

from bridget.

kvaps avatar kvaps commented on June 2, 2024 1

Thank you guys, I could reproduce this issue, problem was in tolerations, fixed in 121b1a9

from bridget.

jfranzoy avatar jfranzoy commented on June 2, 2024

Hi kvaps. I tried the new version, and it did not raise an error in 'create' cmd, but no daemonSet appears to be running.

It looks like I've missed some prerequisite, or something. In case you can help me, which I hope, I give more details about my deployment.

I am trying to setup a Proof of Concept kubernetes using flat networking. I have one laptop with OpenSuse installed. It has one nic 192.168.1.10 (DHCP). Inside it I have two Ubuntu VMs: kube-master and kube-worker0. Both VMs has its VNICs bridged to the phisical NIC of the laptop. kube-master has one VNIC 192.168.1.100 (static), kube-worker0 has three VNICs 192.168.1.101, 192.168.1.102 and 192.168.1.103 (all static). I've verified that there is ping from kube-master to all VNICs of kube-worker0

I run kubeadm init in kube-master and kubeadm join in kube-worker. I create bridget from bridget.yaml, no error was issued, but the cluster remains without pod networking.

Thanks in advance

Details: in https://pastebin.com/btK0t2ej

from bridget.

kvaps avatar kvaps commented on June 2, 2024

Hi @jfranzoy , please provide output of kubectl describe daemonset -n kube-system bridget

from bridget.

jfranzoy avatar jfranzoy commented on June 2, 2024

Thanks kvaps. Here you are

ubuntu@kube-master:~$ sudo kubectl describe daemonset -n kube-system bridget

Name:           bridget
Selector:       app=bridget
Node-Selector:  <none>
Labels:         <none>
Annotations:    deprecated.daemonset.template.generation: 1
Desired Number of Nodes Scheduled: 0
Current Number of Nodes Scheduled: 0
Number of Nodes Scheduled with Up-to-date Pods: 0
Number of Nodes Scheduled with Available Pods: 0
Number of Nodes Misscheduled: 0
Pods Status:  0 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:           app=bridget
  Service Account:  bridget
  Containers:
   bridget:
    Image:      kvaps/bridget:v1.0.1
    Port:       <none>
    Host Port:  <none>
    Environment:
      BRIDGE:       br0
      IFACE:        enp1s0
      MTU:          1400
      POD_NETWORK:  10.221.0.0/16
      NODE_NAME:     (v1:spec.nodeName)
    Mounts:
      /etc/cni/net.d from cni-cfg (rw)
  Volumes:
   cni-cfg:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/cni/net.d
    HostPathType:  
Events:            <none>

from bridget.

kvaps avatar kvaps commented on June 2, 2024

from bridget.

mirceaIordache avatar mirceaIordache commented on June 2, 2024

Hi there, can confirm that no networking occurs. Attached is output from

kubectl describe daemonset -n kube-system bridget

Name:           bridget
Selector:       app=bridget
Node-Selector:  <none>
Labels:         <none>
Annotations:    deprecated.daemonset.template.generation: 1
Desired Number of Nodes Scheduled: 0
Current Number of Nodes Scheduled: 0
Number of Nodes Scheduled with Up-to-date Pods: 0
Number of Nodes Scheduled with Available Pods: 0
Number of Nodes Misscheduled: 0
Pods Status:  0 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:           app=bridget
  Service Account:  bridget
  Containers:
   bridget:
    Image:      kvaps/bridget:v1.0.1
    Port:       <none>
    Host Port:  <none>
    Environment:
      BRIDGE:       br0
      VLAN:         4
      IFACE:        enp1s0f1
      MTU:          1500
      POD_NETWORK:  10.244.0.0/16
      NODE_NAME:     (v1:spec.nodeName)
    Mounts:
      /etc/cni/net.d from cni-cfg (rw)
  Volumes:
   cni-cfg:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/cni/net.d
    HostPathType:  
Events:            <none>

Problem is, the cluster is freshly created (and bridget freshly loaded).

EDIT: Digging through this a bit further, it seems that bridget pods aren't running, even if the daemonset created.

kubectl -n kube-system get pod -l app=bridget -o wide

No resources found in kube-system namespace.

from bridget.

Related Issues (5)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.