-
Notifications
You must be signed in to change notification settings - Fork 1
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
Refactor internal logic of RMK cluster provider initialization and selection #29
Labels
Comments
anovikov-el
added
enhancement
New feature or request
question
Further information is requested
labels
Jul 15, 2024
apanasiuk-el
added a commit
that referenced
this issue
Aug 7, 2024
apanasiuk-el
added a commit
that referenced
this issue
Aug 7, 2024
apanasiuk-el
added a commit
that referenced
this issue
Aug 7, 2024
apanasiuk-el
added a commit
that referenced
this issue
Aug 8, 2024
apanasiuk-el
added a commit
that referenced
this issue
Sep 25, 2024
apanasiuk-el
added a commit
that referenced
this issue
Sep 26, 2024
apanasiuk-el
added a commit
that referenced
this issue
Sep 30, 2024
apanasiuk-el
added a commit
that referenced
this issue
Oct 1, 2024
apanasiuk-el
added a commit
that referenced
this issue
Oct 23, 2024
apanasiuk-el
added a commit
that referenced
this issue
Oct 31, 2024
apanasiuk-el
added a commit
that referenced
this issue
Nov 6, 2024
apanasiuk-el
added a commit
that referenced
this issue
Nov 21, 2024
apanasiuk-el
added a commit
that referenced
this issue
Nov 25, 2024
apanasiuk-el
added a commit
that referenced
this issue
Dec 11, 2024
apanasiuk-el
added a commit
that referenced
this issue
Dec 16, 2024
apanasiuk-el
added a commit
that referenced
this issue
Dec 17, 2024
apanasiuk-el
added a commit
that referenced
this issue
Dec 17, 2024
apanasiuk-el
added a commit
that referenced
this issue
Dec 18, 2024
apanasiuk-el
added a commit
that referenced
this issue
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently, a cluster provided is specified during
rmk config init
. Also there are subcommands likermk cluster k3d
.A refactoring of the
rmk cluster
commands is needed, so the commands are the same and consistent not depending on a provider (e.g., aws, azure, k3d).Steps to reproduce
No response
Expected behaviour
No response
Actual behaviour
No response
Environment info
No response
Agree to the Code of Conduct
The text was updated successfully, but these errors were encountered: