DevTest Upgrading Kubernetes On-Prem installation
search cancel

DevTest Upgrading Kubernetes On-Prem installation

book

Article ID: 233127

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

What are the steps needed to update Kubernetes on-prem 10.6 environments to 10.7?

Environment

All supported DevTest releases and platforms.

Cause

N/A

Resolution

Steps to Upgrade DevTest On-Prem Kubernetes installation.

In this example, we will cover upgrading a 10.6 Kubernetes on-prem environment to a 10.7 DevTest environment.
For the On-prem Kubernetes install IAM and Enterprise Dashboard are required to be on Standalone servers or VM machines.

NOTE: the Coordinator, Simulator(s), and VSE(s) will have the same tag version as the Registry.

Upgrade Process:

  1. Update the IAM and Enterprise dashboard from 10.6 to 10.7
    1. Follow the normal documentation for updating IAM and ED
      1. Preparing Your DevTest Upgrade (broadcom.com)
      2. Upgrading the Authentication Component (broadcom.com)

NOTE: If you are running ED on Linux or a Mac and starting ED as a service you will need to download and apply a patch from the below KB article:
Enterprise Dashboard (ED) UI is not showing up in Linux or MAC environments for DevTest 10.7 when started as a service

  1. Next, you will need to update download the DevTest Kubernetes NodePorts installer
    1. DevTest Docker for Kubernetes Using Nodeports (broadcom.com)
    2. We will require the new devtest-0.X.X.tgz version
      1. Example: devtest-0.2.0.tgz

NOTE: If you have created multiple Simulators, Coordinators or Virtual Service Engine (VSE) then you will need to unzip the devtest-0.X.X.tgz and modify this to match your original configurations from your 10.6 implementation.
IE recreate the folders and edit the helm charts.

  1. Login to the support portal and go to the download section for Service Virtualization
            Click on the green key for token generation

On the next screen scroll to the bottom to get the version information you will need.

 

Note: You may need to copy a new security token to be used with the update if the current token is more than 6 months old

 

 

 

  1. Edit your custom-values.yaml to update the TAG field for the following components:

The config-server

config-server:
  enabled: true
  fullnameOverride: devtest106-config-server
  image:
    repository: esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/config-server
    pullPolicy: IfNotPresent
    tag: 0.0.6.20

 

The registry

registry:
  enabled: true
  fullnameOverride: devtest106-registry
  databaseDriver: db-driver
  dataFileConfigMap: devtest-config
  image:
    repository: esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/lisa
    pullPolicy: IfNotPresent
    tag: 10.7.0.168

                        Note: the LISA image is the registry.

The coordinator

coordinator:
  enabled: true
  fullnameOverride: devtest106-coordinator
  databaseDriver: db-driver
  dataFileConfigMap: devtest-config
  registry:
    fullName: devtest106-registry
  image:
    repository: esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/lisa
    pullPolicy: IfNotPresent
    tag: 10.7.0.168

The Simulator(s)

simulator:
  enabled: true
  fullnameOverride: devtest106-simulator
  databaseDriver: db-driver
  dataFileConfigMap: devtest-config
  registry:
    fullName: devtest106-registry
  image:
    repository: esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/lisa
    pullPolicy: IfNotPresent
    tag: 10.7.0.168

The Portal

portal:
  enabled: true
  fullnameOverride: devtest106-portal
  databaseDriver: db-driver
  dataFileConfigMap: devtest-config
  registry:
    fullName: devtest106-registry
  storageClass:
    name: ""
  image:
    repository: esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/portal
    pullPolicy: IfNotPresent
    tag: 10.7.0.70

The VSE(s)

vse:
  enabled: true
  fullnameOverride: devtest106-vse
  databaseDriver: db-driver
  dataFileConfigMap: devtest-config
  registry:
    fullName: devtest106-registry
  volumeClaimTemplates:
    storageClassName: ""
  image:
    repository: esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/lisa
    pullPolicy: IfNotPresent
    tag: 10.7.0.168

The Virtual-Server-catalog

virtual-service-catalog:
  enabled: true
  fullnameOverride: devtest106-vsc
  databaseDriver: db-driver
  dataFileConfigMap: devtest-config
  image:
    repository: esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/virtual-service-catalog
    pullPolicy: IfNotPresent
    tag: 1.7.6.42

  1. Run the modified helm Upgrade command
    1. helm upgrade <helmnamespace> ./devtest –install –values ./custom-values.yaml –namespace <namespace>

Example:
helm upgrade devtest106 ./devtest-0.2.0.tgz --install --values ./custom-values.yaml --namespace devtest-106

Note: you cannot change the namespace once it is created. To change the namespace you would need to create the environment.

  1. Run the following command to check that the image version has been updated:

kubectl get pods -n devtest-106 -o jsonpath="{.items[*].spec.containers[*].image}" |\
tr -s '[[:space:]]' '\n' |\
sort |\
uniq –c


Example output:
1 esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/config-server:0.0.6.20
4 esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/lisa:10.7.0.168
1 esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/portal:10.7.0.70
1 esd-sv-docker-virtual.artifactory-lvn.broadcom.net/sv/virtual-service-catalog:1.7.6.42

Powered by Wolken Software