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.

Sign up for GitHub

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

Jump to bottom

Follow-up(add extension API): Remove ExtensionInterface and related functions/implementations #634

Closed
Tracked by #591
joelanford opened this issue Feb 21, 2024 · 1 comment · Fixed by #644
Closed
Tracked by #591

Follow-up(add extension API): Remove ExtensionInterface and related functions/implementations #634

joelanford opened this issue Feb 21, 2024 · 1 comment · Fixed by #644
Assignees
@joelanford

Comments

@joelanford
Copy link
Member

Current plan is to remove ClusterExtension, so no need to introduce an abstraction that will very shortly obsolete when we do remove ClusterExtension. If plans change and ClusterExtension sticks around, we can re-assess the need for an abstraction.
@joelanford joelanford mentioned this issue Feb 21, 2024
Closed
16 tasks
@joelanford joelanford self-assigned this Feb 21, 2024
@joelanford
Copy link
Member Author

Once #642 merges, the types/functions mentioned in this issue become dead code. I've got a branch ready to rebase after that merges.

@joelanford joelanford mentioned this issue Feb 21, 2024
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joelanford joelanford

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

✨ remove ExtensionInterface and related functions/implementations joelanford/operator-controller
1 participant
@joelanford