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.

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

[Feature] k3d-managed registry for v3 #283

Closed
wants to merge 1 commit into from
Closed

Conversation

iwilltry42
Copy link
Member

Overview

First Level

  • new command k3d create registry
    • --cluster (multiple): clusters to attach to upon creation
  • new command k3d delete registry
  • new command k3d start registry
  • new command k3d stop registry

Second Level

  • new flag k3d create cluster --use-registry REGISTRY_NAME

Important Notes

  • we need to keep track of the clusters using a registry, so that we can update the respective registries.yaml files when creating/starting/stopping/deleting a registry

Status

  • draft of first level k3d create registry command

@iwilltry42 iwilltry42 added enhancement New feature or request v3 labels Jun 17, 2020
@iwilltry42 iwilltry42 added this to the 3.1.0 milestone Jun 17, 2020
@iwilltry42 iwilltry42 self-assigned this Jun 17, 2020
@iwilltry42 iwilltry42 changed the base branch from master to main July 15, 2020 05:10
@blaggacao
Copy link

@iwilltry check https://github.com/kubernetes/enhancements/blob/0d69f7cea6fbe73a7d70fab569c6898f5ccb7be0/keps/sig-cluster-lifecycle/generic/1755-communicating-a-local-registry/README.md which is accepted/merged. It proposes an incluster standardized ConfigMap for state that third party tooling can support.

@iwilltry42
Copy link
Member Author

Closed in favor of #334 which is adapted to the new project setup!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants