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

Use a stable image for tink-server, tink-worker and tink-cli #146

Merged
merged 1 commit into from
Aug 2, 2022

Conversation

moadqassem
Copy link
Member

Description

The current image that is used in the main branch doesn't work due to the issue which is reported here: #143. There was a PR which addressed this issue already which can be found here tinkerbell/tink#632. This PR uses the latest tink-server, tink-worker and tink-cli which has the fix already in place.

Why is this needed

Fixes: #

How Has This Been Tested?

  • Checked out the main branch
  • Update the env var vTINK to sha-16186501
  • Run docker compose
  • Provision all the needed manifests(HW, WFL, TPL)
  • Reboot the machine

How are existing users impacted? What migration steps/scripts do we need?

I haven't updated any other components or image except the tink image.

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

Signed-off-by: Moath Qasim <moad.qassem@gmail.com>
@moadqassem moadqassem changed the title use a stable image for tink-server, tink-worker and tink-cli Use a stable image for tink-server, tink-worker and tink-cli Aug 1, 2022
Copy link
Member

@jacobweinstock jacobweinstock left a comment

Choose a reason for hiding this comment

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

Thanks @moadqassem !

@jacobweinstock jacobweinstock added the ready-to-merge Signal to Mergify to merge the PR. label Aug 2, 2022
@mergify mergify bot merged commit 1444ac3 into tinkerbell:main Aug 2, 2022
@moadqassem moadqassem deleted the use-a-stable-tink-release branch August 2, 2022 21:25
@moadqassem
Copy link
Member Author

Thanks @moadqassem !

Sure thing, btw, is there any kinda process for backporting things into previous releases?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge Signal to Mergify to merge the PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants