Fixed nodeport issue on result-service.yml and vote-service.yml

[DevMadhup]

Hi @LondheShubham153 sir,

As we are using port-forwarding on kind k8s cluster to access the application on browser, we don't require Nodeport type in service files, so I have removed it from result-service.yml and vote-service.yml.

Summary by CodeRabbit

• New Features

  • The result service now automatically assigns a node port, enhancing flexibility in port management.
  • The vote service has been updated to a default ClusterIP type, optimizing internal communication.

• Bug Fixes

  • Corrected YAML formatting for the result service, ensuring proper structure and readability.

[coderabbitai]

Walkthrough

The changes involve modifications to the Kubernetes service specifications for two applications: result and vote. The result service retains its NodePort type but removes the explicit nodePort assignment, allowing for automatic assignment. The vote service changes from NodePort to ClusterIP, with the nodePort field also removed. Both services maintain their existing port mappings and selectors.

Changes

Files	Change Summary
k8s-specifications/result-service.yaml	Removed explicit nodePort value; corrected indentation of name field under metadata.
k8s-specifications/vote-service.yaml	Changed service type from NodePort to ClusterIP; removed nodePort field.

Poem

In the land of code where services play,
Rabbit hops in, brightening the day.
Ports now assigned, no need to fret,
A tidy YAML, the best we've met!
With ClusterIP and NodePort so fine,
Our services dance in perfect line! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 17c12ea and d6c2031.

📒 Files selected for processing (2)

• k8s-specifications/result-service.yaml (0 hunks)
• k8s-specifications/vote-service.yaml (0 hunks)

💤 Files with no reviewable changes (2)

• k8s-specifications/result-service.yaml
• k8s-specifications/vote-service.yaml

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.