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

Implement a ContextCommand to connect to an existing deployment #588

Open
1 of 5 tasks
Tracked by #47
jeromy-cannon opened this issue Sep 17, 2024 · 0 comments
Open
1 of 5 tasks
Tracked by #47

Implement a ContextCommand to connect to an existing deployment #588

jeromy-cannon opened this issue Sep 17, 2024 · 0 comments
Assignees
@jeromy-cannon
Labels
Epic Lv2 A body of work that can be broken down into specific tasks. HashSphere Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. Needs Refinement The issue needs more refinement and/or design before it can be worked P1 High priority issue. Required to be completed in the assigned milestone.

Comments

@jeromy-cannon
Copy link
Contributor

jeromy-cannon commented Sep 17, 2024 •
edited
Loading

Tasks
Beta Give feedback
  1. Implement solo context connect part 1 of 2 - updates the LocalConfig by connecting a deployment to a k8s context #754
    0 of 12
    HashSphere Requirement P0
    Ivo-Yankov
  2. Implement solo context connect - connects to a deployment and pulls back the RemoteConfig for single cluster deployment #755
    HashSphere Requirement Multiple Cluster Support P1
    Ivo-Yankov
  3. Implement solo context connect - connects to a deployment and pulls back the RemoteConfig for two cluster deployment #913
    HashSphere Requirement Multiple Cluster Support P1
    Ivo-Yankov
  4. add a flag to pass email address into solo context connect #950
    HashSphere Requirement Multiple Cluster Support P1
    Ivo-Yankov
  5. bug: solo context connect prompts for cluster after already supplied #951
    Bug HashSphere Requirement Multiple Cluster Support P1
    Ivo-Yankov
@jeromy-cannon jeromy-cannon mentioned this issue Sep 17, 2024
Open
@jeromy-cannon jeromy-cannon self-assigned this Sep 17, 2024
@jeromy-cannon jeromy-cannon added the Needs Refinement The issue needs more refinement and/or design before it can be worked label Sep 17, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Solo Sep 17, 2024
@jeromy-cannon jeromy-cannon added P0 An issue impacting production environments or impacting multiple releases or multiple individuals. Epic Lv2 A body of work that can be broken down into specific tasks. HashSphere Requirement labels Oct 24, 2024
@jeromy-cannon jeromy-cannon added P1 High priority issue. Required to be completed in the assigned milestone. Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. and removed P0 An issue impacting production environments or impacting multiple releases or multiple individuals. labels Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeromy-cannon jeromy-cannon

Labels
Epic Lv2 A body of work that can be broken down into specific tasks. HashSphere Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. Needs Refinement The issue needs more refinement and/or design before it can be worked P1 High priority issue. Required to be completed in the assigned milestone.
Projects
Solo
Status: 🆕 New
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeromy-cannon