diff --git a/Kubernetes-deployment.md b/Kubernetes-deployment.md
index be9919a..f6f72ad 100644
--- a/Kubernetes-deployment.md
+++ b/Kubernetes-deployment.md
@@ -61,6 +61,8 @@ MetalLB hooks into your Kubernetes cluster, and provides a network load-balancer
 kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.4/config/manifests/metallb-native.yaml
 ```
 
+Or you can simply use [helm](https://artifacthub.io/packages/helm/metallb/metallb) 
+
 ### MetalLB IP pool 
 Create a new yaml file with the following content and be sure to customize your ip range:
 ```
@@ -102,6 +104,7 @@ CM allows us to issue and maintain SSL certificates in our cluster
 ```
 kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.4/cert-manager.yaml
 ```
+Or you can simply use [helm](https://artifacthub.io/packages/helm/cert-manager/cert-manager) 
 
 By default it will issue fake, self signed certificates , but if your cluster is available directly form the internet you can issue let'sencrypt certs
 so we need to create a file
@@ -167,6 +170,9 @@ kubectl apply -f deployments/daemon-set/nginx-ingress.yaml
 kubectl apply -f deployments/service/loadbalancer.yaml
 ```
 
+Or you can simply use [helm](https://artifacthub.io/packages/helm/ingress-nginx/ingress-nginx) 
+
+
 you can check what ip address the service is exposed on with:
 
 ```
@@ -197,6 +203,9 @@ before installing Longhorn itself
 kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/v1.6.1/deploy/longhorn.yaml
 ```
 
+Or you can simply use [helm](https://artifacthub.io/packages/helm/longhorn/longhorn) 
+
+
 To make longhorn UI available trough ingress, create a file:
 
 ```