webdevops/azure-k8s-autopilot Docker 镜像 - 轩辕镜像 | Docker 镜像高效稳定拉取服务
webdevops/azure-k8s-autopilotwebdevops
K8S operator for Azure VMSS/VM for automatic repair and update
下载次数: 0状态：社区镜像维护者：webdevops仓库类型：镜像最近更新：1 天前
Azurer Kubernetes Autopilot
- auto update (update VMSS instances automatically to latest model; only VMSS)
Supports Azure AKS and custom Azure Kubernetes clusters.
Supports shoutrrr notifications.
(Successor of azure-k8s-autorepair)
Configuration
Usage: azure-k8s-autopilot [OPTIONS] Application Options: --dry-run Dry run (no redeploy triggered) [$DRY_RUN] --instance.nodename= Name of node where autopilot is running [$INSTANCE_NODENAME] --instance.namespace= Name of namespace where autopilot is running [$INSTANCE_NAMESPACE] --instance.pod= Name of pod where autopilot is running [$INSTANCE_POD] --debug debug mode [$DEBUG] -v, --verbose verbose mode [$VERBOSE] --log.json Switch log output to json format [$LOG_JSON] --repautoscaler.scaledown-locktime= Prevents cluster autoscaler from scaling down the affected node after update and repair (default: 60m) [$AUTOSCALER_SCALEDOWN_LOCKTIME] --kube.node.labelselector= Node Label selector which nodes should be checked [$KUBE_NODE_LABELSELECTOR] --lease.enable Enable lease (leader election; enabled by default in docker images) [$LEASE_ENABLE] --lease.name= Name of lease lock (default: azure-k8s-autopilot-leader) [$LEASE_NAME] --repair.crontab= Crontab of check runs (default: @every 2m) [$REPAIR_CRONTAB] --repair.notready-threshold= Threshold (duration) when the automatic repair should be tried (eg. after 10 mins of NotReady state after last successfull heartbeat) (default: 10m) [$REPAIR_NOTREADY_THRESHOLD] --repair.concurrency= How many VMs should be redeployed concurrently (default: 1) [$REPAIR_CONCURRENCY] --repair.lock-duration= Duration how long should be waited for another redeploy (default: 30m) [$REPAIR_LOCK_DURATION] --repair.lock-duration-error= Duration how long should be waited for another redeploy in case an error occurred (default: 5m) [$REPAIR_LOCK_DURATION_ERROR] --repair.azure.vmss.action=[restart|redeploy|reimage] Defines the action which should be tried to repair the node (VMSS) (default: redeploy) [$REPAIR_AZURE_VMSS_ACTION] --repair.azure.vm.action=[restart|redeploy] Defines the action which should be tried to repair the node (VM) (default: redeploy) [$REPAIR_AZURE_VM_ACTION] --repair.azure.provisioningstate= Azure VM provisioning states where repair should be tried (eg. avoid repair in "upgrading" state; "*" to accept all states) (default: succeeded, failed) [$REPAIR_AZURE_PROVISIONINGSTATE] --repair.lock-annotation= Node annotation for repair lock time (default: autopilot.webdevops.io/repair-lock) [$REPAIR_LOCK_ANNOTATION] --update.crontab= Crontab of check runs (default: @every 15m) [$UPDATE_CRONTAB] --update.concurrency= How many VMs should be updated concurrently (default: 1) [$UPDATE_CONCURRENCY] --update.lock-duration= Duration how long should be waited for another update (default: 15m) [$UPDATE_LOCK_DURATION] --update.lock-duration-error= Duration how long should be waited for another update in case an error occurred (default: 5m) [$UPDATE_LOCK_DURATION_ERROR] --update.lock-annotation= Node annotation for update lock time (default: autopilot.webdevops.io/update-lock) [$UPDATE_LOCK_ANNOTATION] --update.ongoing-annotation= Node annotation for ongoing update lock (default: autopilot.webdevops.io/update-ongoing) [$UPDATE_ONGOING_ANNOTATION] --update.exclude-annotation= Node annotation for excluding node for updates (default: autopilot.webdevops.io/exclude) [$UPDATE_EXCLUDE_ANNOTATION] --update.azure.vmss.action=[update|update+reimage] Defines the action which should be tried to update the node (VMSS) (default: update+reimage) [$UPDATE_AZURE_VMSS_ACTION] --update.azure.provisioningstate= Azure VM provisioning states where update should be tried (eg. avoid repair in "upgrading" state; "*" to accept all states) (default: succeeded, failed) [$UPDATE_AZURE_PROVISIONINGSTATE] --update.failed-threshold= Failed node threshold when node update is stopped (default: 2) [$UPDATE_FAILED_THRESHOLD] --drain.kubectl= Path to kubectl binary (default: kubectl) [$DRAIN_KUBECTL] --drain.enable Enable drain handling [$DRAIN_ENABLE] --drain.delete-local-data Continue even if there are pods using emptyDir (local data that will be deleted when the node is drained) [$DRAIN_DELETE_LOCAL_DATA] --drain.force Continue even if there are pods not managed by a ReplicationController, ReplicaSet, Job, DaemonSet or StatefulSet [$DRAIN_FORCE] --drain.grace-period= Period of time in seconds given to each pod to terminate gracefully. If negative, the default value specified in the pod will be used. [$DRAIN_GRACE_PERIOD] --drain.ignore-daemonsets Ignore DaemonSet-managed pods. [$DRAIN_IGNORE_DAEMONSETS] --drain.pod-selector= Label selector to filter pods on the node [$DRAIN_POD_SELECTOR] --drain.timeout= The length of time to wait before giving up, zero means infinite (default: 0s) [$DRAIN_TIMEOUT] --drain.wait-after= Wait after drain to let Kubernetes detach volumes etc (default: 30s) [$DRAIN_WAIT_AFTER] --drain.dry-run Do not drain, uncordon or label any node [$DRAIN_DRY_RUN] --notification= Shoutrrr url for notifications (https://containrrr.github.io/shoutrrr/) [$NOTIFICATION] --bind= Server address (default: :8080) [$SERVER_BIND] Help Options: -h, --help Show this help message
for Azure API authentication (using ENV vars) see [***]
for Kubernetes ServiceAccont is discoverd automatically (or you can use env path KUBECONFIG to specify path to your kubeconfig file)
Metrics
(see :8080/metrics)
| Metric | Description |
|---|---|
autopilot_repair_count | Count of repair actions |
autopilot_repair_node_status | Node status |
autopilot_repair_duration | Duration of repair task |
autopilot_update_count | Count of update actions |
autopilot_update_duration | Duration of last exec |
bitnami/azure-cli
Bitnami Secure Images（VMware Tanzu）
Bitnami安全镜像，用于安全运行Azure CLI工具。
12 次收藏1亿+ 次下载
6 个月前更新
cimg/azure
cimg
CircleCI Azure便捷镜像，用于在CircleCI环境中集成Azure服务，提供预配置工具以简化Azure相关开发、部署与测试流程。
3 次收藏100万+ 次下载
1 年前更新
docker/ucp-azure-ip-allocator
Docker 官方工具与组件镜像
暂无描述
1000万+ 次下载
5 年前更新
paketobuildpacks/java-azure
paketobuildpacks
暂无描述
50万+ 次下载
1 年前更新
demisto/pwsh-azure
demisto
暂无描述
1万+ 次下载
9 个月前更新
mirantis/ucp-azure-ip-allocator
mirantis
暂无描述
100万+ 次下载
2 小时前更新
轩辕镜像配置手册
探索更多轩辕镜像的使用方法，找到最适合您系统的配置方式
Docker 配置
登录仓库拉取
通过 Docker 登录认证访问私有仓库
专属域名拉取
无需登录使用专属域名
K8s Containerd
Kubernetes 集群配置 Containerd
K3s
K3s 轻量级 Kubernetes 镜像加速
Dev Containers
VS Code Dev Containers 配置
Podman
Podman 容器引擎配置
Singularity/Apptainer
HPC 科学计算容器配置
其他仓库配置
ghcr、Quay、nvcr 等镜像仓库
Harbor 镜像源配置
Harbor Proxy Repository 对接专属域名
Portainer 镜像源配置
Portainer Registries 加速拉取
Nexus 镜像源配置
Nexus3 Docker Proxy 内网缓存
系统配置
需要其他帮助？请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
镜像拉取常见问题
使用与功能问题
错误码与失败问题
docker pull 提示 manifest unknown 怎么办？
manifest unknown
docker pull 提示 no matching manifest 怎么办？
no matching manifest（架构）
镜像已拉取完成，却提示 invalid tar header 或 failed to register layer 怎么办？
invalid tar header（解压）
Docker pull 时 HTTPS / TLS 证书验证失败怎么办？
TLS 证书失败
Docker pull 时 DNS 解析超时或连不上仓库怎么办？
DNS 超时
Docker 拉取出现 410 Gone 怎么办？
410 Gone 排查
出现 402 或「流量用尽」提示怎么办？
402 与流量用尽
Docker 拉取提示 UNAUTHORIZED（401）怎么办？
401 认证失败
遇到 429 Too Many Requests（请求太频繁）怎么办？
429 限流
docker login 提示 Cannot autolaunch D-Bus，还算登录成功吗？
D-Bus 凭证提示
为什么会出现「单层超过 20GB」或 413，无法加速拉取？
413 与超大单层
账号 / 计费 / 权限
用户好评
来自真实用户的反馈，见证轩辕镜像的优质服务
oldzhang
运维工程师
Linux服务器
5
"Docker访问体验非常流畅，大镜像也能快速完成下载。"