Sync documentation of main branch

Author: actions-user

_generated-doc/main/infra/quarkus-all-build-items.adoc

@@ -4731,6 +4731,29 @@ _No Javadoc found_
 
 
 
+a| https://github.com/quarkusio/quarkus/blob/main/extensions/kubernetes/spi/src/main/java/io/quarkus/kubernetes/spi/KubernetesClusterRoleBindingBuildItem.java[`io.quarkus.kubernetes.spi.KubernetesClusterRoleBindingBuildItem`, window="_blank"]
+[.description]
+--
+Produce this build item to request the Kubernetes extension to generate a Kubernetes `ClusterRoleBinding` resource. The configuration here is limited; in particular, you can't specify subjects of the role binding. The role will always be bound to the application's service account.
+-- a|`java.lang.String name` 
+
+Name of the generated `RoleBinding` resource. Can be `null` , in which case the resource name is autogenerated.
+
+`io.quarkus.kubernetes.spi.RoleRef roleRef` 
+
+RoleRef configuration.
+
+`io.quarkus.kubernetes.spi.Subject[] subjects` 
+
+The target subjects.
+
+`java.util.Map<String,String> labels` 
+
+The labels of the cluster role resource.
+
+
+
+
 a| https://github.com/quarkusio/quarkus/blob/main/extensions/kubernetes/spi/src/main/java/io/quarkus/kubernetes/spi/KubernetesClusterRoleBuildItem.java[`io.quarkus.kubernetes.spi.KubernetesClusterRoleBuildItem`, window="_blank"]
 [.description]
 --
@@ -5099,7 +5122,7 @@ a| https://github.com/quarkusio/quarkus/blob/main/extensions/kubernetes/spi/src/
 [.description]
 --
 Produce this build item to request the Kubernetes extension to generate a Kubernetes `RoleBinding` resource. 
-Note that this can't be used to generate a `ClusterRoleBinding` .
+Use `KubernetesClusterRoleBindingBuildItem` to generate a `ClusterRoleBinding` .
 -- a|`java.lang.String name` 
 
 Name of the generated `RoleBinding` resource. Can be `null` , in which case the resource name is autogenerated.

_versions/main/guides/extension-writing-dev-service.adoc

@@ -23,11 +23,11 @@ include::_attributes.adoc[]
 If your extension provides APIs for connecting to an external service, it's a good idea to provide a xref:dev-services.adoc[Dev Service] implementation.
 
 To create a Dev Service, add a new build step into the extension processor class that returns a `DevServicesResultBuildItem`.
-Here, the link:https://hub.docker.com/_/hello-world`hello-world` image is used, but you should set up the right image for your service.
+Here, the https://hub.docker.com/_/hello-world[`hello-world`] image is used, but you should set up the right image for your service.
 
 [source%nowrap,java]
 ----
-    @BuildStep(onlyIfNot = IsNormal.class, onlyIf = GlobalDevServicesConfig.Enabled.class) {
+    @BuildStep(onlyIfNot = IsNormal.class, onlyIf = GlobalDevServicesConfig.Enabled.class)
     public DevServicesResultBuildItem createContainer() {
         DockerImageName dockerImageName = DockerImageName.parse("hello-world");
         GenericContainer container = new GenericContainer<>(dockerImageName)
@@ -89,7 +89,7 @@ For example,
 
 [source%nowrap,java]
 ----
-    @BuildStep(onlyIfNot = IsNormal.class, onlyIf = GlobalDevServicesConfig.Enabled.class) {
+    @BuildStep(onlyIfNot = IsNormal.class, onlyIf = GlobalDevServicesConfig.Enabled.class)
     public DevServicesResultBuildItem createContainer(MyConfig config) {
 ----