Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Kubernetes provider manifests from YAML #150

Closed
ghost opened this issue Mar 30, 2018 · 2 comments
Closed

Feature request: Kubernetes provider manifests from YAML #150

ghost opened this issue Mar 30, 2018 · 2 comments

Comments

@ghost
Copy link

ghost commented Mar 30, 2018

This issue was originally opened by @okgolove as hashicorp/terraform#17741. It was migrated here as a result of the provider split. The original body of the issue is below.


Terraform Version

Terraform v0.11.5

Terraform Configuration Files

Debug Output

Crash Output

Expected Behavior

I want to use native k8s provider, but I don't want to write k8s spec in HCL. It would be great if I can import k8s spec from yaml files which used for kubectl.

Actual Behavior

I have to write spec in HCL

Steps to Reproduce

Additional Context

References

https://stackoverflow.com/questions/47236358/can-you-define-kubernetes-services-pods-using-yaml-in-terraform

@captn3m0
Copy link

captn3m0 commented Apr 7, 2018

This exists as a third-party provider: https://github.com/ericchiang/terraform-provider-k8s

@radeksimko
Copy link
Member

Hi @okgolove 👋
thanks for raising this question.

Supporting YAML/JSON was considered before (the very first proposal of K8S provider was exactly that) and during the initial implementation of this provider and we decided not to do it. For that reason I'm going to close this issue as we have no intentions of implementing it nor accepting PRs which accept raw configs in JSON/YAML.

Feel free to use the provider @captn3m0 mentioned above.

Full discussion: hashicorp/terraform#3132

TL;DR version (summary): hashicorp/terraform#3453 (comment)

@ghost ghost locked and limited conversation to collaborators Apr 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants