New Features
ZEDEDA Edge Kubernetes Service management
You can now manage ZEDEDA Edge Kubernetes Service clusters directly through Terraform, enabling infrastructure-as-code automation for your Kubernetes deployments at the edge.
- zedcloud_kubernetes_cluster: Create and manage ZEDEDA Edge Kubernetes Service cluster instances by defining cluster names, project associations, node configurations, and cluster interfaces. You can specify nodes with their cluster interface settings and organize clusters using tags.
- zedcloud_kubernetes_cluster_group: Group multiple ZEDEDA Edge Kubernetes Service clusters together for coordinated management. Cluster groups support YAML manifests that you can apply across all member clusters simultaneously.
- zedcloud_kubernetes_cluster_status: Retrieve detailed status information for your ZEDEDA Edge Kubernetes Service clusters, including Kubernetes version, node count, deployment count, run state, and resource capacity metrics for CPU, memory, and pods.
- zedcloud_kubernetes_cluster_import: Import existing external Kubernetes clusters into ZEDEDA Cloud management. You can bring pre-existing clusters under Terraform control by specifying the cluster details and node configurations.
- zedcloud_cluster_group_manifest: Retrieve and manage Kubernetes manifests for cluster groups, allowing you to access the YAML content that defines cluster group configurations.
Kubernetes deployments and Helm charts
You can now deploy applications to your ZEDEDA Edge Kubernetes Service clusters using Helm charts managed entirely through Terraform.
- zedcloud_kubernetes_deployment: Deploy Helm charts to target Kubernetes clusters. You can specify the chart name, version, repository, custom values, and target clusters. The resource supports deploying to specific clusters or multiple clusters based on metadata.
- zedcloud_helm_chart_management: Upload and manage Helm chart files in ZEDEDA Cloud. You can reference these charts in your deployment configurations.
GitOps integration
You can now configure GitOps workflows to automatically synchronize Kubernetes deployments from Git repositories.
- zedcloud_kubernetes_gitops: Define GitOps configurations that connect Git repositories to your ZEDEDA Edge Kubernetes Service clusters. You can specify the repository URL, branch, paths to monitor, and target deployment scope (individual cluster, cluster group, or all clusters). The resource supports both public and private repositories with SSH or basic authentication.
Secrets management
You can now manage authentication credentials for private repositories through Terraform.
- zedcloud_kubernetes_secret: Create and manage Kubernetes secrets for authenticating with private Git repositories and Helm registries. You can configure SSH key pairs or username/password credentials with base64-encoded values.
Private repository configuration
You can now configure access to private Helm repositories for your deployments.
- zedcloud_private_helm_repository: Define private Helm repository connections with authentication. You can specify repository URLs, types (Helm index or Git), and authentication secrets to access charts from private registries.
Network instance configuration
- LLDP forwarding: You can now enable Link Layer Discovery Protocol (LLDP) frame forwarding on switch-type network instances by setting the forward_lldp attribute. This allows LLDP frames to pass through for network topology discovery and management tools.
Enhancements
Documentation updates
- Comprehensive documentation has been added for all new ZEDEDA Edge Kubernetes Service-related resources and data sources.
- Example Terraform configurations have been expanded to demonstrate ZEDEDA Edge Kubernetes Service cluster provisioning, GitOps setup, and Helm deployments.
Key Fixes
- GitOps path filtering: The path_list attribute in GitRepoRepositoryDetails is now correctly honored, allowing you to specify specific paths within a Git repository to monitor for changes.
- GitOps authentication: Authentication parameter handling for GitOps flows has been corrected, ensuring proper credential configuration for private repositories.
- Base image state management: Fixed an issue where the imgvol field in base image resources would incorrectly show differences during plan operations when no actual changes were made.
- Cluster configuration state: Fixed spurious diff detection for cluster_interface and edge_node_cluster fields, preventing unnecessary plan changes when the underlying resource state had not changed.
Limitations
You cannot use the manifest field of the edge-node cluster schema in this release. The field is mainly for internal purposes, but it will be available in the next release along with additional fields.
Find the official Terraform Provider Release Notes in the GitHub repository.