Updated ROADMAP for the next (0.11) release

[frisso]

No description provided.

[adamjensenbot]

Hi @frisso. Thanks for your PR!

I am @adamjensenbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests
  when the rebase operation is completed)
• /merge: Merge this PR into the master branch
• /build Build Liqo components
• /test Launch the E2E and Unit tests
• /hold, /unhold Add/remove the hold label to prevent merging with /merge

Make sure this PR appears in the liqo changelog, adding one of the following labels:

• kind/breaking: 💥 Breaking Change
• kind/feature: 🚀 New Feature
• kind/bug: 🐛 Bug Fix
• kind/cleanup: 🧹 Code Refactoring
• kind/docs: 📝 Documentation

[Sharathmk99]

Can we include #1831 #1846 #1768 please?

[aleoli]

Hi @Sharathmk99, this roadmap is for the next release that will be ready soon. We will include these features in future releases.

The VirtualNode feature is 90% available in the current Liqo version; we need to refactor the authentication workflow to complete it; we will include it in the roadmap for the subsequent releases.

We cannot define a general model for the upgrading process yet, but we will probably provide a manual step-by-step guide for this release.

While for the "graceful" unpeer, we need to think a little about it to identify the best solution for integrating it.

[cheina97]

/rebase test=true

[cheina97]

/rebase test=true

[Sharathmk99]

Hi @Sharathmk99, this roadmap is for the next release that will be ready soon. We will include these features in future releases.

The VirtualNode feature is 90% available in the current Liqo version; we need to refactor the authentication workflow to complete it; we will include it in the roadmap for the subsequent releases.

We cannot define a general model for the upgrading process yet, but we will probably provide a manual step-by-step guide for this release.

While for the "graceful" unpeer, we need to think a little about it to identify the best solution for integrating it.

Thank you so much for the reply. It will be really nice if we can add more virtual node using the same foreign cluster, which help to offload cpu nodes and GPU nodes in a separate virtual node.