pingcap / pingcap/tiup

Add deploy cluster machine port range check

Open
#512 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status/TODO type/enhancement
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

Feature Request

after cluster deploy,if machine port over 0 - 65535 , cluster start will be falied, then report error
image
wish cluster deploy check port range , if port range over , report error ,Not cluster start report

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests; start at the cluster deploy entry point and trace how machine ports are handled before cluster start. Add deploy-time reporting for ports outside 0–65535, then verify that invalid ranges fail during deploy rather than during cluster start.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.