Skip to content

chore(ci): use ru registry for release checks - #2476

Merged
candineer merged 2 commits into
mainfrom
chore/ci/change-registry-check-release
Jul 9, 2026
Merged

candineer merged 2 commits into
mainfrom
chore/ci/change-registry-check-release

Conversation

@candineer

@candineer candineer commented Jun 10, 2026 •

Copy link
Copy Markdown
Contributor

Description

Log in to the private RU registry in the release channels workflow and check module versions against registry.deckhouse.ru/deckhouse.

Why do we need it, and what problem does it solve?

Release channel checks need access to artifacts in the RU registry. This keeps the workflow and version check pointed at the registry that contains the expected release artifacts.

What is the expected result?

The release channels workflow logs in to the RU registry and the module version check completes without registry access errors.

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: ci
type: chore
summary: "Use the RU registry for release channel module version checks."
impact_level: low

Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
@candineer
candineer force-pushed the chore/ci/change-registry-check-release branch from 05e934c to 1020077 Compare June 10, 2026 17:05
Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
@candineer
candineer force-pushed the chore/ci/change-registry-check-release branch from e08e00c to c276ca2 Compare June 10, 2026 17:30
@nevermarine nevermarine modified the milestones: v1.9.1, v1.10.0 Jun 24, 2026
@candineer
candineer merged commit dbb09fc into main Jul 9, 2026
31 of 34 checks passed
@candineer
candineer deleted the chore/ci/change-registry-check-release branch July 9, 2026 12:47
deckhouse-BOaTswain pushed a commit that referenced this pull request Jul 16, 2026
Description
Log in to the private RU registry in the release channels workflow and check module versions against registry.deckhouse.ru/deckhouse.

Why do we need it, and what problem does it solve?
Release channel checks need access to artifacts in the RU registry. This keeps the workflow and version check pointed at the registry that contains the expected release artifacts.

---------

Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
deckhouse-BOaTswain pushed a commit that referenced this pull request Jul 22, 2026
Description
Log in to the private RU registry in the release channels workflow and check module versions against registry.deckhouse.ru/deckhouse.

Why do we need it, and what problem does it solve?
Release channel checks need access to artifacts in the RU registry. This keeps the workflow and version check pointed at the registry that contains the expected release artifacts.

---------

Signed-off-by: Nikita Korolev <nikita.korolev@flant.com>
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