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

RFC: Add Oracle Cloud Infrastructure (OCI) and Kubernetes Engine (OKE) support #2241

Open
tzach opened this issue Dec 5, 2024 · 2 comments
Open

RFC: Add Oracle Cloud Infrastructure (OCI) and Kubernetes Engine (OKE) support #2241

tzach opened this issue Dec 5, 2024 · 2 comments
Labels
kind/epic Categorizes issue as an epic. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@tzach
Copy link
Contributor

tzach commented Dec 5, 2024 •
edited
Loading

What should the feature do?

Work on Oracle Cloud Infrastructure (OCI) and Kubernetes Engine (OKE) in the same way it works on GKE, EKS

What is the use case behind this feature?

OCI users

Anything else we need to know?

No response
@tzach tzach added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 5, 2024
@scylla-operator-bot scylla-operator-bot bot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Dec 5, 2024
@tnozicka tnozicka added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/epic Categorizes issue as an epic. and removed kind/feature Categorizes issue or PR as related to a new feature. labels Dec 5, 2024
@scylla-operator-bot scylla-operator-bot bot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Dec 5, 2024
@tzach tzach changed the title RFC: Add Oracle Cloud Infrastructure (OCI) support RFC: Add Oracle Cloud Infrastructure (OCI) and Kubernetes Engine (OKE) support Dec 5, 2024
@scylla-operator-bot scylla-operator-bot
Copy link
Contributor

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out

/lifecycle stale

@scylla-operator-bot scylla-operator-bot bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2025
@ylebi
Copy link
Collaborator

ylebi commented Jan 4, 2025

/remove-lifecycle stale

@scylla-operator-bot scylla-operator-bot bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/epic Categorizes issue as an epic. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tzach @ylebi @tnozicka