Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce spec.channel field to the operator API #169

Closed
Tracked by #163
awgreene opened this issue Apr 17, 2023 · 0 comments · Fixed by #171
Closed
Tracked by #163

Introduce spec.channel field to the operator API #169

awgreene opened this issue Apr 17, 2023 · 0 comments · Fixed by #171
Assignees

Comments

@awgreene
Copy link
Member

awgreene commented Apr 17, 2023

Goal:
The operator CustomResourceDefinition should be updated to include a spec.channel field.

Acceptance Criteria:

  • A spec.channel field is introduced to the Operator API.
  • The controller ignores the field, it does not influence resolution of the CR.
  • No tests are required.
@joelanford joelanford added this to the v0.1.0 (OLMv1 Milestone 3) milestone Apr 17, 2023
@tmshort tmshort self-assigned this Apr 17, 2023
tmshort added a commit to tmshort/operator-controller that referenced this issue Apr 17, 2023
Just add the Channel to the API
Fixes operator-framework#169
Fixes OPRUN-2916

Signed-off-by: Todd Short <tshort@redhat.com>
grokspawn pushed a commit that referenced this issue Apr 17, 2023
Just add the Channel to the API
Fixes #169
Fixes OPRUN-2916

Signed-off-by: Todd Short <tshort@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants