Currently the Installer in the helminstall package only accepts on-disk kubeconfigs. Service Mesh Hub needs the ability to pass through an in-memory kubeconfig during automated cluster discovery + registration (i.e. clientcmd.ClientConfig) given that SMH's runtime environment won't have access to a filesystem.
Currently the Installer in the
helminstall
package only accepts on-disk kubeconfigs. Service Mesh Hub needs the ability to pass through an in-memory kubeconfig during automated cluster discovery + registration (i.e.clientcmd.ClientConfig
) given that SMH's runtime environment won't have access to a filesystem.