-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Introduce short names for Knative resources #1588
Comments
Some obvious ones to start off:
|
I was about to suggest the same. In addition to |
FYI I do like the idea to add short names though. |
Yes, this is why @grantr suggested Also, this is pattern we could use for all Knative resource short names: |
Should obviously all start with k |
I can read in another comment that the short names do not resolve to fully qualified names, and thus |
I did not make a new issue for it. I just documented it in this issue #1397 (comment) |
Update: it looks like upstream kubectl fixes the issue I have mentioned. Current:
Updated:
|
/area API
I suggest to introduce short names for the Knative resources ("Service", "Revision", "Configuration", "Route") for the following reasons:
configurations
services.serving.knative.dev
, which is long to type when usingkubectl
Kubernetes allows to define short names. See here for an example.
Let's use this issue to suggest short names. We could use some user research to validate them if we need. CC @tliberman
The text was updated successfully, but these errors were encountered: