operator-framework / operator-framework/helm-operator-plugins
Status is incompatible with `metav1.Condition`
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 60
- Forks
- 53
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 5
Description
Currently, metav1.Condition requires Reason and Message fields to be set. This makes the reconciler impossible to use with resources using it, which is pretty standard.
type ResourceStatus struct {
Conditions []metav1.Condition `json:"conditions,omitempty"`
}
Using, results in errors like:
conditions[1].message: Required value, conditions[1].reason: Required value
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 reconciler and status handling that process resources with a conditions field typed as metav1.Condition. Reproduce the validation errors shown in the issue, then verify that resources using metav1.Condition no longer fail because Reason and Message are required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100