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

[Feature]Minimal deployment overlay to serve as starting point for Flyte installation #444

Closed
1 of 13 tasks
kumare3 opened this issue Aug 5, 2020 · 5 comments
Closed
1 of 13 tasks

[Feature]Minimal deployment overlay to serve as starting point for Flyte installation #444

kumare3 opened this issue Aug 5, 2020 · 5 comments
Labels
enhancement New feature or request stale untriaged This issues has not yet been looked at by the Maintainers

Comments

@kumare3
Copy link
Contributor

kumare3 commented Aug 5, 2020

Motivation: Why do you think this is important?
Provide a minimal kustomize Overlay, which can be used as a starting point for cloud deployments. This should go alongwith a tutorial of how to configure Flyte for AWS/GCP/Azure etc.

Goal: What should the final outcome look like, ideally?
Any user should be able to follow this doc and setup Flyte in their own infrastructure.

Describe alternatives you've considered
Current getting started doc is too simple. Flyte provides a lot of knobs for complex setups and discovery and documentation for these knobs is not readily available

Flyte component

  • Overall
  • Flyte Setup and Installation scripts
  • Flyte Documentation
  • Flyte communication (slack/email etc)
  • FlytePropeller
  • FlyteIDL (Flyte specification language)
  • Flytekit (Python SDK)
  • FlyteAdmin (Control Plane service)
  • FlytePlugins
  • DataCatalog
  • FlyteStdlib (common libraries)
  • FlyteConsole (UI)
  • Other
@kumare3 kumare3 added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels Aug 5, 2020
@kumare3 kumare3 changed the title [Feature] [Feature]Minimal deployment overlay to serve as starting point for Flyte installation Aug 5, 2020
@kanterov kanterov mentioned this issue Aug 31, 2020
Merged
8 tasks
@schottra
Copy link
Contributor

Implemented by flyteorg/flyteconsole#92
Available in flyteconsole v0.12.0

@schottra schottra reopened this Sep 22, 2020
@schottra
Copy link
Contributor

Oops. I didn't realize this issue was tracking more than just the inputs/outputs. Reopened it. I'll let @kumare3 decide when it's done.

eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 6, 2022
@hamersaw
Restrict garbage collection with sharded propeller (flyteorg#444)
ac88f95 
* refactored to isolate computing sharded label selector requirements

Signed-off-by: Daniel Rammer <[email protected]>

* restricting garbage collection with sharded label selector requirements

Signed-off-by: Daniel Rammer <[email protected]>

* fix lint issue

Signed-off-by: Daniel Rammer <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
@eugenejahn @anrusina
Make whole row clickable to open TaskExecutionDetails panel (flyteorg…
b6e9941 
…#444)

* fix: issue 398
* fix: prevent parent onclick event trigger

Signed-off-by: eugenejahn <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 9, 2023
@hamersaw
Restrict garbage collection with sharded propeller (flyteorg#444)
774c457 
* refactored to isolate computing sharded label selector requirements

Signed-off-by: Daniel Rammer <[email protected]>

* restricting garbage collection with sharded label selector requirements

Signed-off-by: Daniel Rammer <[email protected]>

* fix lint issue

Signed-off-by: Daniel Rammer <[email protected]>
@github-actions
Copy link

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 github-actions bot added the stale label Aug 26, 2023
@github-actions
Copy link

github-actions bot commented Sep 2, 2023

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 github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 2, 2023
eapolinario pushed a commit that referenced this issue Sep 26, 2023
@jeevb
Revert "GPU Type (#419)" (#444)
7582ad0 
* Revert "GPU Type (#419)"

This reverts commit 7bd98a9.

Signed-off-by: Jeev B <[email protected]>

* Restore .readthedocs.yml

Signed-off-by: Jeev B <[email protected]>

---------

Signed-off-by: Jeev B <[email protected]>
@eapolinario eapolinario reopened this Nov 2, 2023
@kumare3
Copy link
Contributor Author

kumare3 commented Dec 22, 2023

all cloud providers are supported through helm and terraform.

@kumare3 kumare3 closed this as completed Dec 22, 2023
pvditt pushed a commit that referenced this issue Dec 29, 2023
@jeevb
Revert "GPU Type (#419)" (#444)
6011898 
* Revert "GPU Type (#419)"

This reverts commit b92acad.

Signed-off-by: Jeev B <[email protected]>

* Restore .readthedocs.yml

Signed-off-by: Jeev B <[email protected]>

---------

Signed-off-by: Jeev B <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request stale untriaged This issues has not yet been looked at by the Maintainers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@eapolinario @schottra @kumare3