Skip to content

Commit

Permalink
upgrade-to-ubuntu-24.04
Browse files Browse the repository at this point in the history
  • Loading branch information
easystartup-io committed Jul 15, 2024
1 parent 289659a commit 718a676
Show file tree
Hide file tree
Showing 7 changed files with 9 additions and 9 deletions.
6 changes: 3 additions & 3 deletions README-OLD.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ schedule_workloads_on_masters: false
# cluster_dns: 10.43.0.10 # optional: IPv4 Cluster IP for coredns service. Needs to be an address from the service_cidr range
# enable_public_net_ipv4: false # default is true
# enable_public_net_ipv6: false # default is true
# image: rocky-9 # optional: default is ubuntu-22.04
# image: rocky-9 # optional: default is ubuntu-24.04
# autoscaling_image: 103908130 # optional, defaults to the `image` setting
# snapshot_os: microos # otional: specified the os type when using a custom snapshot
cloud_controller_manager_manifest_url: "https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/download/v1.18.0/ccm-networks.yaml"
Expand Down Expand Up @@ -166,10 +166,10 @@ information and instructions.

### Using alternative OS images

By default, the image in use is `ubuntu-22.04` for all the nodes, but you can specify a different default image with the
By default, the image in use is `ubuntu-24.04` for all the nodes, but you can specify a different default image with the
root level `image` config option or even different images for different static node pools by setting the `image` config
option in each node pool. This way you can, for example, have some node pools with ARM instances use the correct OS
image for ARM. To do this and use say Ubuntu 22.04 on ARM instances, set `image` to `103908130` with a specific image
image for ARM. To do this and use say Ubuntu 24.04 on ARM instances, set `image` to `103908130` with a specific image
ID. With regard to autoscaling, due to a limitation in the Cluster Autoscaler for Hetzner it is not possible yet to
specify a different image for each autoscaled pool, so for now you can specify the image for all autoscaled pools by
setting the `autoscaling_image` setting if you want to use an image different from the one specified in `image`.
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/autoscaling-nodes.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ For autoscaling nodes I have used the official kubernetes [Cluster Autoscaler fo
```

:::warning
If you dont specify the above images, the default fallback order is `autoscaling_image` -> `image` -> `ubuntu-22.04`
If you dont specify the above images, the default fallback order is `autoscaling_image` -> `image` -> `ubuntu-24.04`
:::

There is a limitation in the official hetzner kuberentes controller where you cannot set custom images for each autoscaled node group. Currently you can only only set a default image for all arm instances and all x86 instances. In the future when support will be added, this tool will also use the image present in the node pool.
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/config-reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ title: Config Reference Guide
| private_network_subnet | 10.0.0.0/16 | Subnet for the private network. Ensure this doesn't overlap with other networks in the same project. |
| schedule_workloads_on_masters | false | Determines whether workloads can be scheduled on master nodes. |
| worker_node_pools | | Configuration for worker node pools, including names, instance types, counts, locations, and autoscaling configurations. |
| image | "ubuntu-22.04" | The default OS image for nodes. |
| image | "ubuntu-24.04" | The default OS image for nodes. |
| snapshot_os | "default" | OS type when using a custom snapshot for the node image. |
| enable_encryption | false | Enable encryption for data at rest. |
| additional_packages | | Array of additional packages to install on cluster nodes. |
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/getting-started/create-your-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ disable_flannel: false # set to true if you want to install a different CNI
# private_api_load_balancer: true # default is false, if you want to use a private api load balancer, ensure that its accessible from where you are running executing this config
# api_server_hostname: testcluster.example.com # DNS for the k8s API LoadBalancer. Only enable after you have run the create command at least once and done the dns mapping to the private ip or public ip of the load balancer . Else the kubectl command will dns timeout

# image: rocky-9 # optional: default is ubuntu-22.04
# image: rocky-9 # optional: default is ubuntu-24.04

# autoscaling_image: #deprecated, instead use the below two options # 103908130 # defaults to the `image` setting

Expand Down
2 changes: 1 addition & 1 deletion docs/docs/private-setup-guide/setup-access-box.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ accessBoxConfig:
```

:::info
Currently only ubuntu 22.04 based access-box can be created, because the installation scripts are only supported for it. For other env please create your own access box or please help in contributing.
Currently only ubuntu 24.04 based access-box can be created, because the installation scripts are only supported for it. For other env please create your own access box or please help in contributing.
:::

### 2. Run the command to create the access box
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/private-setup-guide/setup-nat-gateway.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ natGatewayConfig:
// highlight-end
```
:::info
Currently only ubuntu 22.04 based nat-gateway can be created, because the installation scripts are only supported for it. For other env please create your own nat gateway or please help in contributing.
Currently only ubuntu 24.04 based nat-gateway can be created, because the installation scripts are only supported for it. For other env please create your own nat gateway or please help in contributing.
:::

### 2. Run the command to create the access box
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ public MainSettings() {
private String[] sshAllowedNetworks = {"0.0.0.0/0"};

@JsonProperty("image")
private String image ="ubuntu-22.04";
private String image ="ubuntu-24.04";

// Deprecated, only for use with v1
@JsonProperty("autoscaling_image")
Expand Down

0 comments on commit 718a676

Please sign in to comment.