Skip to content

docs: 1.47 release notes - #1320

Merged
codyjlandstrom merged 1 commit into
mainfrom
release-notes-1.47
Aug 5, 2026
Merged

docs: 1.47 release notes#1320
codyjlandstrom merged 1 commit into
mainfrom
release-notes-1.47

Conversation

@codyjlandstrom

@codyjlandstrom codyjlandstrom commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

What

Drafts the release notes for Chart 1.47 / CLI 3.22.0. Draft until the release cut — see open items below.

1.47.0 release notes entry

Changes from review (ifbyol)

  • okteto destroy --all fix stays under 1.46 — it shipped in CLI 3.21.0 as a backport ([Backport release-3.21] Fix "okteto destroy --all" hanging on sleeping namespaces okteto#5073); the 1.46 entry is restored untouched (a source comment now records the backport PR). The 1.47 re-listing is dropped.
  • Routine dependency CVE bumps (Go/kubectl/helm/syncthing) removed — not listed in release notes by convention.
  • Sleep-job HTTPRoute fix (DEV-1440) omitted — Gateway API is not yet open to all customers; tracked internally on the release page.

Relationship to #1312

The x-enable-service-links reference entry is intentionally not part of this PR — #1312 (open) already adds it to the Docker Compose reference. The release-notes bullet links to the page level for now; a TODO comment marks where to switch to the #x-enable-service-links-boolean-optional anchor once #1312 merges. Two facts worth adding to #1312 during its review: the field requires Okteto CLI 3.22.0+, and it applies to the pod spec whether the service runs as a Deployment, StatefulSet, or Job.

Open items before marking ready

yarn build passes (Node 22).

🤖 Generated with Claude Code

@netlify

netlify Bot commented Aug 4, 2026

Copy link
Copy Markdown

Deploy Preview for okteto-docs ready!

Name Link
🔨 Latest commit 6294955
🔍 Latest deploy log https://app.netlify.com/projects/okteto-docs/deploys/6a722c567eba5e00082209cb
😎 Deploy Preview https://deploy-preview-1320--okteto-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Comment on lines -28 to -31
### Bug Fixes {#bug-fixes-1.46}

- [Okteto CLI 3.21.0](https://github.com/okteto/okteto/releases/tag/3.21.0): Fixed `okteto destroy --all` hanging until it timed out, and reporting a false error, when run against a Sleeping Namespace. The command now completes and leaves the Namespace in its previous status <!-- okteto/okteto#5072 -->

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be kept. The fix was included in 3.21.0 as a backport once the release was cut, but it went out in that version

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed — the fix is in the 3.21.0 tag history as a backport: commit 20be1c9b, "Fix "destroy all" hanging when namespace is sleeping (#5072) (#5073)". I'd only checked the 3.21.0...3.22.0-beta.1 compare range, which lists the master merge SHA but not the cherry-picked twin. Restored the 1.46 entry — this PR no longer touches the versioned docs; the only change is a source comment on the current-docs entry recording the #5073 backport.


### New Features {#new-features-1.47}

- **Disabling Kubernetes service links in Docker Compose**: Docker Compose services now support a per-service [`x-enable-service-links`](reference/docker-compose.mdx) field. <!-- TODO: link the #x-enable-service-links-boolean-optional anchor once okteto/docs#1312 merges --> Set it to `false` to stop Kubernetes from injecting service link environment variables such as `<SERVICE>_SERVICE_HOST` and `<SERVICE>_PORT` into the service's containers, which can break applications that expect a plain port number — or no value — under those names. This brings Docker Compose deployments to parity with `enableServiceLinks: false` in Kubernetes manifests. The field is opt-in and requires Okteto CLI 3.22.0 or later <!-- PROD-495, DEV-1449, okteto/okteto#5093, okteto/okteto#5097 -->

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a explicit message for the TODO comment, to remember to be filled before merging it

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tracked in the PR checklist ("Merge #1312, then switch the x-enable-service-links link to the section anchor"). The link stays page-level for now because onBrokenAnchors: 'throw' would fail the build against an anchor that only exists in the unmerged #1312.

Comment thread src/content/release-notes.mdx Outdated
### Improvements {#improvements-1.47}

- **Okteto skill setup from the Namespace view**: The Namespace view now includes a shortcut to set up the Okteto skill, making [Agentic Workflows](agentic/index.mdx) easier to discover <!-- DEV-1434 · TODO: confirm final UI copy with Frontend before release -->
- [Okteto CLI 3.22.0](https://github.com/okteto/okteto/releases/tag/3.22.0): Upgraded the Go toolchain and the bundled `kubectl`, `helm`, and `syncthing` binaries to address known CVEs <!-- okteto/okteto#5098, okteto/okteto#5100 -->

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We usually don't include this in the release notes, as this is something we do mostly in all the releases

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed. Checked 1.44–1.46 and routine dependency bumps indeed aren't listed — the ingress-nginx entries were specific high-severity CVEs, which is a different case.

Comment thread src/content/release-notes.mdx Outdated
### Bug Fixes {#bug-fixes-1.47}

- [Okteto CLI 3.22.0](https://github.com/okteto/okteto/releases/tag/3.22.0): Fixed the CLI hanging without output — or crashing with a goroutine deadlock error — when the connection to BuildKit through the port-forward failed. The CLI now reports the connection error <!-- DEV-1441, okteto/okteto#5083 -->
- [Okteto CLI 3.22.0](https://github.com/okteto/okteto/releases/tag/3.22.0): Fixed `okteto destroy --all` hanging until it timed out, and reporting a false error, when run against a Sleeping Namespace. The command now completes and leaves the Namespace in its previous status. This fix was previously listed under 1.46, but it ships with Okteto CLI 3.22.0 <!-- okteto/okteto#5072 -->

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was done in previous release, so we could remove it from here

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed — same conclusion as the thread on the versioned file: the fix shipped in 3.21.0 via the #5073 backport, so the 1.46 entry stands and there's nothing to list under 1.47.

Comment thread src/content/release-notes.mdx Outdated

- [Okteto CLI 3.22.0](https://github.com/okteto/okteto/releases/tag/3.22.0): Fixed the CLI hanging without output — or crashing with a goroutine deadlock error — when the connection to BuildKit through the port-forward failed. The CLI now reports the connection error <!-- DEV-1441, okteto/okteto#5083 -->
- [Okteto CLI 3.22.0](https://github.com/okteto/okteto/releases/tag/3.22.0): Fixed `okteto destroy --all` hanging until it timed out, and reporting a false error, when run against a Sleeping Namespace. The command now completes and leaves the Namespace in its previous status. This fix was previously listed under 1.46, but it ships with Okteto CLI 3.22.0 <!-- okteto/okteto#5072 -->
- Fixed the Namespace sleep job intermittently failing with a conflict error while updating HTTPRoutes, which could leave endpoints of a Sleeping Namespace returning a 503 error instead of waking the environment. This only affects clusters with the Gateway API enabled <!-- DEV-1440 -->

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have doubts about this, should we include it? It is not a feature completely open to all the customers

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed from the public notes. Gateway API is staying out of 1.47 customer comms (it's tracked as an internal workstream on the release page), so a public bullet naming HTTPRoutes would get ahead of the rollout. The fix stays documented internally and we can surface it when Gateway API is announced.

@codyjlandstrom codyjlandstrom changed the title docs: 1.47 release notes + x-enable-service-links reference docs: 1.47 release notes Aug 4, 2026
Add the 1.47.0 release notes entry: BuildKit 0.31 upgrade with the
oci-mediatypes default change and its OKTETO_BUILD_OCI_MEDIATYPES
opt-out, x-enable-service-links for Docker Compose, the Okteto skill
shortcut in the Namespace view, and the BuildKit port-forward
deadlock fix.

Per review (ifbyol): the okteto destroy --all fix stays under 1.46 -
it shipped in CLI 3.21.0 as a backport (okteto/okteto#5073); routine
dependency CVE bumps are not listed per convention; the sleep-job
HTTPRoute fix is omitted since Gateway API is not yet open to all
customers.

The x-enable-service-links reference entry is covered by the open
#1312; the release-notes link points at the page level
until that PR merges.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Cody Landstrom <cody@okteto.com>
@codyjlandstrom
codyjlandstrom marked this pull request as ready for review August 4, 2026 19:05
@codyjlandstrom
codyjlandstrom merged commit 5ff154b into main Aug 5, 2026
4 checks passed
@codyjlandstrom
codyjlandstrom deleted the release-notes-1.47 branch August 5, 2026 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants