Improve resource support

[maciaszczykm]

Do not close the issue. It will be used to track resource support for the next versions.

It is currently based on: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/

Workloads

• Container v1 core (within the context of a pod)
• CronJob v1beta1 batch
• DaemonSet v1 apps
• Deployment v1 apps
• Job v1 batch
• Pod v1 core
• ReplicaSet v1 apps
• ReplicationController v1 core
• StatefulSet v1 apps

Services

• Endpoints v1 core
• EndpointSlice v1beta1 discovery.k8s.io
• Ingress v1beta1 networking.k8s.io
• IngressClass v1beta1 networking.k8s.io
• Service v1 core

Config and storage

• ConfigMap v1 core
• CSIDriver v1 storage.k8s.io
• CSINode v1 storage.k8s.io
• Secret v1 core
• PersistentVolumeClaim v1 core
• StorageClass v1 storage.k8s.io
• Volume v1 core (within the context of a pod)
• VolumeAttachment v1 storage.k8s.io

Metadata

• ControllerRevision v1 apps
• CustomResourceDefinition v1 apiextensions.k8s.io (can be found in a separate menu section)
• Event v1 core (within the context of other resources)
• LimitRange v1 core (within the context of a namespace)
• HorizontalPodAutoscaler v1 autoscaling (within the context of a deployment)
• MutatingWebhookConfiguration v1 admissionregistration.k8s.io
• ValidatingWebhookConfiguration v1 admissionregistration.k8s.io
• PodTemplate v1 core (within the context of workloads)
• PodDisruptionBudget v1beta1 policy
• PriorityClass v1 scheduling.k8s.io
• PodPreset v1alpha1 settings.k8s.io
• PodSecurityPolicy v1beta1 policy

Cluster

• APIService v1 apiregistration.k8s.io
• Binding v1 core
• CertificateSigningRequest v1beta1 certificates.k8s.io
• ClusterRole v1 rbac.authorization.k8s.io
• ClusterRoleBinding v1 rbac.authorization.k8s.io
• ComponentStatus v1 core
• FlowSchema v1alpha1 flowcontrol.apiserver.k8s.io
• Lease v1 coordination.k8s.io
• LocalSubjectAccessReview v1 authorization.k8s.io
• Namespace v1 core
• Node v1 core
• PersistentVolume v1 core
• PriorityLevelConfiguration v1alpha1 flowcontrol.apiserver.k8s.io
• ResourceQuota v1 core (within the context of a namespace)
• Role v1 rbac.authorization.k8s.io
• RoleBinding v1 rbac.authorization.k8s.io
• RuntimeClass v1beta1 node.k8s.io
• SelfSubjectAccessReview v1 authorization.k8s.io
• SelfSubjectRulesReview v1 authorization.k8s.io
• ServiceAccount v1 core
• SubjectAccessReview v1 authorization.k8s.io
• TokenRequest v1 authentication.k8s.io
• TokenReview v1 authentication.k8s.io
• NetworkPolicy v1 networking.k8s.io

[zehuaiWANG]

I think service accounts are quite necessary. Because many operations need to bind service accounts to give permissions. And like endpoints and controller revision, would it be better for us to put them directly in the details page of service (statefulset / daemonset)?

[zehuaiWANG]

BTW, I'm willing to contribute any part of the backend code if needed.