Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Make "k0s install" a bit more verbose #544

Closed
trawler opened this issue Dec 17, 2020 · 2 comments · Fixed by #637
Closed

Make "k0s install" a bit more verbose #544

trawler opened this issue Dec 17, 2020 · 2 comments · Fixed by #637
Assignees
@jasmingacic
Labels
area/install backlog/candidate enhancement New feature or request
Milestone
0.10.0

Comments

@trawler
Copy link
Contributor

trawler commented Dec 17, 2020 •
edited

Is your feature request related to a problem? Please describe.
When running k0s install it would be useful to have some more information:

  • The type of service installed
  • The location of the startup script
  • An output of the startup command
@trawler trawler added the enhancement New feature or request label Dec 17, 2020
@trawler trawler changed the title Make cmd install a bit more verbose Make "k0s install" a bit more verbose Dec 17, 2020
@jasmingacic
Copy link
Contributor

jasmingacic commented Dec 17, 2020 •
edited

I've submitted a PR kardianos/service#255 which will allow us to return path to the service file.

@jnummelin jnummelin added this to the 0.10.0 milestone Jan 15, 2021
@jasmingacic
Copy link
Contributor

The PR I made in December hasn't been merged. So probably we'd have to pull this information from k0s.

@jasmingacic jasmingacic mentioned this issue Jan 19, 2021
Merged
@jasmingacic jasmingacic self-assigned this Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jasmingacic jasmingacic

Labels
area/install backlog/candidate enhancement New feature or request
Projects
None yet
Milestone
0.10.0
Development

Successfully merging a pull request may close this issue.

k0s status jasmingacic/k0s
3 participants
@jnummelin @jasmingacic @trawler