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

Confusing project name #44

Open
PrivatePuffin opened this issue Sep 2, 2021 · 4 comments
Open

Confusing project name #44

PrivatePuffin opened this issue Sep 2, 2021 · 4 comments

Comments

@PrivatePuffin
Copy link

k8s_gateway is not really a smart name. Considering the native k8s feature with the same name that has been in developement for a while now ;-)
@networkop
Copy link
Collaborator

This project fell victim to one of the two hardest problems in computer science. and it's not cache invalidation.
do you have a better suggestion?

@PrivatePuffin
Copy link
Author

PrivatePuffin commented Sep 3, 2021 •
edited
Loading

Hmm... Thats actually a good question...
Maybe KISS and do something descriptive like: CoreDNS_k8s_gateway?

@networkop
Copy link
Collaborator

I feel like having a CoreDNS in the name of a CoreDNS plugin is duplicating information. All plugins are already scoped by the CoreDNS project.
I think the best-fitting name is k8s_external but this name is already taken by the built-in plugin. Maybe something like k8s-external-coredns?

@PrivatePuffin
Copy link
Author

Maybe: k8s-external-gateway? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PrivatePuffin @networkop