Skip to content

resolve different etcd resource prefix for APIService objects #19949

@liggitt

Description

@liggitt

we are passing a different storage constructor that results in APIService objects being stored in a non-standard location in etcd

upstream: <prefix>/apiregistration.k8s.io/apiservices/...
origin: <prefix>/apiservices/...

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.kind/post-rebaselifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/master

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions