Merge branch 'master' into master

Phantom-Intruder · web-flow · commit e6f3aafaee57 · 2025-04-17T16:57:12.000+05:30
diff --git a/Autoscaler101/autoscaler-lab.md b/Autoscaler101/autoscaler-lab.md
@@ -178,4 +178,4 @@ You should be able to see the memory limit getting reached, after which the numb
 
 ## Conclusion
 
-That sums up the lab on autoscalers. In here, we discussed the two most commonly used in-built autoscalers: HPA and VPA. We also took a hands-on look at how the autoscalers worked. This is just the tip of the iceberg when it comes to scaling, however, and the subject of custom scalers that can scale based on metrics other than memory and CPU is vast. If you are interested in looking at more complicated scaling techniques, you could take a look at the [KEDA section](../Keda101/what-is-keda.md) to get some idea of the keda autoscaler.
+That sums up the lab on autoscalers. In here, we discussed the two most commonly used in-built autoscalers: HPA and VPA. We also took a hands-on look at how the autoscalers worked. This is just the tip of the iceberg when it comes to scaling, however, and the subject of custom scalers that can scale based on metrics other than memory and CPU is vast. If you are interested in looking at more complicated scaling techniques, you could take a look at the [KEDA section](../Keda101/what-is-keda.md) to get some idea of the keda autoscaler.
diff --git a/Gemfile.lock b/Gemfile.lock
@@ -8,7 +8,7 @@ PATH
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.1.3)
+    activesupport (7.1.3.4)
       base64
       bigdecimal
       concurrent-ruby (~> 1.0, >= 1.0.2)
@@ -22,7 +22,7 @@ GEM
       public_suffix (>= 2.0.2, < 6.0)
     ast (2.4.2)
     base64 (0.2.0)
-    bigdecimal (3.1.6)
+    bigdecimal (3.1.8)
     coffee-script (2.4.1)
       coffee-script-source
       execjs
@@ -31,20 +31,20 @@ GEM
     commonmarker (0.23.10)
     concurrent-ruby (1.2.2)
     connection_pool (2.4.1)
-    dnsruby (1.70.0)
+    dnsruby (1.72.2)
       simpleidn (~> 0.2.1)
-    drb (2.2.0)
-      ruby2_keywords
+    drb (2.2.1)
     em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0)
     ethon (0.16.0)
       ffi (>= 1.15.0)
     eventmachine (1.2.7)
     execjs (2.9.1)
-    faraday (2.9.0)
+    faraday (2.10.1)
       faraday-net_http (>= 2.0, < 3.2)
-    faraday-net_http (3.1.0)
+      logger
+    faraday-net_http (3.1.1)
       net-http
     ffi (1.15.5)
     forwardable-extended (2.6.0)
@@ -228,16 +228,17 @@ GEM
     listen (3.8.0)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
+    logger (1.6.0)
     mercenary (0.3.6)
     minima (2.5.1)
       jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    minitest (5.22.0)
+    minitest (5.25.1)
     mutex_m (0.2.0)
     net-http (0.4.1)
       uri
-    nokogiri (1.16.2-x86_64-linux)
+    nokogiri (1.16.5-x86_64-linux)
       racc (~> 1.4)
     octokit (4.25.1)
       faraday (>= 1, < 3)
@@ -254,7 +255,8 @@ GEM
     rb-inotify (0.10.1)
       ffi (~> 1.0)
     regexp_parser (2.8.0)
-    rexml (3.2.5)
+    rexml (3.3.6)
+      strscan
     rouge (3.26.0)
     rubocop (0.93.1)
       parallel (~> 1.10)
@@ -268,7 +270,6 @@ GEM
     rubocop-ast (1.28.1)
       parser (>= 3.2.1.0)
     ruby-progressbar (1.13.0)
-    ruby2_keywords (0.0.5)
     rubyzip (2.3.2)
     safe_yaml (1.0.5)
     sass (3.7.4)
@@ -279,17 +280,14 @@ GEM
     sawyer (0.9.2)
       addressable (>= 2.3.5)
       faraday (>= 0.17.3, < 3)
-    simpleidn (0.2.1)
-      unf (~> 0.1.4)
+    simpleidn (0.2.3)
+    strscan (3.1.0)
     terminal-table (1.8.0)
       unicode-display_width (~> 1.1, >= 1.1.1)
     typhoeus (1.4.0)
       ethon (>= 0.9.0)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
-    unf (0.1.4)
-      unf_ext
-    unf_ext (0.0.9.1)
     unicode-display_width (1.8.0)
     uri (0.13.0)
     w3c_validators (1.3.7)
@@ -317,4 +315,4 @@ DEPENDENCIES
   webrick
 
 BUNDLED WITH
-   2.4.12
+   2.4.12
diff --git a/Keda101/keda-lab.md b/Keda101/keda-lab.md
@@ -252,4 +252,5 @@ With the above configuration, a new Keda job will start every time a message is
 ## Conclusion
 This wraps up the lesson on KEDA. What we tried out was a simple demonstration of a MySQL scaler followed by a demonstration of using various authentication methods to connect and consume messages from AWS SQS. This is a good representation of what you can expect from other data sources. If you were considering using this with a different Kubernetes engine running on a different cloud provider, the concept would still work. Make sure you read through the authentication page, which contains different methods of authentication for different cloud providers. Next up, we will look at how you can use KEDA alongside Prometheus and Linkerd to scale your pods based on the number of requests reaching your endpoints.
 
+
 [Next: Scaling with KEDA and Prometheus](./keda-prometheus.md)
diff --git a/README.md b/README.md
@@ -46,7 +46,6 @@ A Curated List of Kubernetes Labs and Tutorials
 ### PWK:
 
   - [Preparing 5-Node Kubernetes Cluster](./kube101.md) 
-  - [Setting up WeaveScope For Visualization on Kubernetes](./weave-pwk.md) 
   - [Running Portainer on 5 Node Kubernetes Cluster](https://github.com/collabnix/kubelabs/tree/master/portainer#running-portainer-on-5-node-kubernetes-cluster)
   
   
@@ -405,7 +404,7 @@ Add the following entry for local access
 url: http://127.0.0.1:4000
 ```
 
-## Step 2. Run the container
+## Step 3. Run the container
 
 
 ```
diff --git a/kube101.md b/kube101.md
@@ -1,5 +1,8 @@
 ## Preparing 5-Node Kubernetes Cluster
 
+> Updated: 26-Jan-2025
+> We recommend you to either use Minikube or Docker Desktop locally to test a single node Kubernetes cluster instead of Play with Kubernetes. PWK is currently unstable and you might face resource insufficient issue. If you're looking out for multiple node, then use VM or bare metal or Cloud > instances. 
+
 To get started with Kubernetes, follow the below steps:
 
 -  Open <a href="https://labs.play-with-k8s.com/" target="_blank">https://labs.play-with-k8s.com/</a> on your browser
diff --git a/portainer/README.md b/portainer/README.md
@@ -1,12 +1,15 @@
 # Running Portainer on 5-Node Kubernetes Cluster
 
+## What is Portainer?
 
-## Pre-requisite:
+![logo](https://www.portainer.io/hubfs/portainer-logo-black.svg)
+Portainer is a one-stop shop for managing your containerized environments, providing a massive amount of functionality in both our Community and Business Editions. We often hear from our users, “Wow, I didn’t know Portainer could do that!” So here’s a list of what you can do with Portainer.
+
+## Pre-requisites:
 
 - Play with Kubernetes Platform
 - Set up 5 Node Kubernetes Cluster
 
-
 ## Run the below command:
 
 ```

Original file line number	Diff line number	Diff line change
`@@ -178,4 +178,4 @@ You should be able to see the memory limit getting reached, after which the numb`
`178`	`178`
`179`	`179`	`## Conclusion`
`180`	`180`
`181`		-That sums up the lab on autoscalers. In here, we discussed the two most commonly used in-built autoscalers: HPA and VPA. We also took a hands-on look at how the autoscalers worked. This is just the tip of the iceberg when it comes to scaling, however, and the subject of custom scalers that can scale based on metrics other than memory and CPU is vast. If you are interested in looking at more complicated scaling techniques, you could take a look at the [KEDA section](../Keda101/what-is-keda.md) to get some idea of the keda autoscaler.
	`181`	+That sums up the lab on autoscalers. In here, we discussed the two most commonly used in-built autoscalers: HPA and VPA. We also took a hands-on look at how the autoscalers worked. This is just the tip of the iceberg when it comes to scaling, however, and the subject of custom scalers that can scale based on metrics other than memory and CPU is vast. If you are interested in looking at more complicated scaling techniques, you could take a look at the [KEDA section](../Keda101/what-is-keda.md) to get some idea of the keda autoscaler.