Skip to content

Comments

Update overview page, clarifying k8s and helm chart versions for TFE 1.0.x#1724

Closed
lucymhdavies wants to merge 1 commit intomainfrom
lucymhdavies-patch-1
Closed

Update overview page, clarifying k8s and helm chart versions for TFE 1.0.x#1724
lucymhdavies wants to merge 1 commit intomainfrom
lucymhdavies-patch-1

Conversation

@lucymhdavies
Copy link

@lucymhdavies lucymhdavies commented Jan 29, 2026

Per slack discussion: https://ibm-hashicorp.slack.com/archives/C09L2PDJ94L/p1769683032311139

From discussion with a customer today, they were confused by the - listed for Helm chart versions in the TFE releases overview page.

Once pointed to the 1.1.x page, this became clear.

So I think our docs should make this clear also.

Preview: https://unified-docs-frontend-preview-8v82b0xrl-hashicorp.vercel.app/terraform/enterprise/releases


Please go to the Preview tab and select the appropriate template:

Terraform

@github-actions
Copy link
Contributor

github-actions bot commented Jan 29, 2026

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Thu Jan 29 10:54:40 UTC 2026
Unified Docs API ✅ Ready (Inspect) Visit Preview Thu Jan 29 10:50:22 UTC 2026

@github-actions
Copy link
Contributor

github-actions bot commented Jan 29, 2026

Broken Link Checker

No broken links found! 🎉

@l2fprod
Copy link
Contributor

l2fprod commented Feb 2, 2026

@lucymhdavies (cc: @trujillo-adam )

Kubernetes/Nomad/Podman/Docker may all have the problem as potentially a 1.1.3 release could support different versions of these. The details of the supported versions is always available in the specific 1.0.x and 1.1.x pages.

so a better approach today would be to remove 1.0.x and 1.1.x rows from this table and have a statement telling the reader to go find the information in the specific release pages.

image

@trujillo-adam
Copy link
Contributor

trujillo-adam commented Feb 2, 2026

Fred and I had a brief discussion about this and agreed that we need a better long-term solution, but for as a short term fix maybe we abandon the table for post x.y.z versions and link to the release details page, for example:


## Supported environments

- Refer to [v1.1.x]() for details 
- Refer to [v1.0.x]() for details 

## Recent releases

{{ existing table for vYYYY -N}}

If that makes sense?

@lucymhdavies
Copy link
Author

As discussed on Slack, I agree with your suggestion to abandon the table for post x.y.z versions. I'll close this PR and let you continue the work ongoing in https://hashicorp.atlassian.net/browse/TF-32471

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants