Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(core, dvcr): configure dvcr creds before contatinerd config #128

Merged
merged 1 commit into from
Jun 13, 2024

Conversation

yaroslavborbat
Copy link
Member

@yaroslavborbat yaroslavborbat commented Jun 13, 2024

Description

Fix the order of configuration steps to ensure that DVCR credentials are configured before merging containerd configurations.

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

We currently have a bashible step 032_configure_containerd.sh with a weight of 32. This step merges the containerd configurations, which requires correct DVCR (Docker V2 Container Registry) credentials. To solve the problem where DVCR credentials must be configured in advance, this PR introduces a lower weight configuration step that runs before the containerd configuration step.

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.

Signed-off-by: yaroslavborbat <[email protected]>
@fl64 fl64 changed the title fix(core, dvcr): increase weight fix(core, dvcr): change nodegroupconfiguration weight Jun 13, 2024
@fl64 fl64 changed the title fix(core, dvcr): change nodegroupconfiguration weight fix(core, dvcr): configure dvcr creds before contatinerd config Jun 13, 2024
@fl64 fl64 self-requested a review June 13, 2024 07:39
@yaroslavborbat yaroslavborbat merged commit 6cc4d26 into main Jun 13, 2024
25 of 28 checks passed
@yaroslavborbat yaroslavborbat deleted the fix/dvcr-step branch June 13, 2024 07:50
universal-itengineer pushed a commit that referenced this pull request Jun 13, 2024
Description
Fix the order of configuration steps to ensure that DVCR credentials are configured before merging containerd configurations.

Why do we need it, and what problem does it solve?
We currently have a bashible step 032_configure_containerd.sh with a weight of 32. This step merges the containerd configurations, which requires correct DVCR (Docker V2 Container Registry) credentials. To solve the problem where DVCR credentials must be configured in advance, this PR introduces a lower weight configuration step that runs before the containerd configuration step.

Signed-off-by: yaroslavborbat <[email protected]>
(cherry picked from commit 6cc4d26)
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