This message was deleted.
# generals
sparse-intern-71089
03/01/2019, 12:09 PMThis message was deleted.
s
stocky-spoon-28903
03/01/2019, 3:01 PMHi @polite-yacht-41549! Great to hear it’s looking good so far!
stocky-spoon-28903
03/01/2019, 3:02 PMSo, we don’t have TLS, MySQL or Huawei providers right now (though they are straightforward to bring up quickly if necessary!)
stocky-spoon-28903
03/01/2019, 3:03 PMOur Kubernetes support doesn’t really map cleanly to the TF provider as it’s a lot more complete and full-featured, but is something you’ll likely enjoy using directly - unfortunately tf2pulumi doesn’t work there though.
c
creamy-potato-29402
03/01/2019, 8:56 PMI would say that unless we see a significant uptake in TF k8s usage, we will probably not support it.
p
polite-yacht-41549
03/02/2019, 12:18 PMHi guys, thanks for repliing so quickly!
K8s would be the main reason why we'll switch to pulami. TF is pretty poor here, It is difficult to maintain k8s artifacts with HCL. I think there is no need to use tf2pulumi for k8s stuff.
Huawei we definitely need, would be great to have a wrapper of the terraform provider.
For MySQL databases and certificates / ssh keys any solution would be good, no need to actually migrate from TF.
One more thing which is crutial for a global enterprise like us, is having no dependency to a third party service for storing the state. Looking forward to the ongoing activities towards s3- support in that area.