Skip to content

Commit 9e2fa10

Browse files
committed
correct code format
1 parent 87a85a1 commit 9e2fa10

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/blog/setting-up-ingress-on-eks.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ When we create a Service of type NodePort, Kubernetes gives us a nodePort value.
8282

8383
*The YAML for NodePort service looks like this:*
8484

85-
```shell
85+
```bash
8686
apiVersion: v1
8787
kind: Service
8888
metadata:
@@ -105,15 +105,15 @@ The `nodePort` parameter here is optional, added here just for an example. With
105105

106106
Create the service:
107107

108-
```shell
108+
```bash
109109
$ kubectl apply -f nginx-svc.yaml
110110
service/nginx-service created
111111

112112
```
113113

114114
Check it:
115115

116-
```shell
116+
```bash
117117
$ kubectl get svc nginx-service
118118
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
119119
nginx-service NodePort 172.20.54.138 <none> 80:30036/TCP 40s
@@ -400,7 +400,7 @@ The Ingress controller provisions an implementation-specific load balancer that
400400
Name-based virtual hosts support routing HTTP traffic to multiple host names at the same IP address.
401401

402402
<p align="center">
403-
<img width="500px" src="/images/blog/setting-up-ingress-on-eks/name-based-virtual-hosting.png" alt="Name based virtual hosting">
403+
<img width="700px" src="/images/blog/setting-up-ingress-on-eks/name-based-virtual-hosting.png" alt="Name based virtual hosting">
404404
</p>
405405

406406
image source: https://kubernetes.io/docs/concepts/services-networking/ingress/#name-based-virtual-hosting

0 commit comments

Comments
 (0)