prep for federation

[jmarhee]

contexts need to be renamed so the regions created can be federated upsteam (i.e. outside of this project)

requires a write-up, or include in README

[jmarhee]

7 standardizes cluster templating, does not entirely address this yet (still needs context renaming)

[jmarhee]

I'm referring to this: https://www.operatorhub.io/operator/federationv2-community.v0.0.2

I'd like to see the use case for this project reflect that we're discussing federated region-specific clusters from a primary region to facilitate workloads that can be decentralized from a primary cluster in a larger/not-edge region for a given user. Approaching new-issue territory, but I'd like use cases to reflect this.

[jmarhee]

https://github.com/packet-labs/packet-k3s/pull/11 addresses context differentiation issue; we'll do some kind of kubeconfig_detection function like:

kubeconfig_reload () {
    export KUBECONFIG="" 
    for f in `ls ~/.kube/config/ | grep yaml`
    do
        export KUBECONFIG="$HOME/.kube/config/$f:$KUBECONFIG" 
    done
}

on the primary controller, or something (maybe just local-exec in terraform rather than add more software to the controller(s) to manage the federation operator client tooling.