-
Notifications
You must be signed in to change notification settings - Fork 539
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
migration tool is awesome #170
Comments
lol - well it's very k8s centric now. i.e. it only supports k8s related plugins. |
ok, perhaps it could evolve into something more general. and maybe the plugins themselves could publish information / code to convert their own configs? If we did that, then external plugins could also implement that. |
yes - I had same dream, but I intentionally didn't go that route because it would have involved coordination in coredns/coredns ... and I needed a solution to happen ... |
... but now that we have a solution ... Of course we can propose going that route. |
Yes, getting the details working in here makes sense.
…On Fri, May 17, 2019 at 10:33 AM chrisohaver ***@***.***> wrote:
... but now that we have a solution ... Of course we can propose going
that route.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#170?email_source=notifications&email_token=ACIHRM4BDCVFVYZJHRQPGBLPV3T7DA5CNFSM4HNXBSDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVVMGLA#issuecomment-493536044>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACIHRM3EFWHQ25GA36NUFWLPV3T7DANCNFSM4HNXBSDA>
.
|
@johnbelamaric, thanks for the enthusiastic support. I've opened #174, proposing generalizing the tool and moving it to a new repo. |
This is super-cool, I don't think it only applies to K8s, maybe it should be up-leveled to the deployment directory, or even have its own repo.
The text was updated successfully, but these errors were encountered: