Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content
  • Zero Downtime Deployment of BusinessWorks Container Edition with Kubernetes ? Part 2


    Manoj Chaurasia

    Table of Contents

    Using the Kubernetes Recreate Strategy


    In my first post in this series, we created a Greeting Service using TIBCO BusinessWorks Container Edition and we created manifest files and deployed our Micro Service into Minikube.

    In this post, we?re going to upgrade our original version of the Micro Service to version 1.1 and we?ll use the Recreate strategy to perform the upgrade.

    To do this, I?ve created a new manifest file (here) that has 2 changes to it. The first is to point it to the newer version of the Docker Image that we created earlier (v1.1), and also to add in the definition of the Recreate Strategy. The extracts from the manifest file of importance are below ? but look at the full file to compare the difference:

    BWcontainer1.png.6c2264f24c3b2cdd1de6e615145391fe.png

    To perform our update, all we need to do is to apply the new version of the manifest file using the following command:

    BWcontainer2.png.6d1f710d0f19720fca8dd16a260fc595.png

    The rollout will happen immediately and has the effect of killing the current pods, whilst starting up the new versions. Looking at the dashboard, we can see that there are 2 pods in Pending status, and none running. We can also use the command below to check the rollout status from the command line:

    BWcontainer4.png.905b5a572af63033e8a5f09718fb5aae.png

    BWcontainer5.png.41e4ff81eaa5cf77aed669fb9647005f.png

    BWcontainer6.png.86ef28fb6cad84ca81654e26b1142911.png

    Our command line utility that checks the Application has also stopped responding ? this is because I haven?t built any error handling in the client, so I?ll just have to stop and restart the shell command, and we can now see that the app has been upgraded and using the latest version as well as the host names changing of course.

    BWcontainer7.png.38fc845a7c59a3031315431aa4891ebd.png

    Because I had to stop my client and restart ? that introduces downtime and may not be what you want (especially given the title of the article!). So we want to look at one of the other strategies.

     that you can follow along with and see the recreated strategy in action.

    The next post in the series will focus on Rolling Updates ? so I hope you?ll come back and continue learning.


    User Feedback

    Recommended Comments

    There are no comments to display.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...