-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ship a default Environment #311
Milestone
Comments
AlekSi
referenced
this issue
in AlekSi/talos-sidero
May 18, 2021
Closes #311. Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
AlekSi
referenced
this issue
in AlekSi/talos-sidero
May 18, 2021
Closes #311. Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
AlekSi
referenced
this issue
in AlekSi/talos-sidero
May 18, 2021
Closes #311. Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
AlekSi
referenced
this issue
in AlekSi/talos-sidero
May 18, 2021
Closes #311. Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
talos-bot
referenced
this issue
in AlekSi/talos-sidero
May 18, 2021
Closes #311. Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
talos-bot
pushed a commit
that referenced
this issue
May 18, 2021
Closes #311. Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most of an Envirtonment can be automatically determined, and even for customizations, it is easier to modify an existing template than to start from scratch.
We should supply a default boot Environment with Sidero; mostly, this just involves knowing Sidero's own endpoint name and the "current" Talos release.
The text was updated successfully, but these errors were encountered: