Comments (8)
Having some way of short scopes as an alternative to fully-qualified namespaced resource names would be useful for Aggregated APIs. For example,
kubectl get servicecatalog:binding my-binding
where servicecatalog
is an alias for the API server owning the binding
resource type.
from apiserver.
Example of fully qualified specification looks like
k get binding.servicecatalog.k8s.io
k get bindings.v1alpha1.servicecatalog.k8s.io --all-namespaces
Long and repetitive to type.
Even had we created a type that was unique at the time, there is no guarantee that a future type would not be created in the core with the same name later. (i.e. we created Binding type first, but later core apiserver comes along and creates a Binding type)
We basically need ICANN/IANA for types in the kube namespace.
from apiserver.
We basically need ICANN/IANA for types in the kube namespace.
it is not realistic to have a centralized registry of unique resource names in the decentralized Aggregated APIs world.
The only reliable solution provided out of the box is fully qualified namespace, but as you mentioned it's too long and repetitive for manual typing in kubectl. Thus, I would consider an alternative scope
approach, and discuss what could be the generic scope which works for everyone:
- API server alias/key - simple and directly suits the API Aggregation which is essentially a collection of API servers under proxy umbrella
- hierarchical name resolution (e.g.
bindings
,servicecatalog.bindings
,v1alpha1.servicecatalog.bindings
etc) with prioritized list of API servers/namespace for conflict naming resolution (i.e.bindings
would be resolved to Kubernetes core API once it is introduced)
from apiserver.
I believe this same conflict dynamic is why TPR does not work with aggregation. The TPR names "binding.servicecatalog.k8s.io", "broker.servicecatalog.k8s.io", etc. overlap with the aggregated API of the same names. While we don't care about TPR, this same problem might also affect CRD.
from apiserver.
Partially qualified names are found too, so kubectl get binding.se
works. You only need to specify enough to unambiguous. Scripts should always fully qualify.
from apiserver.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta
.
/lifecycle stale
from apiserver.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
from apiserver.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
from apiserver.
Related Issues (20)
- apiserver fails json patches with 422 when patch body does not match default json.Marshal encoding HOT 4
- unable to get openapi models: OpenAPIV3 config must not be nil HOT 1
- log error about cert expired - does not show important info HOT 8
- Is it possible to disable TLS in apiserver? I would want istio sidecar to terminate TLS. HOT 4
- Update grpc/otelgrpc dependency to fix CVE-2023-47108 HOT 2
- Segfault when kube-client is not specified.
- Invalid Go version in go.mod HOT 1
- Expose username and group from the appropriate headers HOT 9
- Why exclude resources with errors in the calculation? These errors do not necessarily affect all evaluators HOT 4
- apiserver returns incorrectly results when "Limit" and "LabelSelector" parameters are both set in certain case HOT 7
- Update go-restful module to version >= 3.8.0 due to security issues HOT 5
- OIDC errors HOT 4
- Weird behaviour for remainingItemCount for List HOT 5
- EOL Component HOT 6
- `undefined: unsafe.StringData` on build 1.27-rc.0 with go 1.19 HOT 3
- feature request - audit policy non-resource URL full wildcard support HOT 4
- Query on ContinueToken HOT 8
- Tag v0.28.1 - Issue HOT 6
- Dependency upgrade request - Incompatibility with go.opentelemetry.io/otel version v.1.15.0 and above HOT 5
- New apiserver release that fixes CVE-2023-44487 HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from apiserver.