Currently the only supported method to add a the bored-agent to a cluster for Lens Connect is through the Lens Desktop App. The kubernetes directory does not include all of the components that are deployed on a cluster in the lens-platform namespace. To fix this, a helm chart would work with the resources that are already there and also include the one time jobs that run on initial deployment of the bored-agent.
Currently the only supported method to add a the bored-agent to a cluster for Lens Connect is through the Lens Desktop App. The kubernetes directory does not include all of the components that are deployed on a cluster in the
lens-platformnamespace. To fix this, a helm chart would work with the resources that are already there and also include the one time jobs that run on initial deployment of the bored-agent.