running a harness delegate on an ec2 k3s cluster
for enabling container based pipelines (CI, CD, IaCM, IDP)
leverage k3s for a simple single-node cluster, along with its helm controller for managing charts
No requirements.
| Name | Version |
|---|---|
| aws | 5.95.0 |
| harness | 0.37.3 |
No modules.
| Name | Type |
|---|---|
| aws_instance.k3s | resource |
| harness_platform_delegatetoken.k3s | resource |
| harness_platform_current_account.current | data source |
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| ami | AMI for the instance | string |
n/a | yes |
| delegate_docker_image | n/a | string |
"Delegate image to use" |
no |
| delegate_name | Name for the Harness Delegate | string |
"k3s" |
no |
| harness_org_id | Organization ID when creating an org or project level delegate | string |
null |
no |
| harness_project_id | Project ID when creating a project level delegate | string |
null |
no |
| iam_instance_profile | Instance profile to attach to instance | string |
null |
no |
| instance_type | Size of EC2 to provision. You will need at least 1vcpu and 2g memory | string |
"t3.small" |
no |
| replicas | Number of delegates to run | number |
1 |
no |
| subnet_id | Subnet to place the instance in | string |
n/a | yes |
| vpc_security_group_ids | Security groups to add to the instance | list(string) |
n/a | yes |
No outputs.