Cannot start in just services mode in Equinix Metal

[deitch]

Cannot start in just services mode in Equinix Metal

[deitch]

Update: my CCM was misconfigured. I got that right, but now I am seeing kube-vip with different errors.

I have 3 control plane and 3 worker nodes. On all nodes:

time="2024-04-16T14:44:39Z" level=info msg="Starting kube-vip.io [v0.7.2]"
time="2024-04-16T14:44:39Z" level=info msg="namespace [kube-system], Mode: [BGP], Features(s): Control Plane:[false], Services:[true]"
time="2024-04-16T14:44:39Z" level=warning msg="the status of the interface lo is unknown. Ensure your interface is ready to accept traffic, if so you can safely ignore this message"
time="2024-04-16T14:44:39Z" level=info msg="prometheus HTTP server started"
time="2024-04-16T14:44:39Z" level=info msg="Kube-Vip is waiting for annotation prefix [metal.equinix.com] to be present on this node"
time="2024-04-16T14:44:39Z" level=info msg="Starting Kube-vip Manager with the BGP engine"
time="2024-04-16T14:44:39Z" level=error msg="you must export PACKET_AUTH_TOKEN"
time="2024-04-16T14:44:39Z" level=info msg="Looking up the BGP configuration from Equinix Metal"
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x1e0 pc=0x16f7aa1]

goroutine 1 [running]:
github.com/kube-vip/kube-vip/pkg/equinixmetal.findProject({0x0, 0x0}, 0x0)
	/src/pkg/equinixmetal/utils.go:14 +0xa1
github.com/kube-vip/kube-vip/pkg/equinixmetal.BGPLookup(0x0, 0x32d9c00)
	/src/pkg/equinixmetal/bgp.go:16 +0x56
github.com/kube-vip/kube-vip/pkg/manager.(*Manager).startBGP(0xc0001ea930)
	/src/pkg/manager/manager_bgp.go:46 +0x211
github.com/kube-vip/kube-vip/pkg/manager.(*Manager).Start(0xc0001ea930)
	/src/pkg/manager/manager.go:167 +0x2e5
github.com/kube-vip/kube-vip/cmd.init.func12(0x32bc9c0, {0x1fa6201?, 0x4?, 0x1fa6205?})
	/src/cmd/kube-vip.go:362 +0xa9b
github.com/spf13/cobra.(*Command).execute(0x32bc9c0, {0x333a840, 0x0, 0x0})
	/go/pkg/mod/github.com/spf13/[email protected]/command.go:987 +0xab1
github.com/spf13/cobra.(*Command).ExecuteC(0x32bbe40)
	/go/pkg/mod/github.com/spf13/[email protected]/command.go:1115 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
	/go/pkg/mod/github.com/spf13/[email protected]/command.go:1039
github.com/kube-vip/kube-vip/cmd.Execute()
	/src/cmd/kube-vip.go:173 +0x1a
main.main()
	/src/main.go:17 +0x85

[deitch]

And updated manifest:

apiVersion: apps/v1
kind: DaemonSet
metadata:
  creationTimestamp: null
  labels:
    app.kubernetes.io/name: kube-vip-ds
    app.kubernetes.io/version: v0.7.2
  name: kube-vip-ds
  namespace: kube-system
spec:
  selector:
    matchLabels:
      app.kubernetes.io/name: kube-vip-ds
  template:
    metadata:
      creationTimestamp: null
      labels:
        app.kubernetes.io/name: kube-vip-ds
        app.kubernetes.io/version: v0.7.2
    spec:
      containers:
      - args:
        - manager
        env:
        - name: vip_arp
          value: "false"
        - name: port
          value: "6443"
        - name: vip_interface
          value: lo
        - name: vip_cidr
          value: "32"
        - name: dns_mode
          value: first
        - name: svc_enable
          value: "true"
        - name: svc_leasename
          value: plndr-svcs-lock
        - name: annotation
          value: metal.equinix.com
        - name: vip_packet
          value: "true"
        - name: vip_packetproject
        - name: vip_packetprojectid
        - name: PACKET_AUTH_TOKEN
        - name: bgp_enable
          value: "true"
        - name: vip_address
        - name: prometheus_server
          value: :2112
        image: ghcr.io/kube-vip/kube-vip:v0.7.2
        imagePullPolicy: Always
        name: kube-vip
        resources: {}
        securityContext:
          capabilities:
            add:
            - NET_ADMIN
            - NET_RAW
      hostNetwork: true
      serviceAccountName: kube-vip
  updateStrategy: {}
status:
  currentNumberScheduled: 0
  desiredNumberScheduled: 0
  numberMisscheduled: 0
  numberReady: 0

[deitch]

Oh, I think I got it. I provided --metal, but also --annotations, so it tried to do both, including getting the API, but I didn't provide a key.

I think I can close this.

[thebsdbox]

Just reopening this so I can make sure the panic is fixed.