This repository provides Azure implementation of Kubernetes cloud provider interface. The in-tree cloud provider has been deprecated since v1.20 and only the bug fixes were allowed in the Kubernetes repository directory.
cloud-provider-azure
has been GA since v1.0.0 and its releases are maintained on Microsoft Container Registry (MCR).
The latest version of azure-cloud-controller-manager and azure-cloud-node-manager could be found at
mcr.microsoft.com/oss/kubernetes/azure-cloud-controller-manager:v1.1.1
mcr.microsoft.com/oss/kubernetes/azure-cloud-node-manager:v1.1.1
Version matrix:
Kubernetes version | cloud-provider version | cloud-provider branch |
---|---|---|
master | N/A | master |
v1.22.x | v1.1.1 | release-1.1 |
v1.21.x | v1.0.5 | release-1.0 |
v1.20.x | v0.7.8 | release-0.7 |
v1.19.x | v0.6.0 | release-0.6 |
v1.18.x | v0.5.1 | release-0.5 |
v1.17.x | v0.4.1 | N/A |
v1.16.x | v0.3.0 | N/A |
v1.15.x | v0.2.0 | N/A |
Build binary for azure-cloud-controller-manager:
make all
Build docker image for azure-cloud-controller-manager:
IMAGE_REGISTRY=<registry> make image
Run azure-cloud-controller-manager locally:
azure-cloud-controller-manager \
--cloud-provider=azure \
--cluster-name=kubernetes \
--controllers=*,-cloud-node \
--cloud-config=/etc/kubernetes/azure.json \
--kubeconfig=/etc/kubernetes/kubeconfig \
--allocate-node-cidrs=true \
--configure-cloud-routes=true \
--cluster-cidr=10.240.0.0/16 \
--route-reconciliation-period=10s \
--leader-elect=true \
--port=10267 \
--v=2
Run azure-cloud-node-manager locally:
azure-cloud-node-manager \
--node-name=$(hostname) \
--wait-routes=true
It is recommended to run azure-cloud-controller-manager as Pods on master nodes. See here for the example.
Please checkout more details at Deploy Cloud Controller Manager.
Please check the following documents for e2e tests:
See kubernetes-sigs.github.io/cloud-provider-azure for more documentations.
Please see CONTRIBUTING.md for instructions on how to contribute.
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.
当 Kubernetes 集群运行在云平台内部时,Cloud Provider 使得 Kubernetes 可以直接利用云平台实现持久化卷、负载均衡、网络路由、DNS 解析以及横向扩展等功能。 常见 Cloud Provider Kubenretes 内置的 Cloud Provider 包括 GCE AWS Azure Mesos OpenStack CloudStack Ovirt Photo
但当我的代码调用提供程序时,将foo作为任何文本,wiremock返回: 如何构建一个与请求体响应相同参数的契约? 编辑 也许不支持从请求获取正则表达式值?
As noted throughout this documentation, Flarum uses Laravel's service container (or IoC container) for dependency injection. Service Providers allow low-level configuration and modification of the Fla
12.Content Provider 比方说,你的设备里可能已经有了一个庞大的联系人数据库。联系人应用可以查看它们,拨号应用也可以,有些设备(比如HTC)还带着不同版本的联系人应用与拨号应用。既然都需要用到联系人数据,如果它们各自使用独立数据库的话,事情就会比较麻烦。 Content Provider 提供了一个统一的存储接口,允许多个程序访问同一个数据源。在联系人的这个例子里,还有个应用程序在
A module for accessing the user's MetaMask provider from other WebExtensions. The account provided by this provider will be the user's MetaMask account. When sending signing requests to this provider,
::: tip Attention MetaMask Users If you are a MetaMask user attempting to use a legacy Ethereum website that hasn't migrated to the new API, please see the section on the MetaMask Legacy Web3 Extensio