Upgrade Strategy on K8S

For upgrading MetaDefender ICAP Server the container of the application contains the automation to upgrade the database schema and migrate the configuration data. The strategy recommended to use is

  • Rolling Update ( Easy deployment where functionality test with new version is based on Kubernetes Probes )

As indicated in , the Kubernetes probes like Readiness and Liveness probes help the application to control the expected behavior, not to have a downtime, when doing an upgrade.

Rolling Update Strategy

When using the Rolling Update strategy provided by Kubernetes technology, these are the main points to consider

  • Traffic wont be sent to new pods until readiness probe is successful
  • Old version pods won’t be terminated until new version pods are ready to serve traffic
  • Rolling Update is the default strategy for deployment

Step by step using kubectl

  • Set new image version on the MetaDefender ICAP Server deployment
Bash
Copy

Step by step using helm

  • Set new image version in values.yaml helm file
values.yaml
Copy
  • Run helm upgrade command with the environment variables desired if not indicated in values.yaml file when first deployment
Bash
Copy

Rollout Failed Update

MetaDefender ICAP run the upgrade over the same database. So to rollout it is needed to change the database using the backup created before upgrading. Once the database contains the previous version the deployment can be rollout

Bash
Copy
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
Connect the ICAP Client outside K8s to ICAP on K8s
On This Page
Upgrade Strategy on K8SRolling Update StrategyStep by step using kubectlStep by step using helmRollout Failed Update