MKS Standard - Missing duplication

Author: Y0Coss

pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.de-de.md

@@ -36,22 +36,12 @@ updated: 2025-09-10
 | Availability          | 99,5% SLO                                           | 99,99 SLA (at General Availability stage) |
 | etcd                  | Shared, up to 400MB                                 | Dedicated, up to 8GB                      |
 | Max cluster size      | Up to 100 nodes                                     | Up to 500 nodes                           |
-| Regional availability | Single-zone regions (3-AZ regions planned for 2025) | 3-AZ region for now                       |
+| Regional availability | Single-zone regions                                 | 3-AZ region for now                       |
 
 ## Limitations / Upcoming features
 
 In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features.
 
-This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025.
-
-### Cluster upgrade
-
-Upgrading an existing cluster is not supported at the moment, we'll deliver this functionality once we support the next Kubernetes release (1.33).
-
-### Logs Data Platform integration
-
-Audit logs forwarding to the [Logs Data Platform](/pages/public_cloud/containers_orchestration/managed_kubernetes/forwarding-audit-logs-to-logs-data-platform) is not supported at the moment.
-
 ### ETCD Quota
 
 Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster.
@@ -67,12 +57,6 @@ Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel
 openstack router show ROUTER_ID -c external_gateway_info
 ```
 
-### Anti-affinity
-
-This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR).
-
-We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ.
-
 ### Ports
 
 The OpenStack security group for worker nodes is the `default` one. It allows all egress and ingress traffic by default on your private network.
@@ -110,7 +94,11 @@ They allow to create **zone specific** volumes: a PVC provisioned on a zone `X`
 
 The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
-To create a volume on MKS Standard, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
+To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
+
+### Reset kubeconfig
+
+At the moment, it is not possible to reset your kubeconfig file.
 
 ## Getting started
 
@@ -271,4 +259,4 @@ The following methods are supported to create an MKS Standard cluster:
 
 - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-- Join our [community of users on Discord](https://discord.gg/ovhcloud)!
+- Join our [community of users on Discord](https://discord.gg/ovhcloud)!

pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-asia.md

@@ -36,22 +36,12 @@ updated: 2025-09-10
 | Availability          | 99,5% SLO                                           | 99,99 SLA (at General Availability stage) |
 | etcd                  | Shared, up to 400MB                                 | Dedicated, up to 8GB                      |
 | Max cluster size      | Up to 100 nodes                                     | Up to 500 nodes                           |
-| Regional availability | Single-zone regions (3-AZ regions planned for 2025) | 3-AZ region for now                       |
+| Regional availability | Single-zone regions                                 | 3-AZ region for now                       |
 
 ## Limitations / Upcoming features
 
 In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features.
 
-This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025.
-
-### Cluster upgrade
-
-Upgrading an existing cluster is not supported at the moment, we'll deliver this functionality once we support the next Kubernetes release (1.33).
-
-### Logs Data Platform integration
-
-Audit logs forwarding to the [Logs Data Platform](/pages/public_cloud/containers_orchestration/managed_kubernetes/forwarding-audit-logs-to-logs-data-platform) is not supported at the moment.
-
 ### ETCD Quota
 
 Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster.
@@ -67,12 +57,6 @@ Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel
 openstack router show ROUTER_ID -c external_gateway_info
 ```
 
-### Anti-affinity
-
-This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR).
-
-We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ.
-
 ### Ports
 
 The OpenStack security group for worker nodes is the `default` one. It allows all egress and ingress traffic by default on your private network.
@@ -110,7 +94,11 @@ They allow to create **zone specific** volumes: a PVC provisioned on a zone `X`
 
 The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_limitations#introduction) is not supported yet for MKS clusters on regions with multiple availability zones, since the currently available file systems (ext(2,3,4), xfs and btrfs) can be subject to data corruptions if volumes are attached to multiple instances.
 
-To create a volume on MKS Standard, use the same process as a [standard Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
+To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
+
+### Reset kubeconfig
+
+At the moment, it is not possible to reset your kubeconfig file.
 
 ## Getting started
 
@@ -271,4 +259,4 @@ The following methods are supported to create an MKS Standard cluster:
 
 - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-- Join our [community of users on Discord](https://discord.gg/ovhcloud)!
+- Join our [community of users on Discord](https://discord.gg/ovhcloud)!

pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-au.md

@@ -36,22 +36,12 @@ updated: 2025-09-10
 | Availability          | 99,5% SLO                                           | 99,99 SLA (at General Availability stage) |
 | etcd                  | Shared, up to 400MB                                 | Dedicated, up to 8GB                      |
 | Max cluster size      | Up to 100 nodes                                     | Up to 500 nodes                           |
-| Regional availability | Single-zone regions (3-AZ regions planned for 2025) | 3-AZ region for now                       |
+| Regional availability | Single-zone regions                                 | 3-AZ region for now                       |
 
 ## Limitations / Upcoming features
 
 In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features.
 
-This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025.
-
-### Cluster upgrade
-
-Upgrading an existing cluster is not supported at the moment, we'll deliver this functionality once we support the next Kubernetes release (1.33).
-
-### Logs Data Platform integration
-
-Audit logs forwarding to the [Logs Data Platform](/pages/public_cloud/containers_orchestration/managed_kubernetes/forwarding-audit-logs-to-logs-data-platform) is not supported at the moment.
-
 ### ETCD Quota
 
 Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster.
@@ -67,12 +57,6 @@ Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel
 openstack router show ROUTER_ID -c external_gateway_info
 ```
 
-### Anti-affinity
-
-This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR).
-
-We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ.
-
 ### Ports
 
 The OpenStack security group for worker nodes is the `default` one. It allows all egress and ingress traffic by default on your private network.
@@ -112,6 +96,10 @@ The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_li
 
 To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
+### Reset kubeconfig
+
+At the moment, it is not possible to reset your kubeconfig file.
+
 ## Getting started
 
 ### Prerequisites
@@ -271,4 +259,4 @@ The following methods are supported to create an MKS Standard cluster:
 
 - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-- Join our [community of users on Discord](https://discord.gg/ovhcloud)!
+- Join our [community of users on Discord](https://discord.gg/ovhcloud)!

pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-ca.md

@@ -36,22 +36,12 @@ updated: 2025-09-10
 | Availability          | 99,5% SLO                                           | 99,99 SLA (at General Availability stage) |
 | etcd                  | Shared, up to 400MB                                 | Dedicated, up to 8GB                      |
 | Max cluster size      | Up to 100 nodes                                     | Up to 500 nodes                           |
-| Regional availability | Single-zone regions (3-AZ regions planned for 2025) | 3-AZ region for now                       |
+| Regional availability | Single-zone regions                                 | 3-AZ region for now                       |
 
 ## Limitations / Upcoming features
 
 In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features.
 
-This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025.
-
-### Cluster upgrade
-
-Upgrading an existing cluster is not supported at the moment, we'll deliver this functionality once we support the next Kubernetes release (1.33).
-
-### Logs Data Platform integration
-
-Audit logs forwarding to the [Logs Data Platform](/pages/public_cloud/containers_orchestration/managed_kubernetes/forwarding-audit-logs-to-logs-data-platform) is not supported at the moment.
-
 ### ETCD Quota
 
 Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster.
@@ -67,12 +57,6 @@ Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel
 openstack router show ROUTER_ID -c external_gateway_info
 ```
 
-### Anti-affinity
-
-This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR).
-
-We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ.
-
 ### Ports
 
 The OpenStack security group for worker nodes is the `default` one. It allows all egress and ingress traffic by default on your private network.
@@ -112,6 +96,10 @@ The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_li
 
 To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
+### Reset kubeconfig
+
+At the moment, it is not possible to reset your kubeconfig file.
+
 ## Getting started
 
 ### Prerequisites
@@ -271,4 +259,4 @@ The following methods are supported to create an MKS Standard cluster:
 
 - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-- Join our [community of users on Discord](https://discord.gg/ovhcloud)!
+- Join our [community of users on Discord](https://discord.gg/ovhcloud)!

pages/public_cloud/containers_orchestration/managed_kubernetes/premium/guide.en-ie.md

@@ -36,22 +36,12 @@ updated: 2025-09-10
 | Availability          | 99,5% SLO                                           | 99,99 SLA (at General Availability stage) |
 | etcd                  | Shared, up to 400MB                                 | Dedicated, up to 8GB                      |
 | Max cluster size      | Up to 100 nodes                                     | Up to 500 nodes                           |
-| Regional availability | Single-zone regions (3-AZ regions planned for 2025) | 3-AZ region for now                       |
+| Regional availability | Single-zone regions                                 | 3-AZ region for now                       |
 
 ## Limitations / Upcoming features
 
 In order to help you make the best use of our new Managed Kubernetes Service (MKS) Standard Plan, we have listed some limitations and guidelines related to specific features.
 
-This list is subject to change as new features will be introduced during the Beta period. The end of the Beta phase and General Availability are planned for the end of summer 2025.
-
-### Cluster upgrade
-
-Upgrading an existing cluster is not supported at the moment, we'll deliver this functionality once we support the next Kubernetes release (1.33).
-
-### Logs Data Platform integration
-
-Audit logs forwarding to the [Logs Data Platform](/pages/public_cloud/containers_orchestration/managed_kubernetes/forwarding-audit-logs-to-logs-data-platform) is not supported at the moment.
-
 ### ETCD Quota
 
 Real-time monitoring of the etcd storage usage is not supported at the moment, current etcd quota is 8GB per cluster.
@@ -67,12 +57,6 @@ Retrieve the gateway IP of your cluster's gateway in the [OVHcloud Control Panel
 openstack router show ROUTER_ID -c external_gateway_info
 ```
 
-### Anti-affinity
-
-This feature allows worker nodes to be deployed on different hypervisors (physical servers) within the same availability zone, guaranteeing better fault tolerance. It is currently supported on the MKS Standard Plan (region EU-WEST-PAR).
-
-We recommend using multiple Availability Zones (AZs) instead by using node pool to spread worker nodes between AZ.
-
 ### Ports
 
 The OpenStack security group for worker nodes is the `default` one. It allows all egress and ingress traffic by default on your private network.
@@ -112,6 +96,10 @@ The [classic multi-attach](/pages/public_cloud/compute/classic_block_multi_az_li
 
 To create a volume on MKS Standard, use the same process as a [Free Managed Kubernetes cluster](/pages/public_cloud/containers_orchestration/managed_kubernetes/setting-up-a-persistent-volume).
 
+### Reset kubeconfig
+
+At the moment, it is not possible to reset your kubeconfig file.
+
 ## Getting started
 
 ### Prerequisites
@@ -271,4 +259,4 @@ The following methods are supported to create an MKS Standard cluster:
 
 - If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-- Join our [community of users on Discord](https://discord.gg/ovhcloud)!
+- Join our [community of users on Discord](https://discord.gg/ovhcloud)!