simplifying service creation in quickstart.md -> hrq

Signed-off-by: Zahar Pecherichny <[email protected]>

Author: zfrhv

docs/user-guide/quickstart.md

@@ -475,9 +475,12 @@ acme-org
 ```
 
 You can create a `HierarchicalResourceQuota` in namespace `acme-org`, and the sum of 
-all subnamespaces resource usage cant go over what is configured in the hrq.
+all subnamespaces resource usage can't go over what is configured in the HRQ.
 
-Creating the hrq:
+We will demonstrate how it works using services, but you could also limit `cpu`,
+`memory` or any other `ResourceQuota` field.
+
+Creating the HRQ:
 ```bash
 kubectl apply -f - << EOF
 kind: HierarchicalResourceQuota
@@ -493,38 +496,12 @@ EOF
 
 Lets create Service in namespace `team-a`:
 ```bash
-kubectl apply -f - << EOF
-kind: Service
-apiVersion: v1
-metadata:
-  name: team-a-svc
-  namespace: team-a
-spec:
-  selector:
-    place: holder
-  ports:
-  - protocol: TCP
-    port: 80
-    targetport: 80
-EOF
+kubectl create service clusterip team-a-svc --clusterip="None" -n team-a
 ```
 
 And when we try to create Service in namespace `team-b`:
 ```bash
-kubectl apply -f - << EOF
-kind: Service
-apiVersion: v1
-metadata:
-  name: team-b-svc
-  namespace: team-b
-spec:
-  selector:
-    place: holder
-  ports:
-  - protocol: TCP
-    port: 80
-    targetport: 80
-EOF
+kubectl create service clusterip team-b-svc --clusterip="None" -n team-b
 ```
 We get an error:
 ```
@@ -539,17 +516,18 @@ To view the HRQ usage, simply run:
 ```bash
 kubectl hns hrq -n acme-org
 ```
-you can also view in all namespace:
+You can also view in all namespace:
 ```bash
 kubectl hns hrq --all-namespaces
 ```
 
-and you can delete the hrq via simply deleting the CR:
+And you can delete the HRQ via simply deleting the CR:
 ```bash
 kubectl delete hrq acme-org-hrq -n acme-org
 ```
 
-Note: Decimal point values cannot be specified (you can't do `cpu: 1.5` but you can do `cpu: "1.5"` or `cpu: 1500m`). See [#292](https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/292)
+Note: Decimal point values cannot be specified (you can't do `cpu: 1.5` but
+you can do `cpu: "1.5"` or `cpu: 1500m`). See [#292](https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/292)
 
 <a name="subns"/>
 

test/e2e/quickstart_test.go

@@ -217,39 +217,13 @@ spec:
 		MustApplyYAML(hrq)
 
 		// create service in team-a
-		serviceA:=`
-kind: Service
-apiVersion: v1
-metadata:
-  name: `+nsTeamA+`-svc
-  namespace: `+nsTeamA+`
-spec:
-  selector:
-    place: holder
-  ports:
-  - protocol: TCP
-    port: 80
-    targetport: 80`
-		MustApplyYAML(serviceA)
+		MustRun("kubectl create service clusterip", nsTeamA + "-svc", `--clusterip="None"`, "-n", nsTeamA)
 
 		// show that you can't use resources more than the hrq
-		serviceB:=`
-kind: Service
-apiVersion: v1
-metadata:
-  name: `+nsTeamB+`-svc
-  namespace: `+nsTeamB+`
-spec:
-  selector:
-    place: holder
-  ports:
-  - protocol: TCP
-    port: 80
-    targetport: 80`
-		MustNotApplyYAML(serviceB)
+		MustNotRun("kubectl create service clusterip", nsTeamB + "-svc", `--clusterip="None"`, "-n", nsTeamB)
 
 		// show hrq usage
-		RunShouldContain("requests.cpu: 0/1, requests.memory: 0/2Gi   limits.cpu: 0/2, limits.memory: 0/4Gi, services 1/1", defTimeout, "kubectl hns hrq", "-n", nsOrg)
+		RunShouldContain("services 1/1", defTimeout, "kubectl hns hrq", "-n", nsOrg)
 
 		MustRun("kubectl delete hrq", nsOrg + "-hrq", "-n", nsOrg)
 	})