convert manifest to tf using tfk8s

Question

convert manifest to tf using tfk8s

Closed this issue 9 months ago · 4 comments

I like to use terraform by converting my k8 manifests to terraform using https://github.com/jrhouston/tfk8s. This is what terraform recommends here - https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs/resources/manifest#importing-existing-kubernetes-resources-as-kubernetes_manifest

I download the manifest file from https://github.com/kubernetes-sigs/hierarchical-namespaces/releases/download/v1.1.0/default.yaml
then I convert it. There are some status sections that are causing an error because TF will not allow the presence of status blocks in resource definitions,

Specifically, the status blocks in the Custom Resource Definitions for
hierarchicalresourcequotas.hnc.x-k8s.io
hierarchyconfigurations.hnc.x-k8s.io
hncconfigurations.hnc.x-k8s.io
subnamespaceanchors.hnc.x-k8s.io

Is there any special reason the high-level status blocks are there (the "status" section in the properties section of the openAPIV3Schema are not causing any issue - just the ones at the top level) ?

Answer 1 · 2024-12-10T00:16:00.000Z

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Answer 2 · 2025-01-09T00:48:04.000Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

Answer 3 · 2025-02-08T00:58:04.000Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen
Mark this issue as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Answer 4 · 2025-02-08T00:58:09.000Z

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen

Mark this issue as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.