device-configs.yaml

# Device configuration files for the Cisco Virtual Kubelet (local / dev use).
#
# These files describe the DEVICE only.  Runtime settings (node name, kubeconfig,
# log level) are supplied via CLI flags or environment variables:
#
#   --nodename / VKUBELET_NODE_NAME      Kubernetes node name
#                                         (default: cisco-vk-<device-address>)
#   --config / -c                         Path to this file
#                                         (default: /etc/virtual-kubelet/config.yaml)
#   --kubeconfig / KUBECONFIG             Path to kubeconfig
#   --log-level / LOG_LEVEL               debug | info | warn | error
#
# Credentials:
#   device.password may be inlined for local development. In production use
#   VK_DEVICE_PASSWORD env var (takes precedence) or, in controller mode,
#   spec.credentialSecretRef on the CiscoDevice CR (see ciscodevice-cr.yaml).
#
# Driver-specific networking lives under the driver key (e.g. "xe:").

---
# Example 1: VirtualPortGroup with DHCP
device:
  driver: XE
  address: "192.168.1.100"
  port: 443
  username: admin
  # password: injected via VK_DEVICE_PASSWORD env var
  tls:
    enabled: true
    insecureSkipVerify: true
  xe:
    networking:
      interface:
        type: VirtualPortGroup
        virtualPortGroup:
          dhcp: true
          interface: "0"
          guestInterface: 0

---
# Example 2: VirtualPortGroup with static IP from podCIDR
device:
  driver: XE
  address: "192.168.1.100"
  port: 443
  username: admin
  tls:
    enabled: true
    insecureSkipVerify: true
  podCIDR: "10.0.0.0/24"
  xe:
    networking:
      interface:
        type: VirtualPortGroup
        virtualPortGroup:
          dhcp: false
          interface: "0"
          guestInterface: 0

---
# Example 3: AppGigabitEthernet access with DHCP (Catalyst 9000 front-panel)
device:
  driver: XE
  address: "192.168.1.100"
  port: 443
  username: admin
  tls:
    enabled: true
    insecureSkipVerify: true
  xe:
    networking:
      interface:
        type: AppGigabitEthernet
        appGigabitEthernet:
          mode: access
          dhcp: true
          guestInterface: 0

---
# Example 4: AppGigabitEthernet trunk with static IP on a tagged VLAN
device:
  driver: XE
  address: "192.168.1.100"
  port: 443
  username: admin
  tls:
    enabled: true
    insecureSkipVerify: true
  podCIDR: "10.0.0.0/24"
  xe:
    networking:
      interface:
        type: AppGigabitEthernet
        appGigabitEthernet:
          mode: trunk
          vlanIf:
            dhcp: false
            vlan: 200
            guestInterface: 0

---
# Example 5: AppGigabitEthernet trunk with DHCP on a tagged VLAN
device:
  driver: XE
  address: "192.168.1.100"
  port: 443
  username: admin
  tls:
    enabled: true
    insecureSkipVerify: true
  xe:
    networking:
      interface:
        type: AppGigabitEthernet
        appGigabitEthernet:
          mode: trunk
          vlanIf:
            dhcp: true
            vlan: 200
            guestInterface: 0

---
# Example 6: Management interface with DHCP
device:
  driver: XE
  address: "192.168.1.100"
  port: 443
  username: admin
  tls:
    enabled: true
    insecureSkipVerify: true
  xe:
    networking:
      interface:
        type: Management
        management:
          dhcp: true
          guestInterface: 0

---
# Example 7: Management interface with static IP from podCIDR
device:
  driver: XE
  address: "192.168.1.100"
  port: 443
  username: admin
  tls:
    enabled: true
    insecureSkipVerify: true
  podCIDR: "10.0.0.0/24"
  xe:
    networking:
      interface:
        type: Management
        management:
          dhcp: false
          guestInterface: 0

---
# Example 8: With resource limits and node topology
# Sets defaults/maximums advertised as node capacity; labels and taints
# are applied to the virtual node for scheduling control.
device:
  driver: XE
  address: "192.168.1.100"
  port: 443
  username: admin
  tls:
    enabled: true
    insecureSkipVerify: true
  region: "edge-east"
  zone:   "edge-east-1"
  labels:
    environment: production
    hw.type: catalyst-9000
  taints:
  - key: workload
    value: edge
    effect: NoSchedule
  maxPods: 16
  resourceLimits:
    defaultCPU: "500m"
    defaultMemory: "512Mi"
    defaultStorage: "500Mi"
    maxCPU: "2000m"
    maxMemory: "4Gi"
    maxStorage: "2Gi"
  xe:
    networking:
      interface:
        type: VirtualPortGroup
        virtualPortGroup:
          dhcp: true
          interface: "0"
          guestInterface: 0

---
# Example 9: With OpenTelemetry topology export and allowUnsignedApps
# The OTEL exporter sends topology traces (CDP/OSPF neighbors, hosted apps)
# to an OTLP gRPC collector on the configured interval. Enabling
# allowUnsignedApps bypasses the pkg-policy-invalid guard during installs;
# use only when the device is not enforcing signed-verification.
device:
  driver: XE
  address: "192.168.1.100"
  port: 443
  username: admin
  tls:
    enabled: true
    insecureSkipVerify: true
  allowUnsignedApps: true
  otel:
    enabled: true
    endpoint: "otel-collector.observability.svc:4317"
    insecure: true
    serviceName: "cisco-network"
    intervalSecs: 60
  xe:
    networking:
      interface:
        type: VirtualPortGroup
        virtualPortGroup:
          dhcp: true
          interface: "0"
          guestInterface: 0