link to a page listing the extensions related to kubernetes providers

[feloy]

In the internal implementation of the Kubernetes dashboard, when the does not have any defined connection (no ~/.kube/config file), a specific page is displayed.

In this page, a list of extensions related to Kubernetes providers are displayed, and actions on these extensions are possible (install, etc).

It won't be possible to have the same functionality from an extension, as Podman Desktop does not provide access to the catalog of extensions.

Another solution would be to have a link redirecting tp a page internal to Podman Desktop.

Needs:

• provide a page with specific extensions podman-desktop#14181

[MariaLeonova]

Some comments from the UX call today:

• we need to explore all the use cases for the empty screen: i.e. user has no extensions installed; user has no cluster at all and would like to create one; they want to bring their own cluster, they have a cluster, but also would like to try other extensions.
• we discussed linking to a filtered list of applicable extensions (k8s providers), which could be a search results or a separate tab
• we also mentioned possibly having a mini view / widget to display extensions
• our goal is to drive more towards usage for k8s features

[odockal]

Once the design is decided, we could add some simple e2e tests for empty page vs. one with context present. Ping me pls once you have some decision.

[feloy]

Once the design is decided, we could add some simple e2e tests for empty page vs. one with context present. Ping me pls once you have some decision.

If the e2e test wants to test the logic of displaying the empty page or not, this part is already implemented (PRs #317 and #342).

For the moment, the empty page only displays the static text, but I suppose you could assert its presence by adding some aria label there

[MariaLeonova]

Linking to extensions

Shall we consider adding a similar card for adding a new provider, that would link to extensions?

I think it would be more beneficial for users than just having a link under the Kind cluster card, which is, of course, another option. Adding for comparison:

In the second option (link) users are very likely to ignore the text underneath the card, which contradicts our goal to drive adoption of k8s extensions.

Button behaviour

The button / link See available extensions will lead to the extensions search page filtered by the relevant parameters (category:kubernetes, etc) - see this link.

UI enhancements

I also made some minor changes to the cards themselves:

• button text changed to Create new cluster.
• link replaced with Learn more ↗️ . That is the UI we use on the main Dashboard and in AI Lab recipes.
• Kind card highlighted as default.

[feloy]

Linking to extensions

Shall we consider adding a similar card for adding a new provider, that would link to extensions?

I think it would be more beneficial for users than just **having a link** under the `Kind cluster` card, which is, of course, another option. Adding for comparison:

In the second option (link) users are very likely to ignore the text underneath the card, which contradicts our goal to drive adoption of k8s extensions.

Yes, that seems a great idea to me.

[feloy]

UI enhancements

I also made some minor changes to the cards themselves:

• button text changed to Create new cluster.

OK, note that providers have the possibility to provide their own label for the button, and the extension provides a default label.

• link replaced with Learn more ↗️ . That is the UI we use on the main Dashboard and in AI Lab recipes.
• Kind card highlighted as default.

[MariaLeonova]

OK, note that providers have the possibility to provide their own label for the button, and the extension provides a default label.

Noted!
Where it says Create new now, t would be great to add the word Cluster.