[DO-1431] upgrade prod k8s (!6)
DO-1431 Co-authored-by: denis.patrakeev <denis.patrakeev@avroid.tech> Reviewed-on: https://git.avroid.tech/K8s/k8s-deploy/pulls/6
This commit is contained in:
@@ -43,9 +43,7 @@ upstream_dns_servers:
|
||||
|
||||
## There are some changes specific to the cloud providers
|
||||
## for instance we need to encapsulate packets with some network plugins
|
||||
## If set the possible values are either 'gce', 'aws', 'azure', 'openstack', 'vsphere', 'oci', or 'external'
|
||||
## When openstack is used make sure to source in the openstack credentials
|
||||
## like you would do when using openstack-client before starting the playbook.
|
||||
## If set the possible values only 'external' after K8s v1.31.
|
||||
# cloud_provider:
|
||||
|
||||
## When cloud_provider is set to 'external', you can set the cloud controller to deploy
|
||||
@@ -76,8 +74,8 @@ upstream_dns_servers:
|
||||
# skip_http_proxy_on_os_packages: false
|
||||
|
||||
## Since workers are included in the no_proxy variable by default, docker engine will be restarted on all nodes (all
|
||||
## pods will restart) when adding or removing workers. To override this behaviour by only including master nodes in the
|
||||
## no_proxy variable, set below to true:
|
||||
## pods will restart) when adding or removing workers. To override this behaviour by only including control plane nodes
|
||||
## in the no_proxy variable, set below to true:
|
||||
no_proxy_exclude_workers: false
|
||||
|
||||
## Certificate Management
|
||||
|
||||
@@ -81,7 +81,7 @@ containerd_registries_mirrors:
|
||||
capabilities: [ "pull", "resolve" ]
|
||||
skip_verify: false
|
||||
|
||||
# containerd_max_container_log_line_size: -1
|
||||
# containerd_max_container_log_line_size: 16384
|
||||
|
||||
# containerd_registry_auth:
|
||||
# - registry: 10.0.0.2:5000
|
||||
|
||||
Reference in New Issue
Block a user