-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[WIP] Custom Resource Definition feature to replace Third Party Resources #2449
Conversation
ResourceKindThirdPartyResource: {"thirdpartyresources", ClientTypeExtensionClient, true}, | ||
ResourceKindCustomResourceDefinition: {"CustomResourceDefinition", ClientTypeAPIExtensionsClient, true}, | ||
ResourceKindStorageClass: {"storageclasses", ClientTypeStorageClient, false}, | ||
ResourceKindEndpoint: {"endpoints", ClientTypeDefault, true}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Be careful during merge if cron jobs will go to master first. It will not merge automatically due to indent change.
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
I'll have a look. |
Should be done after Angular migration in the new branch. /close |
Any ideas if this work is already complete? Does the dashboard support CRDs today? |
@kenan435: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Since Third Party Resources will be deprecated in k8s 1.8, we are introducing Custom Resource Definitions feature which is supposed to replace Third Party Resources. The two feature TPR and CRD will both be present on the dashboard during the k8s's 1.7 iteration to easy with migration from TPR's to CRD's