[Addon] Add Crossplane Azure Addon for provisioning Cloud Resources on Azure

[yogeshselvarajan]

Title

[Addon] Add Crossplane-Azure Addon

Description of your changes

This PR adds the Crossplane-Azure addon to the KubeVela catalog as an experimental addon. The addon facilitates the provisioning of Azure resources like Resource Groups, Virtual Networks, and Storage Accounts via Crossplane on KubeVela.

• It contains necessary components, including CUE files and provider configurations, as well as a detailed README.md file explaining the usage, installation, and authentication setup.
• Additionally, examples are provided in the examples directory, showing the Azure Resource Group, Virtual Network, and Storage Account creation.

How has this code been tested?

I have copied the entire addon directory crossplane-azure, which contains the CUE files and provider files. I tested this locally by using the following command:

vela addon enable ./<the-directory-path>

After enabling the addon, I verified the resource provisioning in my Azure portal. The expected resources (Resource Group, Virtual Network, and Storage Account) were successfully created.

Checklist

I have:

• [✔] Title of the PR starts with type (e.g. [Addon], [example], or [Doc]).
• [✔] Updated/Added relevant documentation and examples.
• [✔] Placed the new addon in experimental.
• [✔] Updated the addon version in metadata.yaml.

Request for Reviewers

Dear Maintainers,

This PR introduces the Crossplane-Azure addon for provisioning Azure resources (Resource Groups, VNETs, Storage Accounts) via Crossplane in KubeVela. I kindly request that this addon (Crossplane-Azure), along with the Crossplane and Crossplane-AWS addons (currently in experimental), be promoted to public. This would enable users to manage cloud resources more efficiently across Azure and AWS using Kubevela.

In future updates, I plan to add more CUE files for Azure resources to expand its provisioning capabilities from KubeVela. I will include the proper CUE files using the Azure CRDs for Crossplane (refering Azure CRDs for Crossplane).

[anoop2811]

Can you make sure your commits are signed?

[yogeshselvarajan]

Can you make sure your commits are signed?

@anoop2811 Yes, I have followed the steps and signed the commit. I have force-pushed the commit again with signing using the following commands:

git rebase HEAD~1 --signoff
git push --force-with-lease origin crossplane-azure-addon

[anoop2811]

Thank you for your contrinution @yogeshselvarajan !

[yogeshselvarajan]

Thank you for your contrinution @yogeshselvarajan !

@anoop2811 Thanks for approving this addon PR. I hope this will greatly benefit KubeVela users 🌟. Could you please guide me on the procedure to promote this addon from experimental to a main addon? It has passed the e2e tests and includes a detailed README, which will be helpful for users.

Additionally, I would like to request the promotion of the Crossplane experimental addon (a necessary dependency) to verified/public status.

Please let me know the steps required for this 😊

[yogeshselvarajan]

Also @anoop2811, I see that the PR has been merged, but I noticed that my new addon isn't reflecting in the KubeVela UI. I can only see the existing Crossplane and Crossplane-AWS addons (attached screenshot), with the expeiremntal addon source too enabled in the KubeVela.

Should I be updating something like an OSS bucket, or is there a need to modify the invisible tag in the addon file? Please advise on what might be missing.