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
Flux Subsystem for Argo already supports visualizing Terraform objects managed by https://github.com/weaveworks/tf-controller (to be clear this can be done with just Flux + weaveworks/tf-controller, and visualized with either FSA or any other supporting Flux UI). This benefits users who want to do Terraform + GitOps on Kubernetes without the requirement of subscribing to Terraform cloud.
However, Hashicorp cloud commercial customers are likely to prefer https://github.com/hashicorp/terraform-k8s over weaveworks/tf-controller, because it's certified for Hashicorp support, matches Hashicorp’s learning materials, etc. The subset of these users who are also Argo users could benefit from FSA additional support for visualizing Terraform objects managed by hashicorp/terraform-k8s just as it does for the same objects when managed by weaveworks/tf-controller.
The text was updated successfully, but these errors were encountered:
Flux Subsystem for Argo already supports visualizing Terraform objects managed by https://github.com/weaveworks/tf-controller (to be clear this can be done with just Flux +
weaveworks/tf-controller
, and visualized with either FSA or any other supporting Flux UI). This benefits users who want to do Terraform + GitOps on Kubernetes without the requirement of subscribing to Terraform cloud.However, Hashicorp cloud commercial customers are likely to prefer https://github.com/hashicorp/terraform-k8s over
weaveworks/tf-controller
, because it's certified for Hashicorp support, matches Hashicorp’s learning materials, etc. The subset of these users who are also Argo users could benefit from FSA additional support for visualizing Terraform objects managed byhashicorp/terraform-k8s
just as it does for the same objects when managed byweaveworks/tf-controller
.The text was updated successfully, but these errors were encountered: