Terraform VMware Cloud Director Provider v3.10.0 is accessible now, introducing many new options and enhancements.
Introducing a brand new information to deploy Kubernetes clusters utilizing Container Service Extension (CSE) v4.0
This new model of the supplier provides a brand new CSE information that explains, step-by-step, methods to deploy a Tanzu Kubernetes Grid Multi-cloud (TKGm) cluster by utilizing the already current RDE capabilities that had been launched within the earlier v3.9.0 launch.
The new information comes with a set of configuration information that can be utilized as a place to begin, exhibiting an actual instance of making a TKGm cluster in VCD.
The Container Service Extension v4.0 set up information has additionally been upgraded to utilize
the brand new UI Plugin useful resource, that can permit directors to totally automate their setup by putting in
the “Kubernetes Container Clusters UI plug-in v4.0”, for his or her tenant customers who should not conversant in Terraform to have the ability to create TKGm clusters utilizing the UI wizard.
Extending the Runtime Defined Entity framework with new capabilities
A brand new set of sources and knowledge sources will permit directors to outline and handle Behaviors of their current Defined Interfaces and override them of their Defined Entity Types:
Users may also programmatically invoke Behaviors of their RDEs with the brand new launched model v2.21.0 of the go-vcloud-director SDK.
IP Space administration
Users of VCD variations 10.4.1+ can now use IP Spaces for his or her IP addressing wants. This performance is supported in terraform-provider-vcd with 4 new sources and their corresponding knowledge sources:
Such an abundance of latest useful resource to make use of a not too long ago launched performance referred to as for a devoted information web page that explains the connection between new and previous sources, and has an entire utilization instance.
Service account and API token administration
The new model of the supplier helps the creation and administration of Service Accounts and API tokens.
The new Service Account useful resource is designed to make it simpler to regulate service interplay with
your VCD atmosphere. You can handle the lifecycle of service accounts immediately inside the supplier. This facilitates granular permissions administration, permitting you to outline the precise scope of entry for every service, decreasing safety dangers and selling extra environment friendly operations.
Similarly, the brand new API Token useful resource permits you to automate creating, renewing, and revoking API tokens. This makes it simple to handle the entry of purposes and companies to your VCD atmosphere.
Distributed firewall administration enhancements
By fashionable demand, we now have added a brand new useful resource (and knowledge supply) vcd_nsxt_distributed_firewall_rule that provides the potential of managing firewall guidelines one after the other versus already current vcd_nsxt_distributed_firewall that handles all firewall guidelines in a single useful resource. Additionally, vcd_vdc_group, has a brand new area remove_default_firewall_rule that helps to wash up the default firewall rule.
Improved IPv6 help
IPv6 configurations at the moment are validated by including a layer of automated checks and improved
IPv6 help within the following method:
Provider VDC useful resource
The new useful resource vcd_provider_vdc permits customers with system administrator privileges to create and handle a supplier VDC. Two auxiliary knowledge sources had been launched to facilitate the creation of a supplier VDC: vcd_resource_pool and
SAML configuration for organizations
System directors can set and modify SAML configuration for a selected group utilizing vcd_org_saml. To assist arrange the SAML service, a companion knowledge supply (vcd_org_saml_metadata) permits customers to get the group’s (service supplier) SAML metadata, which can then be handed to the id supplier. Once the directors get the id supplier metadata, they’ll use such a file to set the service.
Cloned vApp operations
vcd_cloned_vapp is a useful resource that creates vApps from both a vApp template or one other vApp. This useful resource ought to be used solely on creation, though deletion additionally works. The results of utilizing this useful resource is a daily vApp (vcd_vapp), with all its contents derived by both a vApp template or one other vApp. As of this primary implementation, no configuration is accessible: the vApp is solely cloned from the supply vApp template or vApp.
In sure conditions, Terraform customers might require ignoring particular metadata entries added by a third occasion to a given useful resource. This new model of the supplier provides a brand new experimental function that can permit ignoring the metadata entries configured within the supplier block. For instance:
This setup will make the supplier ignore all metadata entries set in Organizations named “client1” and which key’s “environment”.
This function features a mechanism to keep away from ignoring metadata entries that had been set by Terraform itself, offering customers higher management of what they’re configuring and higher suggestions.
There are extra full options and enhancements, which you’ll see within the undertaking modifications log.
And, as at all times, we’re awaiting your suggestions and ideas on GitHub Issues and #vcd-terraform-dev Slack channel (vmwarecode.slack.com).