Update current version for eck to 3.3.0

[naemono]

To be merged only on the day of ECK 3.3.0 release!

Release is currently planned for Jan 27, 2026.

[reakaleek]

This should be fine. But FYI, we have an automation that would bump this based on the elastic/cloud-on-k8s repo.

docs-builder/.github/updatecli/updatecli.d/versions.yml

Lines 195 to 206 in 4d2c781

	latest-eck-version:
	name: Get latest release version for Elastic Cloud on Kubernetes
	kind: githubrelease
	transformers:
	- trimprefix: v
	spec:
	owner: elastic
	repository: cloud-on-k8s
	token: '{{ requiredEnv "GITHUB_TOKEN" }}'
	username: '{{ requiredEnv "GITHUB_ACTOR" }}'
	versionfilter:
	kind: latest

cc @theletterf

TL;DR as soon as there is a github release on elastic/cloud-on-k8s, the automation should pick it up.

[naemono]

TL;DR as soon as there is a github release on elastic/cloud-on-k8s, the automation should pick it up.

I came here to merge this today, and am seeing this... I'll hold off and verify if this is working properly for us...

[naemono]

This should be fine. But FYI, we have an automation that would bump this based on the elastic/cloud-on-k8s repo.

docs-builder/.github/updatecli/updatecli.d/versions.yml

Lines 195 to 206 in 4d2c781

	latest-eck-version:
	name: Get latest release version for Elastic Cloud on Kubernetes
	kind: githubrelease
	transformers:
	- trimprefix: v
	spec:
	owner: elastic
	repository: cloud-on-k8s
	token: '{{ requiredEnv "GITHUB_TOKEN" }}'
	username: '{{ requiredEnv "GITHUB_ACTOR" }}'
	versionfilter:
	kind: latest

cc @theletterf

TL;DR as soon as there is a github release on elastic/cloud-on-k8s, the automation should pick it up.

@reakaleek ECK was released yesterdayhttps://github.com/elastic/cloud-on-k8s/releases/tag/v3.3.0, but this still isn't merged. Does it just take longer?

[reakaleek]

@naemono it looks like eck was already updated in #2622 and is up-to-date on main.

https://github.com/elastic/docs-builder/blob/main/config/versions.yml#L22

I think you are still seeing the green merge button because this PR is not up-to-date with the base branch.

[reakaleek]

This PR can be closed

[naemono]

@reakaleek Oh ok. So we don't need to create these at all in the future it seems. 👍