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

Deprecate userdata #1544

Closed
3 tasks done
ahmedwaleedmalik opened this issue Jan 30, 2023 · 1 comment · Fixed by #1642
Closed
3 tasks done

Deprecate userdata #1544

ahmedwaleedmalik opened this issue Jan 30, 2023 · 1 comment · Fixed by #1642
Labels
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@ahmedwaleedmalik
Copy link
Member

ahmedwaleedmalik commented Jan 30, 2023

  • Add a note in README.md that MC userdata is deprecated and OSM should be used instead.
  • Documentation for using OSM in a combination with MC for local development
  • Adjusts scripts, if/when required, to deploy OSM alongside MC
@ahmedwaleedmalik ahmedwaleedmalik added the kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. label Jan 30, 2023
@kubermatic-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants