Add reference architecture for using Kanister with Argo Workflows

[aish-where-ya]

Change Overview

This PR adds a reference architecture for using Kanister with Argo Workflows to automate creation of backup ActionSets.

Pull request type

Please check the type of change your PR introduces:

• 🚧 Work in Progress
• 🌈 Refactoring (no functional changes, no api changes)
• 🐹 Trivial/Minor
• 🐛 Bugfix
• 🌻 Feature
• 🗺️ Documentation
• 🤖 Test

Issues

• fixes Kanister with Argo Workflows #1514

Test Plan

• 💪 Manual
• ⚡ Unit test
• 💚 E2E

[github-actions]

Thanks for submitting this pull request 🎉. The team will review it soon and get back to you.

If you haven't already, please take a moment to review our project contributing guideline and Code of Conduct document.

[pavannd1]

I will break down my reviews into parts to speed things up

[viveksinghggits]

In most of the scenarios when we ask users to create an actionset using kanctl, we (kanctl) query a lot of things (k8s resources) that are passed to the kanctl command line tool.
So its, I think, I bit hard to figure out exact roles that a person need to be able to create an actionset. And that is the reason its a bit challenging to figure out the permissions that argo workflow needs to be able to create the actionset.
Also, I am not sure if giving cluster-admin role to the ServiceAccount is good idea.
Let's see what others say @pavannd1 @PrasadG193

[pavannd1]

@viveksinghggits The main goal of this document is to provide a reference to scheduling actions using Argo Workflows for interested users. Consider it as a tutorial similar to the blueprint examples and the Grafana/Loki example we have in the documentation. As with those documents (we make assumptions in there too), we are only showcasing how we integrate with ArgoWorkflows and not providing a standard way to schedule actions in Kanister. Given the purpose of this tutorial, I think it's acceptable to use the cluster-admin role. However, I agree with your concerns and we could iterate and find a more fine-grained Role that works for creating ActionSets as a follow-up.

[aish-where-ya]

I experimented with a lower admin role instead of cluster-admin. The pod to perform the workflow was not created.
The Argo documentation also allows you to create custom service accounts and then grant them the necessary permissions.

A note can be added saying that using the default service account and the mentioned privileges is not recommended in production and that the user can customize this based on their use case

[pavannd1]

This is looking good. I think it's well structured 👍🏼 💯
Minor improvements suggested. Should be good to merge once accepted.

One thing to follow up on in a separate PR would be to add commands to verify creations and deletions wherever they are missing.

[pavannd1]

LGTM! Good job @aish-where-ya 🥇

[pavannd1]

@viveksinghggits Please take a look

[viveksinghggits]

🚀