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

[WIP] Update sandbox for latest changes #129

Closed
wants to merge 4 commits into from

Conversation

detiber
Copy link
Contributor

@detiber detiber commented Apr 6, 2022

Description

Update sandbox for latest Tinkerbell chagnes

Why is this needed

The last sandbox release is getting quite a bit old at v0.6.0, with all the changes that have landed since then, it's about time for a v0.7.0 release

How Has This Been Tested?

TODO

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

TODO

Checklist:

I have:

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

Blockers:

@detiber detiber self-assigned this Apr 6, 2022
@mmlb
Copy link
Contributor

mmlb commented Apr 7, 2022

I'd like to see the next release be w/o tls which is still in progress in tink. I think it makes sense to wait until then instead of release 0.7 and come up with 0.8 soon after (hopefully). What do you think @detiber?

@displague
Copy link
Member

Getting the dependencies tagged first sounds like the right order to me. Sandbox is then built on well-known, fixed, dependencies.

@chrisdoherty4
Copy link
Member

chrisdoherty4 commented Oct 29, 2022

0.7 has been released with lots of updates. This PR can be closed.

@chrisdoherty4
Copy link
Member

This is outdated and will likely change as we continue moving to Kube backend only.

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.

4 participants