[CI] Add end-to-end testing of Meshery Operator deployments

[leecalcote]

Current Behavior

In order to verify whether changes in a PR are positive and resolve the issue at-hand, we'll want to test.

Desired Behavior

In general, the meshery-operator repo is egregiously missing such tests. Let's fix that.

Implementation

1. copy/paste a workflow from the meshery/meshery repo that checks out a golang program, build the docker container image for meshery-operator
2. deploys a kind cluster and installs the meshery-operator helm chart using the freshly built image.

Acceptance Tests

1. This is just a smoke test. Deeper tests will come later in order to verify MeshSync.

---

Contributor Guides and Resources

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma (open invite)
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

[leecalcote]

@n2h9 do you have this covered?

[n2h9]

@n2h9 do you have this covered?

Hey, Lee hello 👋

No, this flow is not covered.
There is this test: meshery/meshery#14626 which is testing meshery server side. It deploys operator, but from helm chart.

The flow sounds great to me 😇 , I would also add here point 3: subscribe to nats topic and check that meshsync produces some reasonable output.

[n2h9]

By the way, if it is not super urgent, I am interested to work on this issue (could you please assign it to me) 🙂
I like to develop such kind of tests 😄 😇

Thank you 🙇‍♀