Skip to content

Conversation

@mansurianas
Copy link

@mansurianas mansurianas commented Jul 2, 2025

Description

This PR adds a detailed introduction to Kubernetes as part of the documentation initiative. It includes:

  • Why Kubernetes was created

  • Difference between Docker and Kubernetes

  • YAML basics for Kubernetes resources

  • A fully commented example YAML for Pod

  • Suggested learning resources (Killercoda, YouTube, Official docs)

Type of Change

📝 Documentation update

Changes Made

  • Created introduction.mdx under content/docs/Kubernetes/kubernets-docs/

  • Wrote and formatted Kubernetes overview + YAML basics

  • Added meta.json with sidebar positions

  • Removed outdated InterviewQuestions/ directory and index.md

Summary by CodeRabbit

  • New Features

    • Added a comprehensive introductory document covering Kubernetes fundamentals, challenges, advantages, disadvantages, YAML usage, and recommended learning resources.
  • Documentation

    • Updated the structure of Kubernetes interview questions metadata to support ordered sections.
    • Removed outdated or redundant documentation files related to Kubernetes and interview questions.

@vercel
Copy link

vercel bot commented Jul 2, 2025

@mansurianas is attempting to deploy a commit to the devsuraj Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link

coderabbitai bot commented Jul 2, 2025

Walkthrough

This update restructures the Kubernetes documentation by deleting two metadata-only files, revising the interview questions metadata to a structured array with ordering, and introducing a comprehensive introductory document on Kubernetes fundamentals, configuration, and learning resources.

Changes

File(s) Change Summary
content/docs/Kubernetes/InterviewQuestions/index.mdx, content/docs/Kubernetes/index.md Deleted files containing only metadata (title/description).
content/docs/Kubernetes/InterviewQuestions/meta.json Changed from a single metadata object to an array of titled/positioned objects for section ordering.
content/docs/Kubernetes/InterviewQuestions/introduction.mdx Added a new, detailed introduction to Kubernetes, covering concepts, YAML basics, and learning links.

Poem

In burrows deep, I hop and write,
Kubernetes docs now trimmed so light.
Metadata shuffled, a fresh intro appears,
YAML and clusters, no need for fears!
With every change, my whiskers twitch,
Learning made easy—code rabbits enrich! 🐇✨


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (2)
content/docs/Kubernetes/kubernets-docs/introduction.mdx (2)

75-75: Fix heading grammar

Interrogative headings in English need the auxiliary verb before the subject:

-## Why YAML is Used in Kubernetes?
+## Why Is YAML Used in Kubernetes?

37-46: Emojis inside tables hurt accessibility & fallback rendering

Screen-readers will announce “emoji heavy check mark” etc., and some Markdown renderers drop coloured glyphs inside tables.
Consider replacing with plain “Yes / Partial / No” or ✅/❌ via text.

Example:

-| Networking between containers        | 🟡 Limited | ✅         |
+| Networking between containers        | Limited*   | Yes        |

Add a footnote if you need to explain “Limited”.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c9a75f1 and 00e94a2.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (5)
  • content/docs/Kubernetes/InterviewQuestions/index.mdx (0 hunks)
  • content/docs/Kubernetes/InterviewQuestions/meta.json (0 hunks)
  • content/docs/Kubernetes/index.md (0 hunks)
  • content/docs/Kubernetes/kubernets-docs/introduction.mdx (1 hunks)
  • content/docs/Kubernetes/kubernets-docs/meta.json (1 hunks)
💤 Files with no reviewable changes (3)
  • content/docs/Kubernetes/InterviewQuestions/index.mdx
  • content/docs/Kubernetes/index.md
  • content/docs/Kubernetes/InterviewQuestions/meta.json
🧰 Additional context used
🪛 LanguageTool
content/docs/Kubernetes/kubernets-docs/introduction.mdx

[uncategorized] ~22-~22: The verb “was” doesn’t seem to fit in this context, “were” is probably more formally correct.
Context: ...ing - Scaling containers across servers was complex - Rolling updates required manu...

(AI_HYDRA_LEO_CPT_WAS_WERE)


[style] ~24-~24: To elevate your writing, try using a synonym here.
Context: ...rvice discovery and load balancing were hard to manage Kubernetes solves these by: ...

(HARD_TO)


[uncategorized] ~24-~24: A period might be missing here.
Context: ...scovery and load balancing were hard to manage Kubernetes solves these by: - Automat...

(AI_EN_LECTOR_MISSING_PUNCTUATION_PERIOD)


[uncategorized] ~35-~35: Possible missing article found.
Context: ...Kubernetes builds on Docker by managing container lifecycle at scale. | Feature ...

(AI_HYDRA_LEO_MISSING_THE)


[uncategorized] ~54-~54: A determiner appears to be missing. Consider inserting it.
Context: ...ntages of Kubernetes - Complexity: Learning curve is steep, especially for beginner...

(AI_EN_LECTOR_MISSING_DETERMINER)


[grammar] ~75-~75: If this is a question, the word order is probably incorrect. Did you mean “Why is YAML”… ?
Context: ...then tries to make that state real. ## Why YAML is Used in Kubernetes? - ✅ **Human-readab...

(WHY_THE_WORD_ORDER_IS_WRONG)

Comment on lines 1 to 12
[

{
"title": "introduction",
"position": 1

},
{
"title": "architecture",
"position": 2
}
] No newline at end of file
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Directory name is misspelled – will break generated routes & links

The file sits under kubernets-docs/, missing an “e”. All sidebar paths, MDX import links and any slug generation that relies on the physical directory name will silently break.

-content/docs/Kubernetes/kubernets-docs/
+content/docs/Kubernetes/kubernetes-docs/

Rename the folder (and update any references) before this lands on main.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In content/docs/Kubernetes/kubernets-docs/meta.json lines 1 to 12, the directory
name "kubernets-docs" is misspelled and should be corrected to
"kubernetes-docs". Rename the folder to fix the typo and update all references
to this directory in sidebar paths, MDX import links, and any slug generation
logic to prevent broken routes and links.


## Conclusion

Docker sirf ek chhota part hai (container runtime). Kubernetes us container ko manage karta hai — production-ready orchestration system.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Avoid mixing Hindi with English – keep docs language consistent

The sentence mixes Hindi (“sirf ek chhota part hai …”) with English, which can confuse readers and breaks the style of the rest of the docs.

-Docker sirf ek chhota part hai (container runtime). Kubernetes us container ko manage karta hai — production-ready orchestration system.
+Docker is only one piece of the puzzle (the container runtime).  
+Kubernetes manages those containers, providing a production-ready orchestration platform.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Docker sirf ek chhota part hai (container runtime). Kubernetes us container ko manage karta hai — production-ready orchestration system.
Docker is only one piece of the puzzle (the container runtime).
Kubernetes manages those containers, providing a production-ready orchestration platform.
🤖 Prompt for AI Agents
In content/docs/Kubernetes/kubernets-docs/introduction.mdx at line 50, the
sentence mixes Hindi and English, which disrupts the document's language
consistency. Rewrite the sentence entirely in English to maintain a consistent
language style throughout the documentation.

@Suraj-kumar00 Suraj-kumar00 self-requested a review July 3, 2025 16:43
@Suraj-kumar00
Copy link
Owner

Suraj-kumar00 commented Jul 3, 2025

Hi @mansurianas thanks for raising PR.
Can you please share the sreenshot of the website after you make the changes so that i can see how it looks for merging.

and also add the proper chennel links etc.. of these as well:
Prerit Munjal
Kubesimplify
TrainWithShubham
Abhishek.Veeramalla

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (5)
content/docs/Kubernetes/InterviewQuestions/meta.json (1)

4-6: Capitalize titles for consistency

"introduction" / "architecture" differ from previously Title-cased "Interview Questions". Switch to "Introduction" / "Architecture" to keep headings uniform.

-  "title": "introduction",
+  "title": "Introduction",
...
-  "title": "architecture",
+  "title": "Architecture",
content/docs/Kubernetes/InterviewQuestions/introduction.mdx (4)

50-51: Avoid mixed-language sentence

The Hindi phrase may confuse non-Hindi readers. Replace with an English equivalent or provide translation.

- Docker sirf ek chhota part hai (container runtime). Kubernetes us container ko manage karta hai — production-ready orchestration system.
+ Docker is only a small part of the story (it’s the container runtime). Kubernetes manages those containers — it is the production-ready orchestration system.

75-77: Correct the heading grammar

Interrogative headings should invert subject/verb order.

-## Why YAML is Used in Kubernetes?
+## Why Is YAML Used in Kubernetes?

85-91: Small wording fixes & punctuation

Minor style/grammar adjustments for clarity.

- - **Indentation:** Always use spaces, not tabs. Usually 2 spaces.
+ - **Indentation:** Always use spaces, not tabs — commonly 2 spaces.
- - **Key-value pairs:** Use key: value format
+ - **Key–value pairs:** Use `key: value` format.
- - **Start of a YAML doc:** Use --- (3 dashes) to indicate start of YAML file
+ - **Document start:** Use `---` (three dashes) to mark the beginning of a YAML file.

117-129: Add clickable links for all referenced platforms

Only Killercoda is linked; KodeKloud isn’t. Add its URL to maintain parity.

-Platforms like **Killercoda** and **KodeKloud** offer interactive Kubernetes labs.
+Platforms like **[Killercoda](https://killercoda.com/)** and **[KodeKloud](https://kodekloud.com/)** offer interactive Kubernetes labs.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 00e94a2 and 25c35c0.

📒 Files selected for processing (2)
  • content/docs/Kubernetes/InterviewQuestions/introduction.mdx (1 hunks)
  • content/docs/Kubernetes/InterviewQuestions/meta.json (1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/docs/Kubernetes/InterviewQuestions/introduction.mdx

[uncategorized] ~22-~22: The verb “was” doesn’t seem to fit in this context, “were” is probably more formally correct.
Context: ...ing - Scaling containers across servers was complex - Rolling updates required manu...

(AI_HYDRA_LEO_CPT_WAS_WERE)


[style] ~24-~24: To elevate your writing, try using a synonym here.
Context: ...rvice discovery and load balancing were hard to manage Kubernetes solves these by: ...

(HARD_TO)


[uncategorized] ~24-~24: A period might be missing here.
Context: ...scovery and load balancing were hard to manage Kubernetes solves these by: - Automat...

(AI_EN_LECTOR_MISSING_PUNCTUATION_PERIOD)


[uncategorized] ~35-~35: Possible missing article found.
Context: ...Kubernetes builds on Docker by managing container lifecycle at scale. | Feature ...

(AI_HYDRA_LEO_MISSING_THE)


[uncategorized] ~54-~54: A determiner appears to be missing. Consider inserting it.
Context: ...ntages of Kubernetes - Complexity: Learning curve is steep, especially for beginner...

(AI_EN_LECTOR_MISSING_DETERMINER)


[grammar] ~75-~75: If this is a question, the word order is probably incorrect. Did you mean “Why is YAML”… ?
Context: ...then tries to make that state real. ## Why YAML is Used in Kubernetes? - ✅ **Human-readab...

(WHY_THE_WORD_ORDER_IS_WRONG)

🔇 Additional comments (1)
content/docs/Kubernetes/InterviewQuestions/meta.json (1)

1-12: Confirm array format in Kubernetes InterviewQuestions meta.json

Verified that content/docs/Kubernetes/InterviewQuestions/meta.json uses a top-level JSON array, while every other meta.json (including other InterviewQuestions directories) starts with an object ({). If the sidebar builder or custom script expects the single-object shape, this change could break ordering or visibility. Please confirm that Docusaurus (or your sidebar generator) supports a root array in meta.json, or adjust this file back to the object format.

@mansurianas
Copy link
Author

Hi @Suraj-kumar00

I've made the requested changes:

Restored the deleted folders (InterviewQuestions, etc.)

Followed your folder-based structure and notes format

Added YouTube links and updated content accordingly

Attached below is the screenshot of the updated website view after the changes

Screenshot 2025-07-03 233902
Screenshot 2025-07-03 233931

@Suraj-kumar00
Copy link
Owner

Hi Anas, as we discussed and I have explained that you don't have to delete any file that is initially present okay so you deleted the.
Screenshot 2025-07-05 at 12 26 53 AM

the text you're seeing introduction to kubernetes it should in the index.mdx under the kuberentes folder. See the structure i have here.

For the introduction part you have to add all the infromation under

kubernetes
 - index.mdx 

okay

And as I have made the folder for the interview preparation and have two files these files:

Interview preparation
- index.mdx 
- meta.json

Like this you have to make for every topics of kuberentes like k8s resources pods, deployments, services etc...

Do you now understand this?

please clone it again and make the changes because you don't need to delete anything that exists initially.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants