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

Remove operatorkit as a dependency #3722

Open
6 tasks
JosephSalisbury opened this issue Oct 14, 2024 · 0 comments
Open
6 tasks

Remove operatorkit as a dependency #3722

JosephSalisbury opened this issue Oct 14, 2024 · 0 comments
Assignees
Labels
team/planeteers Team Planeteers (Customer Success & Product Management)

Comments

@JosephSalisbury
Copy link
Contributor

JosephSalisbury commented Oct 14, 2024

We need to remove operatorkit as a dependency.

The following projects still use operatorkit, and need to make a plan to remove it.

Projects

  1. team/honeybadger team/planeteers
    JosephSalisbury
  2. team/honeybadger
  3. team/planeteers
  4. team/tenet
  5. team/shield
  6. team/atlas

The following projects we do not need to migrate, with given reasons

  • aws-operator (not used in CAPI)
  • aws-collector (not used in CAPI)
  • cert-operator (not used in CAPI)
  • chart-operator (will be phased out soon)
  • cluster-operator (not used in CAPI)
  • config-controller (not used in CAPI)
  • credentiald (not used in CAPI)
  • node-operator (not used in CAPI)
  • prometheus-meta-operator (not used in CAPI)
  • pss-operator (not used in CAPI)
  • release-operator (not used in CAPI)
@JosephSalisbury JosephSalisbury added the team/planeteers Team Planeteers (Customer Success & Product Management) label Oct 14, 2024
@JosephSalisbury JosephSalisbury self-assigned this Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team/planeteers Team Planeteers (Customer Success & Product Management)
Projects
Status: Inbox 📥
Development

No branches or pull requests

1 participant