Welcome to the previous releases section of our documentation portal for IONOS Cloud. This section is dedicated to archiving previous release notes for the year(s), excluding the latest release.

What's new

🎉Changes as of April 2, 2024

As part of our ongoing redesign, we have significantly enhanced its layout, appearance, and navigation to provide an unmatched user experience and improved visibility of our products and product categories. Consequently, you will observe changes in the product listing on the vertical navigation bar on the left side of this page.

We aim to improve the visibility of our functional products and make documentation easily discoverable. Our team has worked diligently to ensure these modifications align with the best practices in documentation portal design and user experience. The result is a documentation portal that offers our users a streamlined and efficient browsing experience.

What's new

What's new

What's new

What's new

What's new

What's new

At IONOS Cloud, we are committed to continuously improving our services to enhance your experience and safeguard your data. We are pleased to announce that on November 11, 2024, we implemented significant updates to our Identity and Access Management (IAM) Single Sign-On (SSO) login process, resulting in the redesign of the login screens. This change will not impact your data and no action is required at your end.

The updates are designed to increase security protocols to protect user data and streamline access. They will help ensure that IONOS Cloud continues to provide a secure, reliable, user-friendly platform and an improved login interface with faster response times.

The rollout is gradual and not instantaneous. You would have already noticed the changes to the , which went live on November 12, 2024. The transformation of the login screen will be implemented on November 18, 2024.

The change requires you to validate yourself in the following screens:  1. The first one requires your Email Address and Password.  2. The second screen requests the Time-based one-time password (TOTP) from your authenticator app if you have configured .

We recommend proceeding with your authentication as usual. This new login approach improves security by controlling the authentication and authorization of your accounts and makes logging into multiple applications much easier and safer by allowing you to use one set of credentials.

Users need appropriate privileges to create and manage data center. The group privilege called Create Data Center must be enabled for a group so that the members of this group inherit it through group privilege settings and can create and manage Virtual Data Center (VDCs).

To set user privileges to create and manage VDCs, follow these steps:

Manage your account and billing

To associate an SSH key with a Linux storage image of a VM, follow these steps:

1. Log in to the DCD with your credentials.

2. If a VM does not exist, drag a VM element (a Dedicated Core server, a vCPU Server, or a Cube) from the palette onto the workspace based on your needs. Else, you can choose to add storage to an existing VM.

3. Click + on the VM to attach storage.

1. Log in to the DCD with your username and password.

2. Choose a Cube. From the Settings tab in the Inspector pane, select Power > Resume.

3. Confirm your action by checking the appropriate box and clicking Apply RESUME.

What are Cubes?

For a long time, the duopoly of virtual private servers (VPS) and dedicated cloud servers dominated virtualized computing environments.

Enter Cubes — virtual private service instances — the next generation of IaaS. Developed by IONOS Cloud, Cubes are ideal for specific workloads that do not require high compute performance from all resources at all times — development and testing environments, website hosting, simple web applications, and so on.

While based on shared resources, the Cubes can rival physical servers through a platform design that can redistribute available performance capacities among individual instances. At the same time, reduced operational complexity and highly optimized resource utilization translate into lower operating costs.

Cubes instances come complete with vCPUs, RAM, and direct-attached NVMe storage volumes; choose among standard by selecting one of several

It is desirable to extend CoreDNS with additional configuration to make changes that survive control plane maintenance. It is possible to create a ConfigMap in the kube-system namespace. The ConfigMap must be named coredns-additional-conf and contain a data entry with the key extra.conf. The value of the entry must be a string containing the additional configuration.

The following example shows how to add a custom DNS entry for example.abc:

To associate an SSH key with a Linux storage image of a VM, follow these steps:

1. Log in to the DCD with your credentials.

2. If a VM does not exist, drag a VM element (a Dedicated Core server, a vCPU Server, or a Cube) from the palette onto the workspace based on your needs. Else, you can choose to add storage to an existing VM.

3. Click + on the VM to attach storage.

In IONOS Managed Kubernetes, a Public Node Pool provides a foundation for hosting applications and services that require external accessibility over the internet. These node pools consist of worker nodes that are exposed to the public network, enabling them to interact with external clients and services.

You can create Kubernetes clusters for Public Node Pools using the Configuration Management Tools or directly using the IONOS Cloud API.

Features

The key features related to Public Node Pools include:

• External Accessibility: Public Node Pools are designed to host workloads that need to be accessed from outside the Kubernetes cluster. This can include web applications, APIs, and other services that require internet connectivity.

• Load Balancing: Load balancers are used with IONOS Public Node Pools to distribute incoming traffic across multiple nodes. This helps to achieve high availability, scalability, and efficient resource utilization.

• Security: The Implementation of proper network policies, firewall rules, and user groups helps IONOS Public Node Pools mitigate potential risks and help in the protection of sensitive data.

• Scaling: The ability to dynamically scale the number of nodes in a Public Node Pool is crucial for handling varying levels of incoming traffic. This scalability ensures optimal performance during peak usage periods.

• Public Cloud Integration: Public Node Pools seamlessly integrate with IONOS Cloud services.

• Monitoring and Logging: Robust monitoring and logging solutions are essential for tracking the performance and health of applications hosted in Public Node Pools. This includes metrics related to traffic, resource utilization, and potential security incidents.

Explore our guides and reference documents to integrate IONOS Cloud products and services.

Documentation Spotlight

Set Up IONOS Cloud

Developer Reference

Product User Guides

AI

Compute Services

Containers

Data Analytics

Databases

Network Services

Observability

Storage & Backup

Security

What's new

AI Model Hub

Documentation updates

What's new

DCD Support for Cloud DNS

What's new

IONOS Telemetry API for Logging Service

What's new

New Object Storage Web Console (Beta)

What's new

Renamed Virtual Server to Dedicated Core Server

Documentation updates

To create a data center, use one of the following options:

Option 1: From the Data Center Designer menu

1. In the DCD, go to Menu > Data Center Designer. A drop-down window appears.

1. Provide the following details:

• Name: Enter a name to identify the data center uniquely.

• Description: (Optional) Add information that describes the .

• Region: From the drop-down list, choose the physical location of the data center that hosts your infrastructure.

1. Select Create Data Center to confirm.

Alternatively, you can also create a data center using the following options:

Option 2: From the DCD home page

• In the DCD, go to the My Virtual Data Centers section and click Create new.

• Provide the details to create a data center. For more information, see Step 2 in .

• Select Create Data Center to confirm.

Option 3: From the Start Center

• In the DCD, go to Menu > Data Center Designer and click Open Start Center.

• In the right-side of the Start Center screen under the Create Data Center section, provide the details to create the data center. For more information, see Step 2 in .

• Select Create Data Center to confirm.

Managed Kubernetes can be utilized to address the specific needs of its users. Here, you can find a list of common use cases and scenarios. Each use case is described in detail to highlight its relevance and benefits.

• Preserve Source Internet Protocol (IP) Address When Using Ingress

• Add Custom CoreDNS Configuration

• Horizontal Scaling of Network Traffic

What's new

Managed Stackable new version

The VM Auto Scaling Manager displays the list of all servers associated with the selected VM Auto Scaling Group. Each server is given a unique identification string as its name automatically.

To view the associated servers, follow these steps:

1. Log in to DCD with your username and password.

2. Go to Menu > Management > VM Auto Scaling.

3. Click Servers to view one of these:

   • click Console to open the remote console to access your VM.

   • clicking Focus Server opens the VDC and preselects the server automatically.

Managed Kubernetes provides a platform to automate the deployment, scaling, and management of containerized applications. With IONOS Cloud Managed Kubernetes, you can quickly set up Kubernetes clusters and manage Node Pools.

It offers a wide range of features for containerized applications without having to handle the underlying infrastructure details. It is a convenient solution for users who want to leverage the power of Kubernetes without dealing with the operational challenges of managing the cluster themselves.

Product Overview

DCD How-Tos

Frequently Asked Questions (FAQs)

To get answers to the most commonly encountered questions about Managed Kubernetes, see .

When you suspend a Cube, you turn off the server, but the Cube remains saved, and you can resume it later. The following occurs when you suspend a Cube:

• The Cube releases the associated CPU, RAM, and IP addresses and suspends their billing.

• The connected storage devices will be billed.

• The server does not remove the reserved IP addresses.

• A red cross marks the deallocated VM in the DCD.

To suspend a Cube, follow these steps:

1. Log in to the DCD with your username and password.

2. Select the appropriate Virtual Data Center associated with the Cube.

3. Click on the respective Cube in the Workspace.

4. From the Settings tab in the Inspector pane, select Power > Suspend.

Cubes are virtual private service instances with shared resources. Refer to our user guides, reference documentation, and FAQs to support your hosting needs.

Product Overview

Quick Links

Developer Tools

Frequently Asked Questions (FAQs)

To get answers to the most commonly encountered questions about Cubes, see .

With IONOS Cloud , you can quickly provision Dedicated Core servers and vCPU Servers. Leverage our user guides, reference documentation, and FAQs to support your hosting needs.

Product Overview

The IONOS AI Model Hub offers powerful AI capabilities to meet various needs. Here are five pivotal use cases you can implement with this service:

Use Case 1: Text Generation

Text generation models enable advanced language processing tasks, such as content creation, summarization, conversational responses, and question-answering. These models are pre-trained on extensive datasets, allowing for high-quality text generation with minimal setup.

Key Features:

The following are a few FAQs to provide an insight about renaming the product from Virtual Server(s) to Dedicated Core Server(s).

What is the reason for renaming "Virtual Servers" to "Dedicated Core Servers"?

The name change is part of our ongoing efforts to better reflect the performance and benefits of our Virtual Machines. "Dedicated Core Servers" emphasizes the dedicated nature of the compute resources assigned to each instance, ensuring consistent performance and increased reliability.

The DCD's SSH Keys view allows you to save and manage up to 100 public SSH keys for SSH access setup. This saves you from having to copy and paste the public part of an SSH key from an external source multiple times.

In addition to the SSH keys stored in the SSH Keys view, the IONOS SSH key concept supports for Dedicated Core servers, vCPU Servers, and Cubes.

Store SSH Keys in the DCD

To save your SSH key in the DCD, follow these steps:

After successfully configuring your VM Auto Scaling Groups, you can modify scaling thresholds and scaling policies, update replica configuration or associate an ALB via the VM Auto Scaling Manager.

To modify the values, follow these steps:

1. Log in to DCD with your username and password.

2. Go to Menu > Management > VM Auto Scaling.

The scale in and scale out operations performed by the VM Auto Scaling feature are displayed in a chronological order.

To view the list of operations and their statuses, follow these steps:

1. Log in to DCD with your username and password.

2. Go to Menu > Management > VM Auto Scaling.

Deletion of a VM Auto Scaling Group results in the deletion of all the VMs associated with the respective group.

To delete a group, follow these steps:

1. Log in to DCD with your username and password.

2. Go to Menu > Management > VM Auto Scaling.

In IONOS Managed Kubernetes, a Private Node Pool is a dedicated set of nodes within a Kubernetes cluster that is isolated for the exclusive use of a specific user, application, or organization. Private node pools of a cluster are deployed in a private network behind a NAT Gateway to enable connectivity from the nodes to the public internet but not vice-versa.

You can create Kubernetes clusters for Private Node Pools using the or directly using the . By using IONOS Kubernetes clusters for Private Node Pools, you can ensure the network traffic between your nodes and Kubernetes service stays on your private network only.

Features

The key features related to Private Node Pools include:

To generate SSH keys, ensure that you have ssh-keygen command-line tool installed. ssh-keygen is a utility for generating SSH key pairs and storing them in a secure location. With these keys, you can connect to your instances without encountering the login prompt. You can use the SSH keys on a macOS or a Linux using an SSH client.

You can manually generate SSH keys when working with a SSH client using the following:

1. Enter the following command into the terminal window on your computer and press ENTER.

To generate SSH keys, ensure that you have ssh-keygen command-line tool installed. ssh-keygen is a utility for generating SSH key pairs and storing them in a secure location. With these keys, you can connect to your instances without encountering the login prompt. You can use the SSH keys on a macOS or a Linux using an SSH client.

You can manually generate SSH keys when working with a SSH client using the following:

1. Enter the following command into the terminal window on your computer and press ENTER.

Some applications require a Kubernetes service of type LoadBalancer, which preserves the source IP address of incoming packets. Example: . You can manually integrate a Network Load Balancer (NLB) by exposing and attaching a public IP address to a viable Kubernetes node. This node serves as a load balancer using kube-proxy.

You can connect to your VM instance using an SSH client. However, it varies depending on your operating system.

• Linux: Search Terminal or press CTRL+ALT+T.

• macOS: Search Terminal.

• Windows: Search Bash. If you do not have it installed, use PuTTY instead.

What's new

Replication Enhancement

and

What's new

Contract-Owned Buckets in IONOS Object Storage

What's new

DBaaS for MariaDB is available in all IONOS Cloud locations

Documentation updates

The IONOS AI Model Hub provides an OpenAI-compatible API, allowing seamless integration with various frontend tools that use Large Language Models (LLMs). This guide walks you through the setup process, using AnythingLLM as an example tool.

By the end of this tutorial, you will be able to configure AnythingLLM to use the IONOS AI Model Hub as its backend for AI-powered responses.

Step 1: Get an Authentication Token

You will need an authentication token to access the IONOS AI Model Hub. For more information about how to generate your token in the IONOS DCD, see Generate authentication token.

Save this token in a secure place, as you’ll need to enter it into AnythingLLM during setup.

Step 2: Select a Language Model

The IONOS AI Model Hub offers a variety of Large Language Models to suit different needs. Choose the model that best fits your use case from the table below:

During setup, you’ll enter the model’s "Model Name" value into AnythingLLM’s configuration.

Step 3: Obtain the Base URL

For connecting to the IONOS AI Model Hub, use the following Base URL for the OpenAI-compatible API:

You will enter this URL in the configuration settings of AnythingLLM.

Step 4: Configure AnythingLLM

With your authentication token, selected model name, and base URL in hand, you’re ready to set up AnythingLLM:

1. Open AnythingLLM and go to the configuration page for the Large Language Model (LLM) settings.

   • In AnythingLLM, this can be accessed by clicking the wrench icon in the lower left corner, then navigating to AI Providers -> LLM.

2. Choose Generic OpenAI as the provider.

Your screen should look similar to the image below:

1. Click Save Changes to apply the settings.

From now on, AnythingLLM will use the IONOS AI Model Hub as its backend, enabling AI-powered functionality based on your chosen Large Language Model.

Summary

This guide provides a straightforward path for integrating the IONOS AI Model Hub into third-party frontend tools using the OpenAI-compatible API. For other tools and more advanced configurations, the steps will be similar: generate an API key, select a model, and configure the tool’s API settings.

You can enable IPv6 on Dedicated Core servers and vCPU Servers when you create them or after you create them.

Set up IPv6

You can set up IPv6 to improve the network connectivity for your virtualized environment. By setting up IPv6 for your Dedicated Core servers and vCPU Servers, you can ensure that they are accessible to IPv6-enabled networks and clients.

Best practices for provisioning new Opteron VMs

For Terraform Users

Configuration check:

• Ensure that the cpu_family parameter in your Terraform configuration file (*.tf) is not set to AMD_OPTERON.

• The cpu_family parameter is optional, but if it is set to AMD_OPTERON, it must be updated or removed to avoid errors. For more information about the available options, see .

Provisioning:

• Before provisioning new VMs, verify that the Terraform configuration file (*.tf) is updated appropriately.

• Run terraform plan to confirm the configuration is correct.

• Provision the VM using terraform apply.

For Crossplane Users

Configuration check:

• If the specification file has the cpuFamily set to AMD_OPTERON, it should be updated to avoid errors.

• Failure to update the cpuFamily parameter will result in an error when managing VMs.

Verification:

• Check your specification files for the cpuFamily parameter.

• Update the parameter from AMD_OPTERON to the appropriate value according to your needs.

Limitations while creating new VMs with AMD Opteron

These limitations apply when you try to create new VMs:

• You cannot select AMD Opteron as the CPU architecture for New VMs.

• You cannot switch a running or deallocated VM's CPU family to AMD Opteron.

For further assistance or questions, contact .

The IONOS AI Model Hub is a comprehensive platform that empowers developers to easily implement advanced AI functionalities. You can enhance your applications' capabilities by leveraging managed foundation models, vector databases, and advanced retrieval augmented generation techniques while ensuring security and compliance. Explore the potential of IONOS AI Model Hub Service to transform your AI projects today.

Product Overview

Quick Links

Developer Tools

• In the DCD, go to Menu > Data Center Designer and click Open Start Center.

You can connect to your VM instance using an SSH client. However, it varies depending on your operating system.

• Linux: Search Terminal or press CTRL+ALT+T.

• macOS: Search Terminal.

• Windows: Search Bash. If you do not have it installed, use PuTTY instead.

Follow these steps to connect to your VM:

1. Open the terminal window on your local computer and enter the SSH connection command below. After the @, add the of your VM instance. Next, press ENTER.

For a private key, ensure that you have the location of the private key (.pem file), the username, and the public DNS name. Enter the following command:

1. Authentication is the next step in the connection process. You will be able to connect to the VM immediately if you have added the SSH keys or after entering your key pair's passphrase.

If you have not already added SSH keys, you will be prompted for your password:

The terminal remains empty for you to paste the initial password into. Pasting into text-based terminals is different from desktop applications. It is also different from one window manager to another:

• For Linux Gnome Terminal, use CTRL+SHIFT+V.

• For macOS, use the SHIFT-CMD-V or a middle mouse button.

• For Bash on Windows, right-click on the window bar, choose Edit, then Paste. You can also right-click to paste if you enable the QuickEdit mode.

1. Press ENTER after you enter the password.

You can enable IPv6 on Cubes when you create them or after you create them.

Set up IPv6

You can set up IPv6 to improve the network connectivity for your virtualized environment. By setting up IPv6 for your Cubes, you can ensure that they are accessible to IPv6-enabled networks and clients.

To enable IPv6 for Cubes, connect it to an IPv6-enabled using the following:

1. Log in to DCD with your username and password.

2. Select the Network option on the right pane for the specific Cube and enter the following:

• Name: It is recommended to enter a unique name for this Network Interface Controller (NIC).

• MAC: This field is automatically populated.

• LAN: Select an IPv6 enabled Local Area Network (LAN).

• Firewall: Specify whether you want to enable or disable the firewall. For enabling the firewall, choose Ingress

1. Click PROVISION CHANGES.

You can configure VM Auto Scaling via DCD. This feature combines granular configurable options wherein you can create a group and define when the feature must scale in or scale out based on demand. You must also specify the minimum (for scale out) and the maximum (for scale in) number of replicas a group can contain for the replicas to stay within the given threshold.

Configure replicas after configuring thresholds and policies, where you define the settings, network, and storage volumes for the replicas created by the feature. After you define the network, you may add an Application Load Balancer (ALB) to the group.

After successfully creating a group, you can modify its details, delete it, and view its associated servers and list of jobs.

Quick Links

The following links redirect you to the relevant pages.

The release schedule outlines the timeline for Kubernetes versions, updates, availability, and the deployment of new features within the Managed Kubernetes environment. It also provides an estimated release and End of Life (EOL) schedule.

The Managed Kubernetes release schedule provides the following information:

• Kubernetes Version: This refers to a specific release of the Kubernetes, which includes updates, enhancements, and bug fixes.

• Kubernetes Release Date: The date when a specific version of the Kubernetes software is released, making it available for users to download and deploy.

• Availability Date: This is an estimate of the version release of the new feature that becomes accessible or ready for use.

• Kubernetes End of Life (EOL): The date when a specific version or release of Kubernetes reaches the end of its official support and maintenance period, after which it no longer receives updates, security patches, or bug fixes from the Kubernetes community or its maintainers. These versions may still be available in the Managed Kubernetes product but will soon be removed from the available versions.

• End of Life (EOL): The point in time when the Managed Kubernetes product reaches the end of its official support period, after which it will no longer receive updates, patches, or technical assistance.

What's new

When creating based on IONOS Linux images, you can inject into your . You can access your VMs safely on the IONOS Cloud, which uses SSH keys for authentication and secure communication. SSH keys that you intend to use more often can be saved in the view.

facilitates the fully automated setup of Kubernetes clusters. Using Managed Kubernetes, several clusters can be quickly and easily deployed. For example, you can use it on the go to set up staging environments and then delete them if required. Managed Kubernetes simplifies and supports the automation of Continuous Integration and Continuous Delivery/Continuous Deployment (CI/CD) pipelines that help in testing and deployment.

IONOS Managed Kubernetes offers the following:

• Automatic updates and security fixes.

• Version and upgrade provisioning.

What's new

What is VM Auto Scaling?

VM Auto Scaling is a managed service designed to launch or terminate VM instances horizontally to ensure you have the appropriate number of instances available to handle the load on your application.

VM Auto Scaling allows you to automatically scale the number of VM instances horizontally based on the configured policy. This functionality ensures that you have enough VM instances to handle the application loads. It improves efficiency by ensuring that adequate instances are available during peak workloads and saves money by limiting the number of instances available during low workload periods.

This section covers the components of VM Auto Scaling, its features, benefits, and limitations.

Components of VM Auto Scaling

The following components are an integral part of VM Auto Scaling:

When creating based on IONOS Linux images, you can inject into your . You can access your VMs safely on the IONOS Cloud, which uses SSH keys for authentication and secure communication. SSH keys that you intend to use more often can be saved in the view.