Add MongoDB Resource Type and Kubernetes Terraform Recipe

[panagiotisbellias]

This PR introduces a new MongoDB resource type schema and an associated Kubernetes recipe using Terraform. It fully implements the requirements from GitHub Issue #21.

Changes included:

• Resource Schema: schemas/databases/mongodb.yaml defines required and optional properties, defaults, validation rules, and enums.
• Kubernetes Recipe: Terraform files provision MongoDB with:
  • Secret for credentials
  • Service
  • StatefulSet with optional PVC (controlled by persistence variable)
  • Resource requests/limits
• README.md: Complete documentation including inputs/outputs, manual testing steps, ephemeral testing snippet, and CI/GitHub Actions workflow description.
• GitHub Actions workflow: .github/workflows/test-mongodb-recipe.yml automatically tests the recipe on PRs and branch pushes, creating a temporary Kind cluster and cleaning up resources afterwards.

Manual Testing Results:

• Applied Terraform with persistence=false for CI-style testing.
• Pod test-mongodb-0 reached READY=1/1.
• Service created and accessible internally.
• Verified database operations.

Usage in Real Environments:

• Set persistence=true to enable PVC-backed storage.
• Configure storage_class according to the target Kubernetes environment.
• Provide secure and unique credentials for username and password.
• Optionally configure backup_enabled and backup_schedule for production backup requirements.
• Adjust resources (CPU/memory requests and limits) based on workload requirements.
• Apply Terraform against a production-ready cluster instead of a Kind cluster.

Closes #21

[Reshrahim]

@panagiotisbellias - Thanks for your interest in contributing!

Some high level thoughts:

• This repository follows a structure and pattern to organize and structure the resource-type definitions and Recipes. Please read the contributions guidelines thoroughly and make sure to follow the exact repository structure and naming conventions .
• Checkout the tutorial on Resource types -https://docs.radapp.io/tutorials/create-resource-type/ to understand how Resource types and Recipes work together.
• Resource type schema must follow the required metadata properties we use across other resource types (naming, descriptions, API versions). Please align it with existing schemas in the repo.
• Checkout the guide on How to Author Recipes to adhere to the structure
• README's should follow the exact structure as defined in the guidelines as they serve as the guidance for platform engineers
• For an alpha stage contribution, no automated test is required. Submit manual testing evidence following this https://github.com/radius-project/resource-types-contrib/blob/main/docs/contributing/testing-resource-types-recipes.md

Let me know if you need help with this. Would be happy to chat 1:1 as well in Discord.

[Reshrahim]

A GH workflow to test only the mongo type is not required and a manual evidence of testing is enough for alpha level contribution. Please review the testing guidelines.

[panagiotisbellias]

So I remove it but have no available environment to run terraform right now and I won't test

[Reshrahim]

Thanks for iterating on the feedback here. I’ve reviewed the schema definition and added a few suggestions.

Think of the schema as the interface that developers will use in their application definitions, and the Recipes as the implementation of that interface. The schema should remain as generic as possible, without Kubernetes-specific properties, while the Recipes handle the platform-specific details.