[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-detail-31937":3,"doc-seo-31937":27},{"code":4,"msg":5,"data":6},0,"success",{"doc_id":7,"user_id":8,"nickname":9,"user_avatar":10,"doc_module":4,"category_id":11,"category_name":12,"doc_title":13,"doc_description":14,"file_id":15,"file_url":16,"file_type":17,"file_size":18,"view_count":4,"is_deleted":4,"is_public":19,"is_downloadable":19,"audit_status":19,"page_count":20,"language":21,"language_code":22,"table_of_contents":23,"faqs":24,"seo_title":13,"seo_description":14,"update_tm":25,"read_time":26},31937,1099513958762,"Logic","https://ap-avatar.wpscdn.com/avatar/1000023916a998db790?_k=1776737595927829259",8,"Research & Report","Enhancing the Kubernetes Platform with a Load-Aware Orchestration Strategy","Microservice architecture is increasingly adopted for large-scale applications in distributed, resource-constrained cloud-to-edge environments. Kubernetes is a key cloud-native orchestrator, yet its default static scheduling does not consider runtime resource usage patterns across shared node clusters, which can increase contention and degrade response time. To address this, the work proposes a load-aware orchestration strategy that dynamically adjusts microservice placement according to real-time resource behavior. Prototype evaluation in a testbed shows substantial improvements over the standard Kubernetes scheduler.","cbCaimAW6zzPGTDF","https://ap.wps.com/l/cbCaimAW6zzPGTDF","pdf",2245296,1,15,"English","en","# Introduction\n# Background\n## Kubernetes Scheduler\n## Edge and Cloud-to-Edge Continuum\n# Proposed Framework\n# Performance Evaluation\n# Related Work\n# Conclusions and Future Work","[{\"question\":\"What problem does the proposed approach address in Kubernetes scheduling?\",\"answer\":\"The approach targets Kubernetes’ default static scheduling, which ignores runtime cluster and microservice resource usage, leading to resource contention and worse application response time.\"},{\"question\":\"How does the load-aware orchestration strategy work?\",\"answer\":\"It orchestrates microservice applications dynamically using real-time resource usage patterns and continuously re-adjusts placement as infrastructure and application states change.\"},{\"question\":\"What benefits are reported compared with the standard Kubernetes scheduler?\",\"answer\":\"A prototype evaluation in a testbed demonstrates substantial benefits, including improved application performance while enabling higher application colocation on the same cluster and maintaining acceptable response times.\"}]",1780520435,38,{"code":4,"msg":28,"data":29},"ok",{"site_id":30,"language":22,"slug":31,"title":13,"keywords":32,"description":14,"schema_data":33,"social_meta":84,"head_meta":86,"extra_data":88,"updated_unix":25},105,"enhancing-the-kubernetes-platform-with-a-load-aware-orchestration-strategy","",{"@graph":34,"@context":83},[35,52,66],{"@type":36,"itemListElement":37},"BreadcrumbList",[38,42,46,49],{"item":39,"name":40,"@type":41,"position":19},"https://docshare.wps.com","Home","ListItem",{"item":43,"name":44,"@type":41,"position":45},"https://docshare.wps.com/document/","Document",2,{"item":47,"name":12,"@type":41,"position":48},"https://docshare.wps.com/document/research-report/",3,{"item":50,"name":13,"@type":41,"position":51},"https://docshare.wps.com/document/enhancing-the-kubernetes-platform-with-a-load-aware-orchestration-strategy/31937/",4,{"url":50,"name":13,"@type":53,"author":54,"headline":13,"publisher":56,"fileFormat":59,"description":14,"dateModified":60,"datePublished":60,"encodingFormat":59,"isAccessibleForFree":61,"interactionStatistic":62},"DigitalDocument",{"name":9,"@type":55},"Person",{"url":39,"name":57,"@type":58},"DocShare","Organization","application/pdf","2026-06-03",true,{"@type":63,"interactionType":64,"userInteractionCount":4},"InteractionCounter",{"@type":65},"ViewAction",{"@type":67,"mainEntity":68},"FAQPage",[69,75,79],{"name":70,"@type":71,"acceptedAnswer":72},"What problem does the proposed approach address in Kubernetes scheduling?","Question",{"text":73,"@type":74},"The approach targets Kubernetes’ default static scheduling, which ignores runtime cluster and microservice resource usage, leading to resource contention and worse application response time.","Answer",{"name":76,"@type":71,"acceptedAnswer":77},"How does the load-aware orchestration strategy work?",{"text":78,"@type":74},"It orchestrates microservice applications dynamically using real-time resource usage patterns and continuously re-adjusts placement as infrastructure and application states change.",{"name":80,"@type":71,"acceptedAnswer":81},"What benefits are reported compared with the standard Kubernetes scheduler?",{"text":82,"@type":74},"A prototype evaluation in a testbed demonstrates substantial benefits, including improved application performance while enabling higher application colocation on the same cluster and maintaining acceptable response times.","https://schema.org",{"og:url":50,"og:type":85,"og:title":13,"og:site_name":57,"og:description":14},"article",{"robots":87,"canonical":50},"index,follow",{"doc_id":7,"site_id":30}]