-
Notifications
You must be signed in to change notification settings - Fork 835
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d987603
commit ec88fd4
Showing
1 changed file
with
19 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
## Task 32/40 | ||
|
||
In this exercise, you will explore Kubernetes Networking, container network interface(CNI), container runtime etc | ||
> [!NOTE] | ||
> If you do not already have a Kubernetes cluster, you can create a local Kubernetes cluster by following [Day06 Video](https://youtu.be/RORhczcOrWs) | ||
Also, could you do the port binding at the cluster level if you are using KIND? The Day9 video has the details on how to do that. | ||
|
||
### Task details | ||
1. Perform the steps as per the video demo. | ||
2. **Share your learnings**: Document your key takeaways and insights in a blog post and social media update | ||
3. **Make it public**: Share what you learn publicly on LinkedIn or Twitter. | ||
- **Tag us and use the hashtag**: Include the following in your post: | ||
- Tag [@PiyushSachdeva](https://www.linkedin.com/in/piyush-sachdeva) and [@CloudOps Community](https://www.linkedin.com/company/thecloudopscomm) (on both platforms) | ||
- Use the hashtag **#40daysofkubernetes** | ||
- **Embed the video**: Enhance your blog post by embedding the video lesson from the Kubernetes series. This will give you visual context and reinforce your written explanations. | ||
|
||
## Blog Post Focus 📝 | ||
|
||
- **Clarity is essential**: Write your blog post clearly and concisely, making it easy for anyone to grasp the concepts, regardless of their prior Kubernetes experience. |