Skip to content

Commit

Permalink
Merge pull request #1009 from maggie44/patch-1
Browse files Browse the repository at this point in the history
Remove warnings about missing EU arm server types from kube.tf.example
  • Loading branch information
mysticaltech authored Oct 11, 2023
2 parents 910497b + e84c637 commit 25d47b4
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions kube.tf.example
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,6 @@ module "kube-hetzner" {

# Please note that changing labels and taints after the first run will have no effect. If needed, you can do that through Kubernetes directly.

# ⚠️ When choosing ARM cax* server types, for the moment they are only available in fsn1 and hel1.
# Multi-architecture clusters are OK for most use cases, as container underlying images tend to be multi-architecture too.

# * Example below:
Expand Down Expand Up @@ -207,7 +206,7 @@ module "kube-hetzner" {
floating_ip = true
count = 1
},
# Arm based nodes, currently available only in FSN and HEL locations
# Arm based nodes
{
name = "agent-arm-small",
server_type = "cax11",
Expand Down Expand Up @@ -265,7 +264,6 @@ module "kube-hetzner" {
# By default we set a compatible version with the default initial_k3s_channel, to set another one,
# have a look at the tag value in https://github.com/kubernetes/autoscaler/blob/master/charts/cluster-autoscaler/values.yaml
# ⚠️ Based on how the autoscaler works with this project, you can only choose either x86 instances or ARM server types for ALL autoscaler nodepools.
# Also, as mentioned above, for the time being ARM cax* instances are only available in fsn1.
# If you are curious, it's ok to have a multi-architecture cluster, as most underlying container images are multi-architecture too.
# * Example below:
# autoscaler_nodepools = [
Expand Down

0 comments on commit 25d47b4

Please sign in to comment.