You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added autoscaler, I feel like it either needs a feature flag to enable it, or we need to get rid of the existing workers implementation, since there is not much point in having it if the cluster autoscales on its own
# Outputs:
Initializing the backend...
Initializing provider plugins...
- Finding alekc/kubectl versions matching ">= 2.1.3"...
- Finding hashicorp/tls versions matching ">= 4.0.6"...
- Finding latest version of hashicorp/kubernetes...
- Finding hetznercloud/hcloud versions matching ">= 1.50.1"...
- Finding siderolabs/talos versions matching ">= 0.7.1"...
- Finding hashicorp/http versions matching ">= 3.4.5"...
- Finding hashicorp/helm versions matching ">= 2.17.0"...
- Installing hashicorp/http v3.5.0...
- Installed hashicorp/http v3.5.0 (signed by HashiCorp)
- Installing hashicorp/helm v2.17.0...
- Installed hashicorp/helm v2.17.0 (signed by HashiCorp)
- Installing alekc/kubectl v2.1.3...
- Installed alekc/kubectl v2.1.3 (self-signed, key ID 772FB27A86DAFCE7)
- Installing hashicorp/tls v4.1.0...
- Installed hashicorp/tls v4.1.0 (signed by HashiCorp)
- Installing hashicorp/kubernetes v2.36.0...
- Installed hashicorp/kubernetes v2.36.0 (signed by HashiCorp)
- Installing hetznercloud/hcloud v1.50.1...
- Installed hetznercloud/hcloud v1.50.1 (signed by a HashiCorp partner, key ID 5219EACB3A77198B)
- Installing siderolabs/talos v0.8.0...
- Installed siderolabs/talos v0.8.0 (signed by a HashiCorp partner, key ID AF0815C7E2EC16A8)
Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
# Errors:
🤖 Terraform Validate: ✅
# Outputs:
Success! The configuration is valid.
# Errors:
# Outputs:
Initializing the backend...
Initializing provider plugins...
- Finding hashicorp/helm versions matching ">= 2.17.0"...
- Finding alekc/kubectl versions matching ">= 2.1.3"...
- Finding hashicorp/tls versions matching ">= 4.0.6"...
- Finding hetznercloud/hcloud versions matching ">= 1.50.1"...
- Finding latest version of hashicorp/kubernetes...
- Finding siderolabs/talos versions matching ">= 0.7.1"...
- Finding hashicorp/http versions matching ">= 3.4.5"...
- Installing alekc/kubectl v2.1.3...
- Installed alekc/kubectl v2.1.3 (self-signed, key ID 772FB27A86DAFCE7)
- Installing hashicorp/tls v4.1.0...
- Installed hashicorp/tls v4.1.0 (signed by HashiCorp)
- Installing hetznercloud/hcloud v1.50.1...
- Installed hetznercloud/hcloud v1.50.1 (signed by a HashiCorp partner, key ID 5219EACB3A77198B)
- Installing hashicorp/kubernetes v2.36.0...
- Installed hashicorp/kubernetes v2.36.0 (signed by HashiCorp)
- Installing siderolabs/talos v0.8.0...
- Installed siderolabs/talos v0.8.0 (signed by a HashiCorp partner, key ID AF0815C7E2EC16A8)
- Installing hashicorp/http v3.5.0...
- Installed hashicorp/http v3.5.0 (signed by HashiCorp)
- Installing hashicorp/helm v2.17.0...
- Installed hashicorp/helm v2.17.0 (signed by HashiCorp)
Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
# Errors:
🤖 Terraform Validate: ✅
# Outputs:
Success! The configuration is valid.
# Errors:
Okay, I've looked at it and have a few comments that I'll write down if you want to continue developing the PR. Are you interested in continuing to develop it, or are you already at the point in the other repo where you're no longer interested in this PR?
Yeah, I don't think that im interested in further working on this PR mostly because my rewrite has come much further compared to this module (tho not complete yet)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added autoscaler, I feel like it either needs a feature flag to enable it, or we need to get rid of the existing workers implementation, since there is not much point in having it if the cluster autoscales on its own
Please let me know what the next steps should be
Resolves: #16