You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we assume that lagoon-facts is going to be run inside a cli pod.
In moving to custom tasks, we could run lagoon-facts in cli pods/services - however, there is the possibility that a project doesn't use the cli service.
In this case, we'd still like to be able to run lagoon-facts.
To this end, it would be good to be able to run this app in a custom task. Specifically, it would be good to be able to run these as a custom image.
To this end, we'd like to enhance the lagoon-facts app to
Make facts K8S aware (so we can load access tokens and list services in the current namespaces)
where gatherers run, we need to be able to support either running directly in the current environment (how it currently works) OR exec'ing into running containers.
This will allow us to run gathers in multiple contexts (either directly in a collection environment or by execing into running environments from a task)
The text was updated successfully, but these errors were encountered:
Currently, we assume that lagoon-facts is going to be run inside a cli pod.
In moving to custom tasks, we could run lagoon-facts in cli pods/services - however, there is the possibility that a project doesn't use the cli service.
In this case, we'd still like to be able to run lagoon-facts.
To this end, it would be good to be able to run this app in a custom task. Specifically, it would be good to be able to run these as a custom image.
To this end, we'd like to enhance the lagoon-facts app to
This will allow us to run gathers in multiple contexts (either directly in a collection environment or by execing into running environments from a task)
The text was updated successfully, but these errors were encountered: