5 Commits

Author	SHA1	Message	Date
Patrick Ohly	8a908e0c0b	remove import doc comments ... The "// import <path>" comment has been superseded by Go modules. We don't have to remove them, but doing so has some advantages: - They are used inconsistently, which is confusing. - We can then also remove the (currently broken) hack/update-vanity-imports.sh. - Last but not least, it would be a first step towards avoiding the k8s.io domain. This commit was generated with sed -i -e 's;^package \(.*\) // import.*;package \1;' $(git grep -l '^package.*// import' | grep -v 'vendor/') Everything was included, except for package labels // import k8s.io/kubernetes/pkg/util/labels because that package is marked as "read-only".	2024-12-02 16:59:34 +01:00
kerthcet	02f77a1b84	Feat: ga component config in kube-scheduler ... Signed-off-by: kerthcet <kerthcet@gmail.com>	2022-07-29 08:47:48 +08:00
Abdullah Gharaibeh	faf0ce68a0	Remove scheduler's legacy policy config	2021-10-24 21:58:12 -04:00
Jordan Liggitt	87a4e082ac	Change defaulter-gen input to package path	2021-08-14 11:00:18 -04:00
Wei Huang	c649666b4a	manual API changes and code refactoring ... - add Policy API to pkg/scheduler/apis/config and staging/src/k8s.io/kube-scheduler/config/v1 - dual-register Policy as apiGroup "v1" and "kubescheduler.config.k8s.io - move/merge pkg/scheduler/api to pkg/scheduler/apis/config/... - alias schedulerapi to pkg/scheduler/apis/config - alias legacyapi to pkg/scheduler/api - eliminate latest.Codec; use scheme.Codecs instead - unit tests to verify Policy YAML with version "v1" or "kubescheduler.config.k8s.io/v1" can be loaded properly - update api/api-rules/violation_exceptions.list	2019-11-01 14:24:36 -07:00