Terraform VMware Cloud Director Supplier v3.10.0 is obtainable 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, easy methods to deploy a Tanzu Kubernetes Grid Multi-cloud (TKGm) cluster through the use of the already current RDE capabilities that have been launched within the earlier v3.9.0 launch.
The brand 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 may enable 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 acquainted with Terraform to have the ability to create TKGm clusters utilizing the UI wizard.
Extending the Runtime Outlined Entity framework with new capabilities
A brand new set of sources and information sources will enable directors to outline and handle Behaviors of their current Outlined Interfaces and override them of their Outlined Entity Sorts:
Customers can even programmatically invoke Behaviors of their RDEs with the brand new launched model v2.21.0 of the go-vcloud-director SDK.
IP Area administration
Customers of VCD variations 10.4.1+ can now use IP Areas for his or her IP addressing wants. This performance is supported in terraform-provider-vcd with 4 new sources and their corresponding information sources:
Such an abundance of recent useful resource to make use of a not too long ago launched performance known as for a devoted information web page that explains the connection between new and outdated sources, and has a whole utilization instance.
Service account and API token administration
The brand new model of the supplier helps the creation and administration of Service Accounts and API tokens.
The brand new Service Account useful resource is designed to make it simpler to regulate service interplay with
your VCD setting. You’ll be able to handle the lifecycle of service accounts immediately throughout 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.
Equally, the brand new API Token useful resource lets you automate creating, renewing, and revoking API tokens. This makes it easy to handle the entry of purposes and companies to your VCD setting.
Distributed firewall administration enhancements
By fashionable demand, we have now added a brand new useful resource (and information supply) vcd_nsxt_distributed_firewall_rule that provides the aptitude 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. Moreover, vcd_vdc_group, has a brand new area remove_default_firewall_rule that helps to scrub up the default firewall rule.
Improved IPv6 assist
IPv6 configurations are actually validated by including a layer of automated exams and improved
IPv6 assist within the following manner:
Supplier VDC useful resource
The brand new useful resource vcd_provider_vdc permits customers with system administrator privileges to create and handle a supplier VDC. Two auxiliary information sources have 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 information supply (vcd_org_saml_metadata) permits customers to get the group’s (service supplier) SAML metadata, which is able to then be handed to the identification supplier. As soon as the directors get the identification supplier metadata, they will 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 must 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 obtainable: the vApp is just cloned from the supply vApp template or vApp.
In sure conditions, Terraform customers might require ignoring particular metadata entries added by a third get together to a given useful resource. This new model of the supplier provides a brand new experimental function that may enable 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 secret is “setting”.
This function features a mechanism to keep away from ignoring metadata entries that have 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 be able to see within the venture adjustments log.
And, as at all times, we’re awaiting your suggestions and recommendations on GitHub Points and #vcd-terraform-dev Slack channel (vmwarecode.slack.com).
