flyteorg / flyte

Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
https://flyte.org
Apache License 2.0
5.79k stars 660 forks source link

[Housekeeping] Enable verbose logging for sandbox and demo environments #2491

Open pmahindrakar-oss opened 2 years ago

pmahindrakar-oss commented 2 years ago

Describe the issue

Currently its hard to debug errors in sandbox and demo environments if the installation fails during helm installation . Enable verbose logging for helm commands and also kubectl commands

https://kubernetes.io/docs/reference/kubectl/cheatsheet/#kubectl-output-verbosity-and-debugging

The default option should be with this flag off.

 flytectl demo start --verbose
 flytectl sandbox start --verbose

Have similar flags during teardown of the environments

flytectl demo teardown --verbose
flytectl sandbox teardown --verbose

What if we do not do this?

Longer debugging cycles

Related component(s)

flytectl,flyte

Are you sure this issue hasn't been raised already?

Have you read the Code of Conduct?

yindia commented 2 years ago

cc: @TheYk98

GrayFlash commented 2 years ago

Hey @pmahindrakar-oss @samhita-alla can I pick up this issue??

samhita-alla commented 2 years ago

@GrayFlash, will have to assign it to Hemanth as he created a PR already.

GrayFlash commented 2 years ago

oh no issues. @samhita-alla is there any decent feature related issue I can work on?? flytectl repo seems to have no such issues.

samhita-alla commented 2 years ago

@GrayFlash, have you seen https://github.com/flyteorg/flyte/issues/2777?

GrayFlash commented 2 years ago

Sure working on it @samhita-alla going through the codebase and docs properly.!!

github-actions[bot] commented 1 year ago

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

github-actions[bot] commented 1 year ago

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

github-actions[bot] commented 3 months ago

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏