Object Management Instructions
You can operate native Kubernetes objects such as Deployment and DaemonSet in the console.
The Kubernetes objects are persistent entities in clusters and are used to host services running within the clusters. Different Kubernetes objects can represent diffrent entites:
- Running applications
- Resources available to applications
- Policies associated with applications
You can use Kubernetes objects directly in the TKE console or through the Kubernetes APIs such as kubectl.
Types of Objects
Common Kubernetes objects can be divided into the following types:
- Deployment: used to manage Pods for which scheduling rules have been specified.
- StatefulSet: the workload API object used to manage stateful applications.
- DaemonSet: ensures that all or some nodes run a copy of a Pod, such as a logs collection daemon.
- Job: creates one or more Pods until the end of run.
- CronJob: scheduled Job.
- Service: a Kubernetes object that provides access to Pod. You can define different types based on your needs.
- Ingress: a Kubernetes object that manages external access to services in a cluster.
- ConfigMap: used to store configuration information.
- Secret: used to store sensitive information such as passwords and tokens.
- Volume: used to store data related to container access.
- Persistent Volumes (PV): a piece of storage configured in the Kubernetes cluster.
- PersistentVolumesClaim (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, storage of the specified type, i.e., storage 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 website.
TKE uses ResourceQuota/tke-default-quota to set resource limit for all managed clusters. If you need a higher quota, please submit a ticket.
|Number of nodes ≤ 5
|5 < Number of nodes ≤ 20
|Number of nodes > 20
Object Management Operations