[BUG-NOK] Open-Edge-Node - rke2 reference

[amathan]

Bug Description

On the edge node there is reference for the rke2

cat /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
KUBECONFIG=/etc/rancher/rke2/rke2.yaml

cat /etc/rancher/rke2/rke2.yaml
cat: /etc/rancher/rke2/rke2.yaml: No such file or directory

System Setup

Device provisioned against AWS based Orchestrator v3.1.2

Reproducible Steps

1. Provision a device
2. On the node check the /etc/environment file to see rke2 reference

Root Cause Analysis

No response

[krishnajs]

@adorney99 can you please verify if we are setting k3s path as well ?

[hyunsun]

@Ram-srini Suggest to add /var/lib/rancher/k3s/bin to PATH and replace KUBECONFIG env value to /etc/rancher/k3s/k3s.yaml in the default environment.

[Ram-srini]

@hyunsun Please add required ENV variables into cloud-init.cfg file https://github.com/open-edge-platform/infra-onboarding/blob/main/onboarding-manager/pkg/cloudinit/99_infra.cfg#L234

[hyunsun]

Any hard-coded RKE2 specific environment variables in Infra Manager repository will be removed.
Instead, we'll create drop-in environment file, for example /etc/environment.d/50-k3s.conf, for setting extended PATH and KUBECONFIG path using Cluster Template.

[hyunsun]

@togashidm will be the owner of the fix and update the progress here.