[Feature][Project 1.2.0] add KubernestLauncher to start EngineConn
Open
enhancement
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/incubator-linkis/issues) and found no similar feature requirement.
### Problem Description
_No response_
### Description
_No response_
### Use case
_No response_
### solutions
_No response_
### Anything else
_No response_
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
Contributor guide
Research direction
The issue names a KubernestLauncher intended to start EngineConn, but provides no files, tests, use case, or acceptance criteria. First locate the existing EngineConn startup path and any launcher entry points, then clarify the expected Kubernetes behavior and define tests before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100