Last updated: 2020-01-02 10:59:17


Object Management Instructions

You can directly manipulate native Kubernetes objects such as Deployment and DaemonSet in the console.
The Kubernetes objects are persistent entities in the cluster and are used to host services running within the cluster. Different Kubernetes objects can express different meanings:

  • Running applications
  • Resources available to applications
  • Application-associated policies

You can use Kubernetes objects directly in the TKE console or through the Kubernetes APIs such as kubectl.

Types of Objects

Common Kubernetes objects are mainly divided into the following types:

  • Workloads
    • Deployment: used to manage a Pod for which a scheduling rule has been specified.
    • StatefulSet: used to manage the workload API objects of a stateful application.
    • DaemonSet: used to ensure that pods are running on all or some of the nodes, such as the log collection program.
    • Job: a Job creates one or more Pods until the end of run.
    • CronJob: a Job that runs as scheduled.
  • Services
    • Service: a Kubernetes object that provides Pod access. Different types can be defined based on business needs.
    • Ingress: a Kubernetes object that manages external access to Services in a cluster.
  • Configuration
    • ConfigMap: used to store configuration information.
    • Secret: used to store sensitive information such as passwords and tokens.
  • Storage
    • Volume: used to store container access-related data.
    • Persistent Volume (PV): a piece of storage configured in the Kubernetes cluster.
    • Persistent Volumes Claim (PVC): claim for a storage request. If PVs were Pods, then PVCs would be workloads.
    • StorageClass: used to describe the type of storage. When a PVC is created, the storage of the specified type (that is, stored template) is created using StorageClass.

There are dozens of other Kubernetes objects such as Namespace, HPA, and ResourceQuotas. You can use different objects based on your business needs. Available objects vary depending on Kubernetes version. For more information, visit Kubernetes' official website.

Resource limit

TKE uses ResourceQuota/tke-default-quota to control resources for all managed clusters. If you need more quota items, please submit a ticket.

Cluster scale Total limit
Pod ConfigMap
Number of nodes <= 5 4000 3000
5 < number of nodes <= 20 8000 6000
Number of nodes > 20 NA NA

Object Management Operations