Pipeline validates upgrade instructions

[izgeri]

At current, we don't do any validation of the helm upgrade process in our pipeline.

In this issue, we'd like to add some automation to our pipeline to validate basic upgrade flows automatically, to reduce the XA load.

Before starting work on this card, please define the plan in a comment and seek feedback from the team.

Last XA plan (not everything necessarily needs to be tested in the pipeline, just sharing here for reference):

• Standard Conjur version upgrade post-release, deploys PG - Run default deploy flow in a recent K8s version using Helm v3 with Conjur v1.x and then run helm upgrade to Conjur v1.{x+1}. Verify:
  • Works as expected
  • Conjur certs are managed appropriately after upgrade
  • Data still available after upgrade via API
• Standard Conjur version upgrade post-release, remote PG - Run same flow as before, but with a remote PG instance
• Upgrade from old helm chart release to new helm chart release