diff --git a/linkerd.io/content/2-edge/tasks/automatic-failover.md b/linkerd.io/content/2-edge/tasks/automatic-failover.md index c9cc2dafa9..cabed90b38 100644 --- a/linkerd.io/content/2-edge/tasks/automatic-failover.md +++ b/linkerd.io/content/2-edge/tasks/automatic-failover.md @@ -116,13 +116,12 @@ web-svc ClusterIP 10.96.222.169 80/TCP 13m web-svc-east ClusterIP 10.96.244.245 80/TCP 92s ``` -{{< alert severity="warning" >}} -The order in which the Application and the ServiceProfile used by the -TrafficSplit resource are created is important. If a ServiceProfile is -created after the pod has already started, the workloads will need to be -restarted. For more details on Service Profiles, -check out the [Service Profiles documentation](../features/service-profiles.md). -{{< /alert >}} +{{< warning >}} +The order in which the Application and the ServiceProfile used by the TrafficSplit +resource are created is important. If a ServiceProfile is created after the pod has +already started, the workloads will need to be restarted. For more details on Service +Profiles, check out the [Service Profiles documentation](../features/service-profiles.md). +{{< /warning >}} ## Testing the Failover diff --git a/linkerd.io/content/2.11/tasks/automatic-failover.md b/linkerd.io/content/2.11/tasks/automatic-failover.md index c9cc2dafa9..cabed90b38 100644 --- a/linkerd.io/content/2.11/tasks/automatic-failover.md +++ b/linkerd.io/content/2.11/tasks/automatic-failover.md @@ -116,13 +116,12 @@ web-svc ClusterIP 10.96.222.169 80/TCP 13m web-svc-east ClusterIP 10.96.244.245 80/TCP 92s ``` -{{< alert severity="warning" >}} -The order in which the Application and the ServiceProfile used by the -TrafficSplit resource are created is important. If a ServiceProfile is -created after the pod has already started, the workloads will need to be -restarted. For more details on Service Profiles, -check out the [Service Profiles documentation](../features/service-profiles.md). -{{< /alert >}} +{{< warning >}} +The order in which the Application and the ServiceProfile used by the TrafficSplit +resource are created is important. If a ServiceProfile is created after the pod has +already started, the workloads will need to be restarted. For more details on Service +Profiles, check out the [Service Profiles documentation](../features/service-profiles.md). +{{< /warning >}} ## Testing the Failover diff --git a/linkerd.io/content/2.12/tasks/automatic-failover.md b/linkerd.io/content/2.12/tasks/automatic-failover.md index c9cc2dafa9..cabed90b38 100644 --- a/linkerd.io/content/2.12/tasks/automatic-failover.md +++ b/linkerd.io/content/2.12/tasks/automatic-failover.md @@ -116,13 +116,12 @@ web-svc ClusterIP 10.96.222.169 80/TCP 13m web-svc-east ClusterIP 10.96.244.245 80/TCP 92s ``` -{{< alert severity="warning" >}} -The order in which the Application and the ServiceProfile used by the -TrafficSplit resource are created is important. If a ServiceProfile is -created after the pod has already started, the workloads will need to be -restarted. For more details on Service Profiles, -check out the [Service Profiles documentation](../features/service-profiles.md). -{{< /alert >}} +{{< warning >}} +The order in which the Application and the ServiceProfile used by the TrafficSplit +resource are created is important. If a ServiceProfile is created after the pod has +already started, the workloads will need to be restarted. For more details on Service +Profiles, check out the [Service Profiles documentation](../features/service-profiles.md). +{{< /warning >}} ## Testing the Failover diff --git a/linkerd.io/content/2.13/tasks/automatic-failover.md b/linkerd.io/content/2.13/tasks/automatic-failover.md index c9cc2dafa9..cabed90b38 100644 --- a/linkerd.io/content/2.13/tasks/automatic-failover.md +++ b/linkerd.io/content/2.13/tasks/automatic-failover.md @@ -116,13 +116,12 @@ web-svc ClusterIP 10.96.222.169 80/TCP 13m web-svc-east ClusterIP 10.96.244.245 80/TCP 92s ``` -{{< alert severity="warning" >}} -The order in which the Application and the ServiceProfile used by the -TrafficSplit resource are created is important. If a ServiceProfile is -created after the pod has already started, the workloads will need to be -restarted. For more details on Service Profiles, -check out the [Service Profiles documentation](../features/service-profiles.md). -{{< /alert >}} +{{< warning >}} +The order in which the Application and the ServiceProfile used by the TrafficSplit +resource are created is important. If a ServiceProfile is created after the pod has +already started, the workloads will need to be restarted. For more details on Service +Profiles, check out the [Service Profiles documentation](../features/service-profiles.md). +{{< /warning >}} ## Testing the Failover diff --git a/linkerd.io/content/2.14/tasks/automatic-failover.md b/linkerd.io/content/2.14/tasks/automatic-failover.md index c9cc2dafa9..cabed90b38 100644 --- a/linkerd.io/content/2.14/tasks/automatic-failover.md +++ b/linkerd.io/content/2.14/tasks/automatic-failover.md @@ -116,13 +116,12 @@ web-svc ClusterIP 10.96.222.169 80/TCP 13m web-svc-east ClusterIP 10.96.244.245 80/TCP 92s ``` -{{< alert severity="warning" >}} -The order in which the Application and the ServiceProfile used by the -TrafficSplit resource are created is important. If a ServiceProfile is -created after the pod has already started, the workloads will need to be -restarted. For more details on Service Profiles, -check out the [Service Profiles documentation](../features/service-profiles.md). -{{< /alert >}} +{{< warning >}} +The order in which the Application and the ServiceProfile used by the TrafficSplit +resource are created is important. If a ServiceProfile is created after the pod has +already started, the workloads will need to be restarted. For more details on Service +Profiles, check out the [Service Profiles documentation](../features/service-profiles.md). +{{< /warning >}} ## Testing the Failover diff --git a/linkerd.io/content/2.15/tasks/automatic-failover.md b/linkerd.io/content/2.15/tasks/automatic-failover.md index c9cc2dafa9..cabed90b38 100644 --- a/linkerd.io/content/2.15/tasks/automatic-failover.md +++ b/linkerd.io/content/2.15/tasks/automatic-failover.md @@ -116,13 +116,12 @@ web-svc ClusterIP 10.96.222.169 80/TCP 13m web-svc-east ClusterIP 10.96.244.245 80/TCP 92s ``` -{{< alert severity="warning" >}} -The order in which the Application and the ServiceProfile used by the -TrafficSplit resource are created is important. If a ServiceProfile is -created after the pod has already started, the workloads will need to be -restarted. For more details on Service Profiles, -check out the [Service Profiles documentation](../features/service-profiles.md). -{{< /alert >}} +{{< warning >}} +The order in which the Application and the ServiceProfile used by the TrafficSplit +resource are created is important. If a ServiceProfile is created after the pod has +already started, the workloads will need to be restarted. For more details on Service +Profiles, check out the [Service Profiles documentation](../features/service-profiles.md). +{{< /warning >}} ## Testing the Failover diff --git a/linkerd.io/content/2.16/tasks/automatic-failover.md b/linkerd.io/content/2.16/tasks/automatic-failover.md index c9cc2dafa9..cabed90b38 100644 --- a/linkerd.io/content/2.16/tasks/automatic-failover.md +++ b/linkerd.io/content/2.16/tasks/automatic-failover.md @@ -116,13 +116,12 @@ web-svc ClusterIP 10.96.222.169 80/TCP 13m web-svc-east ClusterIP 10.96.244.245 80/TCP 92s ``` -{{< alert severity="warning" >}} -The order in which the Application and the ServiceProfile used by the -TrafficSplit resource are created is important. If a ServiceProfile is -created after the pod has already started, the workloads will need to be -restarted. For more details on Service Profiles, -check out the [Service Profiles documentation](../features/service-profiles.md). -{{< /alert >}} +{{< warning >}} +The order in which the Application and the ServiceProfile used by the TrafficSplit +resource are created is important. If a ServiceProfile is created after the pod has +already started, the workloads will need to be restarted. For more details on Service +Profiles, check out the [Service Profiles documentation](../features/service-profiles.md). +{{< /warning >}} ## Testing the Failover diff --git a/linkerd.io/content/2.17/tasks/automatic-failover.md b/linkerd.io/content/2.17/tasks/automatic-failover.md index 750e90128a..cabed90b38 100644 --- a/linkerd.io/content/2.17/tasks/automatic-failover.md +++ b/linkerd.io/content/2.17/tasks/automatic-failover.md @@ -116,12 +116,12 @@ web-svc ClusterIP 10.96.222.169 80/TCP 13m web-svc-east ClusterIP 10.96.244.245 80/TCP 92s ``` -{{< alert severity="warning" >}} +{{< warning >}} The order in which the Application and the ServiceProfile used by the TrafficSplit resource are created is important. If a ServiceProfile is created after the pod has already started, the workloads will need to be restarted. For more details on Service Profiles, check out the [Service Profiles documentation](../features/service-profiles.md). -{{< /alert >}} +{{< /warning >}} ## Testing the Failover