fix gateway yaml format and missing label (#455)

* fix gateway api label

Signed-off-by: Jooho Lee <[email protected]>

* fix format of yaml

Signed-off-by: Jooho Lee <[email protected]>

---------

Signed-off-by: Jooho Lee <[email protected]>

Author: Jooho

docs/admin/gatewayapi_migration.md

@@ -129,7 +129,7 @@ kubectl rollout restart deployment kserve-controller-manager -n kserve
 If you are using a cloud provider, you may need to configure the external traffic to the LoadBalancer service created in [step 4](#4-create-gateway-resource).
 
 ```shell
-kubectl get svc kserve-ingress-gateway -l  -A
+kubectl get svc -l serving.kserve.io/gateway=kserve-ingress-gateway -A
 ```
 
 ## 8. Verify the Gateway API configuration

docs/admin/kubernetes_deployment.md

@@ -55,9 +55,9 @@ The minimally required Cert Manager version is 1.15.0 and you can refer to [Cert
         - name: http
           protocol: HTTP
           port: 80
-            allowedRoutes:
-              namespaces:
-                from: All
+          allowedRoutes:
+            namespaces:
+              from: All
         - name: https
           protocol: HTTPS
           port: 443
@@ -70,9 +70,9 @@ The minimally required Cert Manager version is 1.15.0 and you can refer to [Cert
           allowedRoutes:
             namespaces:
               from: All
-        infrastructure:
-        labels:
-          serving.kserve.io/gateway: kserve-ingress-gateway
+      infrastructure:
+      labels:
+        serving.kserve.io/gateway: kserve-ingress-gateway
     ```
     !!! note
         KServe comes with a default `Gateway` named kserve-ingress-gateway. You can enable the default gateway by setting Helm value `kserve.controller.gateway.ingressGateway.createGateway` to `true`.