public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-26 13:08:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1711 from rancher/main

Browse Source 
Syncing Main Branch into v2.11.0 Branch
This commit is contained in:
Sunil Singh
2025-03-17 17:21:29 -07:00
committed by GitHub
parent d97217c6f6 af896b7aba
commit b93f050ea7
8 changed files with 536 additions and 536 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/azure.md
+67 -67
View File
@@ -193,74 +193,74 @@ stringData:
4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**. 4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**.
Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/). Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/).
Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli). Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli).
```yaml ```yaml
apiVersion: helm.cattle.io/v1 apiVersion: helm.cattle.io/v1
kind: HelmChart kind: HelmChart
metadata: metadata:
name: azure-cloud-controller-manager name: azure-cloud-controller-manager
namespace: kube-system namespace: kube-system
spec: spec:
chart: cloud-provider-azure chart: cloud-provider-azure
repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo
targetNamespace: kube-system targetNamespace: kube-system
bootstrap: true bootstrap: true
valuesContent: |- valuesContent: |-
infra: infra:
clusterName: <cluster-name> clusterName: <cluster-name>
cloudControllerManager: cloudControllerManager:
cloudConfigSecretName: azure-cloud-config cloudConfigSecretName: azure-cloud-config
cloudConfig: null cloudConfig: null
clusterCIDR: null clusterCIDR: null
enableDynamicReloading: 'true' enableDynamicReloading: 'true'
nodeSelector: nodeSelector:
node-role.kubernetes.io/control-plane: 'true' node-role.kubernetes.io/control-plane: 'true'
allocateNodeCidrs: 'false' allocateNodeCidrs: 'false'
hostNetworking: true hostNetworking: true
caCertDir: /etc/ssl caCertDir: /etc/ssl
configureCloudRoutes: 'false' configureCloudRoutes: 'false'
enabled: true enabled: true
tolerations: tolerations:
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/master key: node-role.kubernetes.io/master
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/control-plane key: node-role.kubernetes.io/control-plane
value: 'true' value: 'true'
- effect: NoSchedule - effect: NoSchedule
key: node.cloudprovider.kubernetes.io/uninitialized key: node.cloudprovider.kubernetes.io/uninitialized
value: 'true' value: 'true'
--- ---
apiVersion: v1 apiVersion: v1
kind: Secret kind: Secret
metadata: metadata:
name: azure-cloud-config name: azure-cloud-config
namespace: kube-system namespace: kube-system
type: Opaque type: Opaque
stringData: stringData:
cloud-config: |- cloud-config: |-
{ {
"cloud": "AzurePublicCloud", "cloud": "AzurePublicCloud",
"tenantId": "<tenant-id>", "tenantId": "<tenant-id>",
"subscriptionId": "<subscription-id>", "subscriptionId": "<subscription-id>",
"aadClientId": "<client-id>", "aadClientId": "<client-id>",
"aadClientSecret": "<tenant-id>", "aadClientSecret": "<tenant-id>",
"resourceGroup": "docker-machine", "resourceGroup": "docker-machine",
"location": "westus", "location": "westus",
"subnetName": "docker-machine", "subnetName": "docker-machine",
"securityGroupName": "rancher-managed-kqmtsjgJ", "securityGroupName": "rancher-managed-kqmtsjgJ",
"securityGroupResourceGroup": "docker-machine", "securityGroupResourceGroup": "docker-machine",
"vnetName": "docker-machine-vnet", "vnetName": "docker-machine-vnet",
"vnetResourceGroup": "docker-machine", "vnetResourceGroup": "docker-machine",
"primaryAvailabilitySetName": "docker-machine", "primaryAvailabilitySetName": "docker-machine",
"routeTableResourceGroup": "docker-machine", "routeTableResourceGroup": "docker-machine",
"cloudProviderBackoff": false, "cloudProviderBackoff": false,
"useManagedIdentityExtension": false, "useManagedIdentityExtension": false,
"useInstanceMetadata": true, "useInstanceMetadata": true,
"loadBalancerSku": "standard", "loadBalancerSku": "standard",
"excludeMasterFromStandardLB": false, "excludeMasterFromStandardLB": false,
} }
``` ```
5. Click **Create** to submit the form and create the cluster. 5. Click **Create** to submit the form and create the cluster.
i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/azure.md
+67 -67
View File
@@ -175,74 +175,74 @@ stringData:
4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**. 4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**.
Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/). Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/).
Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli). Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli).
```yaml ```yaml
apiVersion: helm.cattle.io/v1 apiVersion: helm.cattle.io/v1
kind: HelmChart kind: HelmChart
metadata: metadata:
name: azure-cloud-controller-manager name: azure-cloud-controller-manager
namespace: kube-system namespace: kube-system
spec: spec:
chart: cloud-provider-azure chart: cloud-provider-azure
repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo
targetNamespace: kube-system targetNamespace: kube-system
bootstrap: true bootstrap: true
valuesContent: |- valuesContent: |-
infra: infra:
clusterName: <cluster-name> clusterName: <cluster-name>
cloudControllerManager: cloudControllerManager:
cloudConfigSecretName: azure-cloud-config cloudConfigSecretName: azure-cloud-config
cloudConfig: null cloudConfig: null
clusterCIDR: null clusterCIDR: null
enableDynamicReloading: 'true' enableDynamicReloading: 'true'
nodeSelector: nodeSelector:
node-role.kubernetes.io/control-plane: 'true' node-role.kubernetes.io/control-plane: 'true'
allocateNodeCidrs: 'false' allocateNodeCidrs: 'false'
hostNetworking: true hostNetworking: true
caCertDir: /etc/ssl caCertDir: /etc/ssl
configureCloudRoutes: 'false' configureCloudRoutes: 'false'
enabled: true enabled: true
tolerations: tolerations:
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/master key: node-role.kubernetes.io/master
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/control-plane key: node-role.kubernetes.io/control-plane
value: 'true' value: 'true'
- effect: NoSchedule - effect: NoSchedule
key: node.cloudprovider.kubernetes.io/uninitialized key: node.cloudprovider.kubernetes.io/uninitialized
value: 'true' value: 'true'
--- ---
apiVersion: v1 apiVersion: v1
kind: Secret kind: Secret
metadata: metadata:
name: azure-cloud-config name: azure-cloud-config
namespace: kube-system namespace: kube-system
type: Opaque type: Opaque
stringData: stringData:
cloud-config: |- cloud-config: |-
{ {
"cloud": "AzurePublicCloud", "cloud": "AzurePublicCloud",
"tenantId": "<tenant-id>", "tenantId": "<tenant-id>",
"subscriptionId": "<subscription-id>", "subscriptionId": "<subscription-id>",
"aadClientId": "<client-id>", "aadClientId": "<client-id>",
"aadClientSecret": "<tenant-id>", "aadClientSecret": "<tenant-id>",
"resourceGroup": "docker-machine", "resourceGroup": "docker-machine",
"location": "westus", "location": "westus",
"subnetName": "docker-machine", "subnetName": "docker-machine",
"securityGroupName": "rancher-managed-kqmtsjgJ", "securityGroupName": "rancher-managed-kqmtsjgJ",
"securityGroupResourceGroup": "docker-machine", "securityGroupResourceGroup": "docker-machine",
"vnetName": "docker-machine-vnet", "vnetName": "docker-machine-vnet",
"vnetResourceGroup": "docker-machine", "vnetResourceGroup": "docker-machine",
"primaryAvailabilitySetName": "docker-machine", "primaryAvailabilitySetName": "docker-machine",
"routeTableResourceGroup": "docker-machine", "routeTableResourceGroup": "docker-machine",
"cloudProviderBackoff": false, "cloudProviderBackoff": false,
"useManagedIdentityExtension": false, "useManagedIdentityExtension": false,
"useInstanceMetadata": true, "useInstanceMetadata": true,
"loadBalancerSku": "standard", "loadBalancerSku": "standard",
"excludeMasterFromStandardLB": false, "excludeMasterFromStandardLB": false,
} }
``` ```
5. Click **Create** to submit the form and create the cluster. 5. Click **Create** to submit the form and create the cluster.
i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/azure.md
+67 -67
View File
@@ -176,74 +176,74 @@ stringData:
4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**. 4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**.
Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/). Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/).
Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli). Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli).
```yaml ```yaml
apiVersion: helm.cattle.io/v1 apiVersion: helm.cattle.io/v1
kind: HelmChart kind: HelmChart
metadata: metadata:
name: azure-cloud-controller-manager name: azure-cloud-controller-manager
namespace: kube-system namespace: kube-system
spec: spec:
chart: cloud-provider-azure chart: cloud-provider-azure
repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo
targetNamespace: kube-system targetNamespace: kube-system
bootstrap: true bootstrap: true
valuesContent: |- valuesContent: |-
infra: infra:
clusterName: <cluster-name> clusterName: <cluster-name>
cloudControllerManager: cloudControllerManager:
cloudConfigSecretName: azure-cloud-config cloudConfigSecretName: azure-cloud-config
cloudConfig: null cloudConfig: null
clusterCIDR: null clusterCIDR: null
enableDynamicReloading: 'true' enableDynamicReloading: 'true'
nodeSelector: nodeSelector:
node-role.kubernetes.io/control-plane: 'true' node-role.kubernetes.io/control-plane: 'true'
allocateNodeCidrs: 'false' allocateNodeCidrs: 'false'
hostNetworking: true hostNetworking: true
caCertDir: /etc/ssl caCertDir: /etc/ssl
configureCloudRoutes: 'false' configureCloudRoutes: 'false'
enabled: true enabled: true
tolerations: tolerations:
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/master key: node-role.kubernetes.io/master
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/control-plane key: node-role.kubernetes.io/control-plane
value: 'true' value: 'true'
- effect: NoSchedule - effect: NoSchedule
key: node.cloudprovider.kubernetes.io/uninitialized key: node.cloudprovider.kubernetes.io/uninitialized
value: 'true' value: 'true'
--- ---
apiVersion: v1 apiVersion: v1
kind: Secret kind: Secret
metadata: metadata:
name: azure-cloud-config name: azure-cloud-config
namespace: kube-system namespace: kube-system
type: Opaque type: Opaque
stringData: stringData:
cloud-config: |- cloud-config: |-
{ {
"cloud": "AzurePublicCloud", "cloud": "AzurePublicCloud",
"tenantId": "<tenant-id>", "tenantId": "<tenant-id>",
"subscriptionId": "<subscription-id>", "subscriptionId": "<subscription-id>",
"aadClientId": "<client-id>", "aadClientId": "<client-id>",
"aadClientSecret": "<tenant-id>", "aadClientSecret": "<tenant-id>",
"resourceGroup": "docker-machine", "resourceGroup": "docker-machine",
"location": "westus", "location": "westus",
"subnetName": "docker-machine", "subnetName": "docker-machine",
"securityGroupName": "rancher-managed-kqmtsjgJ", "securityGroupName": "rancher-managed-kqmtsjgJ",
"securityGroupResourceGroup": "docker-machine", "securityGroupResourceGroup": "docker-machine",
"vnetName": "docker-machine-vnet", "vnetName": "docker-machine-vnet",
"vnetResourceGroup": "docker-machine", "vnetResourceGroup": "docker-machine",
"primaryAvailabilitySetName": "docker-machine", "primaryAvailabilitySetName": "docker-machine",
"routeTableResourceGroup": "docker-machine", "routeTableResourceGroup": "docker-machine",
"cloudProviderBackoff": false, "cloudProviderBackoff": false,
"useManagedIdentityExtension": false, "useManagedIdentityExtension": false,
"useInstanceMetadata": true, "useInstanceMetadata": true,
"loadBalancerSku": "standard", "loadBalancerSku": "standard",
"excludeMasterFromStandardLB": false, "excludeMasterFromStandardLB": false,
} }
``` ```
5. Click **Create** to submit the form and create the cluster. 5. Click **Create** to submit the form and create the cluster.
i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/azure.md
+67 -67
View File
@@ -176,74 +176,74 @@ stringData:
4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**. 4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**.
Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/). Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/).
Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli). Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli).
```yaml ```yaml
apiVersion: helm.cattle.io/v1 apiVersion: helm.cattle.io/v1
kind: HelmChart kind: HelmChart
metadata: metadata:
name: azure-cloud-controller-manager name: azure-cloud-controller-manager
namespace: kube-system namespace: kube-system
spec: spec:
chart: cloud-provider-azure chart: cloud-provider-azure
repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo
targetNamespace: kube-system targetNamespace: kube-system
bootstrap: true bootstrap: true
valuesContent: |- valuesContent: |-
infra: infra:
clusterName: <cluster-name> clusterName: <cluster-name>
cloudControllerManager: cloudControllerManager:
cloudConfigSecretName: azure-cloud-config cloudConfigSecretName: azure-cloud-config
cloudConfig: null cloudConfig: null
clusterCIDR: null clusterCIDR: null
enableDynamicReloading: 'true' enableDynamicReloading: 'true'
nodeSelector: nodeSelector:
node-role.kubernetes.io/control-plane: 'true' node-role.kubernetes.io/control-plane: 'true'
allocateNodeCidrs: 'false' allocateNodeCidrs: 'false'
hostNetworking: true hostNetworking: true
caCertDir: /etc/ssl caCertDir: /etc/ssl
configureCloudRoutes: 'false' configureCloudRoutes: 'false'
enabled: true enabled: true
tolerations: tolerations:
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/master key: node-role.kubernetes.io/master
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/control-plane key: node-role.kubernetes.io/control-plane
value: 'true' value: 'true'
- effect: NoSchedule - effect: NoSchedule
key: node.cloudprovider.kubernetes.io/uninitialized key: node.cloudprovider.kubernetes.io/uninitialized
value: 'true' value: 'true'
--- ---
apiVersion: v1 apiVersion: v1
kind: Secret kind: Secret
metadata: metadata:
name: azure-cloud-config name: azure-cloud-config
namespace: kube-system namespace: kube-system
type: Opaque type: Opaque
stringData: stringData:
cloud-config: |- cloud-config: |-
{ {
"cloud": "AzurePublicCloud", "cloud": "AzurePublicCloud",
"tenantId": "<tenant-id>", "tenantId": "<tenant-id>",
"subscriptionId": "<subscription-id>", "subscriptionId": "<subscription-id>",
"aadClientId": "<client-id>", "aadClientId": "<client-id>",
"aadClientSecret": "<tenant-id>", "aadClientSecret": "<tenant-id>",
"resourceGroup": "docker-machine", "resourceGroup": "docker-machine",
"location": "westus", "location": "westus",
"subnetName": "docker-machine", "subnetName": "docker-machine",
"securityGroupName": "rancher-managed-kqmtsjgJ", "securityGroupName": "rancher-managed-kqmtsjgJ",
"securityGroupResourceGroup": "docker-machine", "securityGroupResourceGroup": "docker-machine",
"vnetName": "docker-machine-vnet", "vnetName": "docker-machine-vnet",
"vnetResourceGroup": "docker-machine", "vnetResourceGroup": "docker-machine",
"primaryAvailabilitySetName": "docker-machine", "primaryAvailabilitySetName": "docker-machine",
"routeTableResourceGroup": "docker-machine", "routeTableResourceGroup": "docker-machine",
"cloudProviderBackoff": false, "cloudProviderBackoff": false,
"useManagedIdentityExtension": false, "useManagedIdentityExtension": false,
"useInstanceMetadata": true, "useInstanceMetadata": true,
"loadBalancerSku": "standard", "loadBalancerSku": "standard",
"excludeMasterFromStandardLB": false, "excludeMasterFromStandardLB": false,
} }
``` ```
5. Click **Create** to submit the form and create the cluster. 5. Click **Create** to submit the form and create the cluster.
i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/azure.md
+67 -67
View File
@@ -176,74 +176,74 @@ stringData:
4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**. 4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**.
Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/). Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/).
Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli). Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli).
```yaml ```yaml
apiVersion: helm.cattle.io/v1 apiVersion: helm.cattle.io/v1
kind: HelmChart kind: HelmChart
metadata: metadata:
name: azure-cloud-controller-manager name: azure-cloud-controller-manager
namespace: kube-system namespace: kube-system
spec: spec:
chart: cloud-provider-azure chart: cloud-provider-azure
repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo
targetNamespace: kube-system targetNamespace: kube-system
bootstrap: true bootstrap: true
valuesContent: |- valuesContent: |-
infra: infra:
clusterName: <cluster-name> clusterName: <cluster-name>
cloudControllerManager: cloudControllerManager:
cloudConfigSecretName: azure-cloud-config cloudConfigSecretName: azure-cloud-config
cloudConfig: null cloudConfig: null
clusterCIDR: null clusterCIDR: null
enableDynamicReloading: 'true' enableDynamicReloading: 'true'
nodeSelector: nodeSelector:
node-role.kubernetes.io/control-plane: 'true' node-role.kubernetes.io/control-plane: 'true'
allocateNodeCidrs: 'false' allocateNodeCidrs: 'false'
hostNetworking: true hostNetworking: true
caCertDir: /etc/ssl caCertDir: /etc/ssl
configureCloudRoutes: 'false' configureCloudRoutes: 'false'
enabled: true enabled: true
tolerations: tolerations:
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/master key: node-role.kubernetes.io/master
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/control-plane key: node-role.kubernetes.io/control-plane
value: 'true' value: 'true'
- effect: NoSchedule - effect: NoSchedule
key: node.cloudprovider.kubernetes.io/uninitialized key: node.cloudprovider.kubernetes.io/uninitialized
value: 'true' value: 'true'
--- ---
apiVersion: v1 apiVersion: v1
kind: Secret kind: Secret
metadata: metadata:
name: azure-cloud-config name: azure-cloud-config
namespace: kube-system namespace: kube-system
type: Opaque type: Opaque
stringData: stringData:
cloud-config: |- cloud-config: |-
{ {
"cloud": "AzurePublicCloud", "cloud": "AzurePublicCloud",
"tenantId": "<tenant-id>", "tenantId": "<tenant-id>",
"subscriptionId": "<subscription-id>", "subscriptionId": "<subscription-id>",
"aadClientId": "<client-id>", "aadClientId": "<client-id>",
"aadClientSecret": "<tenant-id>", "aadClientSecret": "<tenant-id>",
"resourceGroup": "docker-machine", "resourceGroup": "docker-machine",
"location": "westus", "location": "westus",
"subnetName": "docker-machine", "subnetName": "docker-machine",
"securityGroupName": "rancher-managed-kqmtsjgJ", "securityGroupName": "rancher-managed-kqmtsjgJ",
"securityGroupResourceGroup": "docker-machine", "securityGroupResourceGroup": "docker-machine",
"vnetName": "docker-machine-vnet", "vnetName": "docker-machine-vnet",
"vnetResourceGroup": "docker-machine", "vnetResourceGroup": "docker-machine",
"primaryAvailabilitySetName": "docker-machine", "primaryAvailabilitySetName": "docker-machine",
"routeTableResourceGroup": "docker-machine", "routeTableResourceGroup": "docker-machine",
"cloudProviderBackoff": false, "cloudProviderBackoff": false,
"useManagedIdentityExtension": false, "useManagedIdentityExtension": false,
"useInstanceMetadata": true, "useInstanceMetadata": true,
"loadBalancerSku": "standard", "loadBalancerSku": "standard",
"excludeMasterFromStandardLB": false, "excludeMasterFromStandardLB": false,
} }
``` ```
5. Click **Create** to submit the form and create the cluster. 5. Click **Create** to submit the form and create the cluster.
versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/azure.md
+67 -67
View File
@@ -194,74 +194,74 @@ stringData:
4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**. 4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**.
Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/). Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/).
Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli). Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli).
```yaml ```yaml
apiVersion: helm.cattle.io/v1 apiVersion: helm.cattle.io/v1
kind: HelmChart kind: HelmChart
metadata: metadata:
name: azure-cloud-controller-manager name: azure-cloud-controller-manager
namespace: kube-system namespace: kube-system
spec: spec:
chart: cloud-provider-azure chart: cloud-provider-azure
repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo
targetNamespace: kube-system targetNamespace: kube-system
bootstrap: true bootstrap: true
valuesContent: |- valuesContent: |-
infra: infra:
clusterName: <cluster-name> clusterName: <cluster-name>
cloudControllerManager: cloudControllerManager:
cloudConfigSecretName: azure-cloud-config cloudConfigSecretName: azure-cloud-config
cloudConfig: null cloudConfig: null
clusterCIDR: null clusterCIDR: null
enableDynamicReloading: 'true' enableDynamicReloading: 'true'
nodeSelector: nodeSelector:
node-role.kubernetes.io/control-plane: 'true' node-role.kubernetes.io/control-plane: 'true'
allocateNodeCidrs: 'false' allocateNodeCidrs: 'false'
hostNetworking: true hostNetworking: true
caCertDir: /etc/ssl caCertDir: /etc/ssl
configureCloudRoutes: 'false' configureCloudRoutes: 'false'
enabled: true enabled: true
tolerations: tolerations:
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/master key: node-role.kubernetes.io/master
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/control-plane key: node-role.kubernetes.io/control-plane
value: 'true' value: 'true'
- effect: NoSchedule - effect: NoSchedule
key: node.cloudprovider.kubernetes.io/uninitialized key: node.cloudprovider.kubernetes.io/uninitialized
value: 'true' value: 'true'
--- ---
apiVersion: v1 apiVersion: v1
kind: Secret kind: Secret
metadata: metadata:
name: azure-cloud-config name: azure-cloud-config
namespace: kube-system namespace: kube-system
type: Opaque type: Opaque
stringData: stringData:
cloud-config: |- cloud-config: |-
{ {
"cloud": "AzurePublicCloud", "cloud": "AzurePublicCloud",
"tenantId": "<tenant-id>", "tenantId": "<tenant-id>",
"subscriptionId": "<subscription-id>", "subscriptionId": "<subscription-id>",
"aadClientId": "<client-id>", "aadClientId": "<client-id>",
"aadClientSecret": "<tenant-id>", "aadClientSecret": "<tenant-id>",
"resourceGroup": "docker-machine", "resourceGroup": "docker-machine",
"location": "westus", "location": "westus",
"subnetName": "docker-machine", "subnetName": "docker-machine",
"securityGroupName": "rancher-managed-kqmtsjgJ", "securityGroupName": "rancher-managed-kqmtsjgJ",
"securityGroupResourceGroup": "docker-machine", "securityGroupResourceGroup": "docker-machine",
"vnetName": "docker-machine-vnet", "vnetName": "docker-machine-vnet",
"vnetResourceGroup": "docker-machine", "vnetResourceGroup": "docker-machine",
"primaryAvailabilitySetName": "docker-machine", "primaryAvailabilitySetName": "docker-machine",
"routeTableResourceGroup": "docker-machine", "routeTableResourceGroup": "docker-machine",
"cloudProviderBackoff": false, "cloudProviderBackoff": false,
"useManagedIdentityExtension": false, "useManagedIdentityExtension": false,
"useInstanceMetadata": true, "useInstanceMetadata": true,
"loadBalancerSku": "standard", "loadBalancerSku": "standard",
"excludeMasterFromStandardLB": false, "excludeMasterFromStandardLB": false,
} }
``` ```
5. Click **Create** to submit the form and create the cluster. 5. Click **Create** to submit the form and create the cluster.
versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/azure.md
+67 -67
View File
@@ -194,74 +194,74 @@ stringData:
4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**. 4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**.
Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/). Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/).
Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli). Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli).
```yaml ```yaml
apiVersion: helm.cattle.io/v1 apiVersion: helm.cattle.io/v1
kind: HelmChart kind: HelmChart
metadata: metadata:
name: azure-cloud-controller-manager name: azure-cloud-controller-manager
namespace: kube-system namespace: kube-system
spec: spec:
chart: cloud-provider-azure chart: cloud-provider-azure
repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo
targetNamespace: kube-system targetNamespace: kube-system
bootstrap: true bootstrap: true
valuesContent: |- valuesContent: |-
infra: infra:
clusterName: <cluster-name> clusterName: <cluster-name>
cloudControllerManager: cloudControllerManager:
cloudConfigSecretName: azure-cloud-config cloudConfigSecretName: azure-cloud-config
cloudConfig: null cloudConfig: null
clusterCIDR: null clusterCIDR: null
enableDynamicReloading: 'true' enableDynamicReloading: 'true'
nodeSelector: nodeSelector:
node-role.kubernetes.io/control-plane: 'true' node-role.kubernetes.io/control-plane: 'true'
allocateNodeCidrs: 'false' allocateNodeCidrs: 'false'
hostNetworking: true hostNetworking: true
caCertDir: /etc/ssl caCertDir: /etc/ssl
configureCloudRoutes: 'false' configureCloudRoutes: 'false'
enabled: true enabled: true
tolerations: tolerations:
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/master key: node-role.kubernetes.io/master
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/control-plane key: node-role.kubernetes.io/control-plane
value: 'true' value: 'true'
- effect: NoSchedule - effect: NoSchedule
key: node.cloudprovider.kubernetes.io/uninitialized key: node.cloudprovider.kubernetes.io/uninitialized
value: 'true' value: 'true'
--- ---
apiVersion: v1 apiVersion: v1
kind: Secret kind: Secret
metadata: metadata:
name: azure-cloud-config name: azure-cloud-config
namespace: kube-system namespace: kube-system
type: Opaque type: Opaque
stringData: stringData:
cloud-config: |- cloud-config: |-
{ {
"cloud": "AzurePublicCloud", "cloud": "AzurePublicCloud",
"tenantId": "<tenant-id>", "tenantId": "<tenant-id>",
"subscriptionId": "<subscription-id>", "subscriptionId": "<subscription-id>",
"aadClientId": "<client-id>", "aadClientId": "<client-id>",
"aadClientSecret": "<tenant-id>", "aadClientSecret": "<tenant-id>",
"resourceGroup": "docker-machine", "resourceGroup": "docker-machine",
"location": "westus", "location": "westus",
"subnetName": "docker-machine", "subnetName": "docker-machine",
"securityGroupName": "rancher-managed-kqmtsjgJ", "securityGroupName": "rancher-managed-kqmtsjgJ",
"securityGroupResourceGroup": "docker-machine", "securityGroupResourceGroup": "docker-machine",
"vnetName": "docker-machine-vnet", "vnetName": "docker-machine-vnet",
"vnetResourceGroup": "docker-machine", "vnetResourceGroup": "docker-machine",
"primaryAvailabilitySetName": "docker-machine", "primaryAvailabilitySetName": "docker-machine",
"routeTableResourceGroup": "docker-machine", "routeTableResourceGroup": "docker-machine",
"cloudProviderBackoff": false, "cloudProviderBackoff": false,
"useManagedIdentityExtension": false, "useManagedIdentityExtension": false,
"useInstanceMetadata": true, "useInstanceMetadata": true,
"loadBalancerSku": "standard", "loadBalancerSku": "standard",
"excludeMasterFromStandardLB": false, "excludeMasterFromStandardLB": false,
} }
``` ```
5. Click **Create** to submit the form and create the cluster. 5. Click **Create** to submit the form and create the cluster.
versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/azure.md
+67 -67
View File
@@ -194,74 +194,74 @@ stringData:
4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**. 4. Under **Cluster Configuration > Add-on Config**, add the cloud controller manager manifest shown below into **Additional Manifest**.
Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/). Note that this chart reads the Cloud Provider Config from the secret in the `kube-system` namespace. An example secret for the Cloud Provider Config is shown below; modify it as needed. Refer to the full list of configuration options in the [upstream docs](https://cloud-provider-azure.sigs.k8s.io/install/configs/).
Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli). Alternatively, you can also install the cloud controller manager using the [Helm CLI](#helm-chart-installation-from-cli).
```yaml ```yaml
apiVersion: helm.cattle.io/v1 apiVersion: helm.cattle.io/v1
kind: HelmChart kind: HelmChart
metadata: metadata:
name: azure-cloud-controller-manager name: azure-cloud-controller-manager
namespace: kube-system namespace: kube-system
spec: spec:
chart: cloud-provider-azure chart: cloud-provider-azure
repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo repo: https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo
targetNamespace: kube-system targetNamespace: kube-system
bootstrap: true bootstrap: true
valuesContent: |- valuesContent: |-
infra: infra:
clusterName: <cluster-name> clusterName: <cluster-name>
cloudControllerManager: cloudControllerManager:
cloudConfigSecretName: azure-cloud-config cloudConfigSecretName: azure-cloud-config
cloudConfig: null cloudConfig: null
clusterCIDR: null clusterCIDR: null
enableDynamicReloading: 'true' enableDynamicReloading: 'true'
nodeSelector: nodeSelector:
node-role.kubernetes.io/control-plane: 'true' node-role.kubernetes.io/control-plane: 'true'
allocateNodeCidrs: 'false' allocateNodeCidrs: 'false'
hostNetworking: true hostNetworking: true
caCertDir: /etc/ssl caCertDir: /etc/ssl
configureCloudRoutes: 'false' configureCloudRoutes: 'false'
enabled: true enabled: true
tolerations: tolerations:
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/master key: node-role.kubernetes.io/master
- effect: NoSchedule - effect: NoSchedule
key: node-role.kubernetes.io/control-plane key: node-role.kubernetes.io/control-plane
value: 'true' value: 'true'
- effect: NoSchedule - effect: NoSchedule
key: node.cloudprovider.kubernetes.io/uninitialized key: node.cloudprovider.kubernetes.io/uninitialized
value: 'true' value: 'true'
--- ---
apiVersion: v1 apiVersion: v1
kind: Secret kind: Secret
metadata: metadata:
name: azure-cloud-config name: azure-cloud-config
namespace: kube-system namespace: kube-system
type: Opaque type: Opaque
stringData: stringData:
cloud-config: |- cloud-config: |-
{ {
"cloud": "AzurePublicCloud", "cloud": "AzurePublicCloud",
"tenantId": "<tenant-id>", "tenantId": "<tenant-id>",
"subscriptionId": "<subscription-id>", "subscriptionId": "<subscription-id>",
"aadClientId": "<client-id>", "aadClientId": "<client-id>",
"aadClientSecret": "<tenant-id>", "aadClientSecret": "<tenant-id>",
"resourceGroup": "docker-machine", "resourceGroup": "docker-machine",
"location": "westus", "location": "westus",
"subnetName": "docker-machine", "subnetName": "docker-machine",
"securityGroupName": "rancher-managed-kqmtsjgJ", "securityGroupName": "rancher-managed-kqmtsjgJ",
"securityGroupResourceGroup": "docker-machine", "securityGroupResourceGroup": "docker-machine",
"vnetName": "docker-machine-vnet", "vnetName": "docker-machine-vnet",
"vnetResourceGroup": "docker-machine", "vnetResourceGroup": "docker-machine",
"primaryAvailabilitySetName": "docker-machine", "primaryAvailabilitySetName": "docker-machine",
"routeTableResourceGroup": "docker-machine", "routeTableResourceGroup": "docker-machine",
"cloudProviderBackoff": false, "cloudProviderBackoff": false,
"useManagedIdentityExtension": false, "useManagedIdentityExtension": false,
"useInstanceMetadata": true, "useInstanceMetadata": true,
"loadBalancerSku": "standard", "loadBalancerSku": "standard",
"excludeMasterFromStandardLB": false, "excludeMasterFromStandardLB": false,
} }
``` ```
5. Click **Create** to submit the form and create the cluster. 5. Click **Create** to submit the form and create the cluster.