Cloud Run add health check probes

Updates Cloud Run adapter to include startup and liveness probes

Updates Terraform Google provider version

Terraform Google provider version updated to include versions up to v6 to be able to use newer resource arguments

Updates Terraform Google provider version

Terraform Google provider version updated to include versions up to v5 to be able to use newer resources

Cloud Run containers resources bug fix

Bug Fix

Encountered an issue when updating a cloud run service using this module. Memory and CPU resources limits on containers were not being picked up.

Modified the for_each loop on gcp_cloudrun.tf containers resources dynamic block to do the correct lookups.

Update Kubernetes modules

Breaking Changes

• Minimum Kubernetes version is v1.23
• Update the minimum kubernetes provider version to 2.14.0 and max provider version <3.0.0
• Update all kubernetes terraform resources to v1 versions, apart from kubernetes_horizontal_pod_autoscaler which is upgraded to v2 to maintain use of metrics configuration
• ingress now has spec.default_backend instead of spec.backend
• spec.default_backend and spec.rule.http.path.*.backend have a different format, allowing either service or resource blocks ( see KUBERNETES.md for example)

Fixes

• Add metadata configuration for kubernetes cronjob job
• Address Snyk vulnerability alerts

Changes

• Change logic behind port configuration in kubernetes_services_v1
• New container_resource metric in k8s_pod_autoscaler
• Updated App Engine security_level default to SECURE_ALWAYS

Cloud Run patch

Modified gcp_outputs.tf file to include cloudrun_service_ids output needed on LB deployments

Cloud Run Revision Name Bug Fix

Bug Fix

Encountered an issue when attempting to update a cloud run service using this module. The update failed as it attempted to replace an existing revision (google.cloud.run.v1.Services.ReplaceService). The error received in Google Cloud Logging was Revision named '[service]-[previous-revision-name]' with different configuration already exists.

It is possible that in this case templates.metadata.name was present during import, so terraform set autogenerate_revision_name to false (see documentaion).
Added the missing autogenerate_revision_name key to the module, which is set to:

• true if there is nothing specified in template.metadata.name
• false if autogenerate_revision_name attribute is set to false in gcp_cloudrun.yml
• false if template.metadata.name is specified, regardless of what autogenerate_revision_name is set to in gcp_cloudrun.yml

Changes

• Removed google_project_service service, therefore requiring iam.googleapis.com and run.googleapis.com APIs to be enabled before deployment.
• Removed the default annotation "run.googleapis.com/ingress-status" = "all" as that is an output only annotation that does not need to be set in module.
• Updated documentation and unit tests to reflect changes

MCP Services Initial Release

Initial release of MCP Services Modules after separation from the Terraform Infrastructure Modules repository

Changes

• Add Cloud Run secrets functionality, giving the ability to attach existing secrets as volumes and/or environment variables
• Removed project creation from Cloud Run module as project creation will be handles in MCP Foundations modules
• Removed Artifact Registry repository creation from Cloud Run module. It was unnecessary as images for cloud run services must exist before deployment of the module