Add a new BuildItem class: KubernetesDevServiceRequestBuildItem

[cmoulliard]

• Review the kubernetes dev service documentation (adoc file)to improve it,
• Add a new class KubernetesDevServiceRequestBuildItem and adapt the code to instantiate it part of the step creating the kind container
• Include the javadoc annotations for the newly created classes

[iocanel]

I think that the intention of KubernetesDevServiceRequestBuildItem has been misunderstood. The idea, is we create an alternative to configuration for controlling the DevService, so that other extension (e.g. quarkus-argocd or quarkus-tekton) can request the creation of the DevService.

So, I added some suggestions. But we still need more things: Consume the KubenretesDevServiceBuildItem and check if its present so that we can start the dev service.

[iocanel]

LGTM, let's squash and I'll merge once CI greenlights things.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 38882ec.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[github-actions]

🙈 The PR is closed and the preview is expired.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 38882ec.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.