You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After research and dicussions on community meetings and TSC meetings, we have found that there are currently no scenarios for using viaduct repository independently. To better maintain this part, we have decided to migrate viaduct directly to https://github.com/kubeedge/kubeedge/tree/master/pkg.
1. Repository to archive:
https://github.com/kubeedge/viaduct
2. When should this be done?
September 20th.
3. Additional context for request.
After research and dicussions on community meetings and TSC meetings, we have found that there are currently no scenarios for using viaduct repository independently. To better maintain this part, we have decided to migrate viaduct directly to https://github.com/kubeedge/kubeedge/tree/master/pkg.
I have also submitted an issue kubeedge/kubeedge#5857 to track this migration.
The text was updated successfully, but these errors were encountered: