removed references to Ubuntu 16.04

Author: tomvcassidy

articles/service-fabric/service-fabric-cluster-creation-via-arm.md

@@ -93,7 +93,7 @@ declare CertSubjectName="mylinux.westus.cloudapp.azure.com"
 declare vmpassword="Password!1"
 declare certpassword="Password!4321"
 declare vmuser="myadmin"
-declare vmOs="UbuntuServer1604"
+declare vmOs="UbuntuServer1804"
 declare certOutputFolder="c:\certificates"
 
 az sf cluster create --resource-group $resourceGroupName --location $resourceGroupLocation  \
@@ -190,7 +190,7 @@ declare resourceGroupName="mylinux"
 declare vaultResourceGroupName="myvaultrg"
 declare vaultName="myvault"
 declare certificate-file="c:\certificates\mycert.pem"
-declare vmOs="UbuntuServer1604"
+declare vmOs="UbuntuServer1804"
 
 az sf cluster create --resource-group $resourceGroupName --location $resourceGroupLocation  \
 	--certificate-file $certificate-file --certificate-password $certPassword  \

articles/service-fabric/service-fabric-cluster-upgrade-os.md

@@ -11,18 +11,18 @@ ms.date: 07/14/2022
 
 # Upgrade Linux OS for Azure Service Fabric
 
-This document describes how to migrate your Azure Service Fabric for Linux cluster from Ubuntu version 16.04 LTS to 18.04 LTS. Each operating system (OS) version requires a different Service Fabric runtime package. This article describes the steps required to facilitate a smooth migration to the newer version.
+This document describes how to migrate your Azure Service Fabric for Linux cluster from Ubuntu version 18.04 LTS to 20.04 LTS. Each operating system (OS) version requires a different Service Fabric runtime package. This article describes the steps required to facilitate a smooth migration to the newer version.
 
 ## Approach to migration
 
 The general approach to the migration follows these steps:
 
-1. Switch the Service Fabric cluster Azure Resource Manager resource `vmImage` to `Ubuntu18_04`. This setting pulls future code upgrades for this OS version. This temporary OS mismatch against existing node types blocks automatic code upgrade rollouts to ensure safe rollover.
+1. Switch the Service Fabric cluster Azure Resource Manager resource `vmImage` to `Ubuntu20_04`. This setting pulls future code upgrades for this OS version. This temporary OS mismatch against existing node types blocks automatic code upgrade rollouts to ensure safe rollover.
 
    > [!TIP]
    > Avoid issuing manual Service Fabric cluster code upgrades during the OS migration. Doing so may cause the old node type nodes to enter a state that requires human intervention.
 
-1. For each node type in the cluster, create another node type that targets the Ubuntu 18.04 OS image for the underlying Virtual Machine Scale Set. Each new node type assumes the role of its old counterpart.
+1. For each node type in the cluster, create another node type that targets the Ubuntu 20.04 OS image for the underlying Virtual Machine Scale Set. Each new node type assumes the role of its old counterpart.
 
    * A new primary node type has to be created to replace the old node type marked as `isPrimary: true`.
    * For each non-primary node type, these nodes types are marked `isPrimary: false`.
@@ -48,7 +48,7 @@ This procedure demonstrates how to quickly prototype the node type migration by
     $resourceGroup="Group1"
     $clusterName="Contoso01SFCluster"
     # Update cluster vmImage to target OS. This registers the SF runtime package type that is supplied for upgrades.
-    Update-AzServiceFabricVmImage -ResourceGroupName $resourceGroup -ClusterName $clusterName -VmImage Ubuntu18_04
+    Update-AzServiceFabricVmImage -ResourceGroupName $resourceGroup -ClusterName $clusterName -VmImage Ubuntu20_04
     ```
 
 2. Add new node type counterpart for each of the existing node types:

articles/service-fabric/service-fabric-get-started-linux.md

@@ -195,16 +195,12 @@ Start a container-based [Service Fabric Onebox](https://hub.docker.com/_/microso
     ```bash
     docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u20
     ```
+
     <b>Ubuntu 18.04 LTS:</b>
     ```bash
     docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u18
     ```
 
-    <b>Ubuntu 16.04 LTS:</b>
-    ```bash
-    docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u16
-    ```
-
     >[!TIP]
     > By default, this will pull the image with the latest version of Service Fabric. For particular revisions, please visit the [Docker Hub](https://hub.docker.com/r/microsoft/service-fabric-onebox/) page.
 

articles/service-fabric/service-fabric-get-started-mac.md

@@ -56,14 +56,14 @@ To set up a local Docker container and have a Service Fabric cluster running on
     >We recommend increasing the resources allocated to Docker when testing large applications. This can be done by selecting the **Docker Icon**, then selecting **Advanced** to adjust the number of cores and memory.
 
 2. Start the cluster.<br/>
-    <b>Ubuntu 18.04 LTS:</b>
+    <b>Ubuntu 20.04 LTS:</b>
     ```bash
-    docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u18
+    docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u20
     ```
 
-    <b>Ubuntu 16.04 LTS:</b>
+    <b>Ubuntu 18.04 LTS:</b>
     ```bash
-    docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u16
+    docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u18
     ```
 
     >[!TIP]

articles/service-fabric/service-fabric-how-to-publish-linux-app-vs.md

@@ -40,7 +40,7 @@ With Visual Studio tooling you can develop and publish Service Fabric .Net Core
 
 4. Update the RuntimeIndetifier from win7-x64 to the target platform in the service project.
 ```xml
-    <RuntimeIdentifier>ubuntu.16.04-x64</RuntimeIdentifier>
+    <RuntimeIdentifier>ubuntu.20.04-x64</RuntimeIdentifier>
 ```
 5. In the ServiceManifest, update the entrypoint program to remove .exe. 
 ```xml

articles/service-fabric/service-fabric-local-linux-cluster-windows.md

@@ -51,14 +51,14 @@ To set up a local Docker container and have a Service Fabric cluster running on
     * Apply & Restart - restart the Docker daemon for the changes to take effect.
 
 2. Start the cluster via PowerShell.<br/>
-    <b>Ubuntu 18.04 LTS:</b>
-    ```powershell
-    docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u18
+    <b>Ubuntu 20.04 LTS:</b>
+    ```bash
+    docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u20
     ```
 
-    <b>Ubuntu 16.04 LTS:</b>
+    <b>Ubuntu 18.04 LTS:</b>
     ```powershell
-    docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u16
+    docker run --name sftestcluster -d -v /var/run/docker.sock:/var/run/docker.sock -p 19080:19080 -p 19000:19000 -p 25100-25200:25100-25200 mcr.microsoft.com/service-fabric/onebox:u18
     ```
 
     >[!TIP]

articles/service-fabric/service-fabric-quickstart-containers-linux.md

@@ -75,7 +75,7 @@ az group create --name $ResourceGroupName --location $Location
 # Create secure five node Linux cluster. Creates a key vault in a resource group
 # and creates a certificate in the key vault. The certificate's subject name must match 
 # the domain that you use to access the Service Fabric cluster.  The certificate is downloaded locally.
-az sf cluster create --resource-group $ResourceGroupName --location $Location --certificate-output-folder . --certificate-password $Password --certificate-subject-name $Subject --cluster-name $ClusterName --cluster-size 5 --os UbuntuServer1604 --vault-name $VaultName --vault-resource-group $ResourceGroupName --vm-password $VmPassword --vm-user-name $VmUserName
+az sf cluster create --resource-group $ResourceGroupName --location $Location --certificate-output-folder . --certificate-password $Password --certificate-subject-name $Subject --cluster-name $ClusterName --cluster-size 5 --os UbuntuServer1804 --vault-name $VaultName --vault-resource-group $ResourceGroupName --vm-password $VmPassword --vm-user-name $VmUserName
 ```
 
 > [!Note]
@@ -87,12 +87,12 @@ az sf cluster create --resource-group $ResourceGroupName --location $Location --
 Service Fabric provides several tools that you can use to manage a cluster and its applications:
 
 - Service Fabric Explorer, a browser-based tool.
-- Service Fabric Command Line Interface (CLI), which runs on top of Azure CLI. 
+- Service Fabric Command Line Interface (CLI), which runs on top of Azure CLI.
 - PowerShell commands.
 
 In this quickstart, you use the Service Fabric CLI and Service Fabric Explorer (a web based tool). To use Service Fabric Explorer, you need to import the certificate PFX file into the browser. By default, the PFX file has no password.
 
-Mozilla Firefox is the default browser in Ubuntu 16.04. To import the certificate into Firefox, click the menu button in the upper right corner of your browser, then click **Options**. On the **Preferences** page, use the search box to search for "certificates". Click **View Certificates**, select the **Your Certificates** tab, click **Import** and follow the prompts to import the certificate.
+Mozilla Firefox is the default browser in Ubuntu 18.04. To import the certificate into Firefox, click the menu button in the upper right corner of your browser, then click **Options**. On the **Preferences** page, use the search box to search for "certificates". Click **View Certificates**, select the **Your Certificates** tab, click **Import** and follow the prompts to import the certificate.
 
    ![Install certificate on Firefox](./media/service-fabric-quickstart-containers-linux/install-cert-firefox.png)
 

articles/service-fabric/service-fabric-tutorial-create-vnet-and-linux-cluster.md

@@ -29,14 +29,6 @@ The following procedures create a seven-node Service Fabric cluster. To calculat
 
 Download the following Resource Manager template files:
 
-For Ubuntu 16.04 LTS:
-- [AzureDeploy.json][template]
-  - **vmImageSku** attribute is to "16.04-LTS"
-  - Microsoft.ServiceFabric/clusters resource's
-    - **apiVersion** being set to "2018-02-01"
-    - **vmImage** property being set to "Linux"
-- [AzureDeploy.Parameters.json][parameters]
-
 For Ubuntu 18.04 LTS:
 - [AzureDeploy.json][template2]
   - **vmImageSku** attribute is to "18.04-LTS"
@@ -61,7 +53,7 @@ In the **Microsoft.ServiceFabric/clusters** resource, a Linux cluster is deploye
 
 * three node types
 * five nodes in the primary node type (configurable in the template parameters), one node in each of the other node types
-* OS: (Ubuntu 16.04 LTS / Ubuntu 18.04 LTS) (configurable in the template parameters)
+* OS: (Ubuntu 18.04 LTS / Ubuntu 20.04) (configurable in the template parameters)
 * certificate secured (configurable in the template parameters)
 * [DNS service](service-fabric-dnsservice.md) is enabled
 * [Durability level](service-fabric-cluster-capacity.md#durability-characteristics-of-the-cluster) of Bronze (configurable in the template parameters)

articles/service-fabric/service-fabric-tutorial-package-containers.md

@@ -242,7 +242,7 @@ az group create --name $ResourceGroupName --location $Location
 # The certificate is downloaded locally as a PEM file.
 az sf cluster create --resource-group $ResourceGroupName --location $Location \ 
 --certificate-output-folder . --certificate-password $Password --certificate-subject-name $Subject \ 
---cluster-name $ClusterName --cluster-size 5 --os UbuntuServer1604 --vault-name $VaultName \ 
+--cluster-name $ClusterName --cluster-size 5 --os UbuntuServer1804 --vault-name $VaultName \ 
 --vault-resource-group $ResourceGroupName --vm-password $VmPassword --vm-user-name $VmUserName
 ```
 

articles/service-fabric/service-fabric-versions.md

@@ -108,7 +108,6 @@ Support for Service Fabric on a specific OS ends when support for the OS version
 | --- | --- | --- |
 | Ubuntu 20.04 | April 2025 | <a href="https://wiki.ubuntu.com/Releases">Ubuntu lifecycle</a>|
 | Ubuntu 18.04 | April 2023 | <a href="https://wiki.ubuntu.com/Releases">Ubuntu lifecycle</a>|
-| Ubuntu 16.04 | April 2021 | <a href="https://wiki.ubuntu.com/Releases">Ubuntu lifecycle</a>|
 
 ## Service Fabric version name and number reference
 The following table lists the version names of Service Fabric and their corresponding version numbers.