krallistic / krallistic/tensorflow-operator
Automatic Creation of CRD
Open
Nobody has claimed this yet.
enhancement
good first issue
help wanted
- Dominant language
- Python
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Currently CRD has to manually created, this should be done at startup for the operator
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the operator's startup entry point and the existing CRD definition or creation path. Trace how the operator currently initializes in Kubernetes, then verify that a fresh startup creates the required CRD without manual setup. Done means the operator can start successfully when the CRD is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100