kube-scheduler配置的示例分析
发表于:2025-01-25 作者:千家信息网编辑
千家信息网最后更新 2025年01月25日,这篇文章将为大家详细讲解有关kube-scheduler配置的示例分析,小编觉得挺实用的,因此分享给大家做个参考,希望大家阅读完这篇文章后可以有所收获。version: kubernetes 1.6.
千家信息网最后更新 2025年01月25日kube-scheduler配置的示例分析
这篇文章将为大家详细讲解有关kube-scheduler配置的示例分析,小编觉得挺实用的,因此分享给大家做个参考,希望大家阅读完这篇文章后可以有所收获。
version: kubernetes 1.6.2
##kube-scheduler Configuration
下面是我梳理的kube-scheduler的完成配置:
flag | default value | comments |
---|---|---|
--address string | 0.0.0.0 | The IP address to serve on (set to 0.0.0.0 for all interfaces) (default "0.0.0.0") |
--algorithm-provider string | DefaultProvider | The scheduling algorithm provider to use, one of: DefaultProvider |
--failure-domains string | kubernetes.io/hostname, failure-domain.beta.kubernetes.io/zone, failure-domain.beta.kubernetes.io/region | Indicate the "all topologies" set for an empty topologyKey when it's used for PreferredDuringScheduling pod anti-affinity. (default "kubernetes.io/hostname,failure-domain.beta.kubernetes.io/zone,failure-domain.beta.kubernetes.io/region") |
--feature-gates value | A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: AllAlpha=true | |
--google-json-key string | The Google Cloud Platform Service Account JSON Key to use for authentication. | |
--hard-pod-affinity-symmetric-weight int | 1 | RequiredDuringScheduling affinity is not symmetric, but there is an implicit PreferredDuringScheduling affinity rule corresponding to every RequiredDuringScheduling affinity rule. --hard-pod-affinity-symmetric-weight represents the weight of implicit PreferredDuringScheduling affinity rule. (default 1) |
--kube-api-burst value | 100 | Burst to use while talking with kubernetes apiserver (default 100) |
--kube-api-content-type string | application/vnd.kubernetes.protobuf | Content type of requests sent to apiserver. (default "application/vnd.kubernetes.protobuf") |
--kube-api-qps value | 50 | QPS to use while talking with kubernetes apiserver (default 50) |
--kubeconfig string | Path to kubeconfig file with authorization and master location information. | |
--leader-elect | true | Start a leader election client and gain leadership before executing the main loop. Enable this when running replicated components for high availability. (default true) |
--leader-elect-lease-duration duration | 15s | The duration that non-leader candidates will wait after observing a leadership renewal until attempting to acquire leadership of a led but unrenewed leader slot. This is effectively the maximum duration that a leader can be stopped before it is replaced by another candidate. This is only applicable if leader election is enabled. (default 15s) |
--leader-elect-renew-deadline duration | 10s | The interval between attempts by the acting master to renew a leadership slot before it stops leading. This must be less than or equal to the lease duration. This is only applicable if leader election is enabled. (default 10s) |
--leader-elect-retry-period duration | 2s | The duration the clients should wait between attempting acquisition and renewal of a leadership. This is only applicable if leader election is enabled. (default 2s) |
--master string | The address of the Kubernetes API server (overrides any value in kubeconfig) | |
--policy-config-file string | File with scheduler policy configuration | |
--port value | 10251 | The port that the scheduler's http service runs on (default 10251) |
--profiling | true | Enable profiling via web interface host:port/debug/pprof/ (default true) |
--scheduler-name string | default-scheduler | Name of the scheduler, used to select which pods will be processed by this scheduler, based on pod's annotation with key 'scheduler.alpha.kubernetes.io/name' (default "default-scheduler") |
kube-scheduler Configuration Best Practices
下面是我梳理的,个人认为必须关注的配置:
flag | default value | comments |
---|---|---|
--address string | 0.0.0.0 | The IP address to serve on (set to 0.0.0.0 for all interfaces) (default "0.0.0.0") |
--kubeconfig string | Path to kubeconfig file with authorization and master location information. | |
--master string | The address of the Kubernetes API server (overrides any value in kubeconfig) | |
--policy-config-file string | File with scheduler policy configuration | |
--port value | 10251 | The port that the scheduler's http service runs on (default 10251) |
--profiling | true | Enable profiling via web interface host:port/debug/pprof/ (default true) |
关于"kube-scheduler配置的示例分析"这篇文章就分享到这里了,希望以上内容可以对大家有一定的帮助,使各位可以学到更多知识,如果觉得文章不错,请把它分享出去让更多的人看到。
配置
篇文章
示例
分析
更多
不错
实用
个人
内容
文章
知识
参考
帮助
有关
数据库的安全要保护哪些东西
数据库安全各自的含义是什么
生产安全数据库录入
数据库的安全性及管理
数据库安全策略包含哪些
海淀数据库安全审计系统
建立农村房屋安全信息数据库
易用的数据库客户端支持安全管理
连接数据库失败ssl安全错误
数据库的锁怎样保障安全
设备状态监测与故障诊断数据库
服务器开发讲解视频
血源连不上服务器
广州直播软件开发一个多少钱
网络安全 打击
矢量网络技术重庆有限责任公司
佛山金融软件开发订制
徐州暑假网络安全课堂下载
诺基亚是不是没有服务器了
黑龙江立体化软件开发发展现状
网络安全小故事视频
武汉oa软件开发哪家好
数据库建立重要性
安卓的软件开发服务流程
内蒙算力服务器租赁费用
网络安全日的会议记录
桂阳软件开发工程师学费多少
lol服务器无法定位
抖音特效什么软件开发
软件开发中专学校广东有哪些
河北公安网络安全稽查处
社交网络技术传播方式
hutool 查数据库表结构
联通dns服务器盐城
小爱音箱云端服务器崩溃
服务端软件开发工程师
pb 如何连接数据库
小程序的软件开发多少算合理
浙江电网网络安全宣传活动
招聘考试数据库考试题及答案