Skip to main content

Step 9: Update the Application

To test the new release that you promoted, return to the admin console in a browser to update the application.

To update the application:

  1. Access the admin console using https://localhost:8800 if the installation script is still running. Otherwise, run the following command to access the admin console:

    kubectl kots admin-console --namespace NAMESPACE

    Replace NAMESPACE with the namespace where the admin console is installed.

  2. Go to the Version history page, and click Check for update.

    admin console version history page

    The admin console loads the new release that you promoted.

  3. Click Deploy. In the dialog, click Yes, deploy to deploy the new version.

    admin console version history page with new version

  4. After the admin console deploys the new version, go to the Config page where the Another Text Example field that you added is displayed.

    admin console configuration page with Another Text Example field

  5. In the new Another Text Example field, enter any text. Click Save config.

    The admin console notifies you that the configuration settings for the application have changed.

    dialog over admin console configuration screen

  6. In the dialog, click Go to updated version.

    The admin console loads the updated version on the Version history page.

  7. On the Version history page, click Deploy next to the latest version to deploy the configuration change.

    admin console version history page with new version

  8. Go to the Dashboard page and click Open App. The application displays the text that you added to the field.

    web page with text from the new configuration field

    note

    If you do not see the new text, refresh your browser.

Next Step​

Congratulations! As part of this tutorial, you:

  • Created and promoted a release for a Kubernetes application using the replicated CLI
  • Installed the application in a Kubernetes cluster
  • Edited the manifest files for the application, adding a new configuration field and using template functions to reference the field
  • Promoted a new release with your changes
  • Used the admin console to update the application to the latest version

As a next step, you can continue to iterate on your application, using replicated release create --auto to promote each new release. For a list of KOTS features to integrate with your application, see Onboarding with KOTS.