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

Provide a Helm chart for standalone and RAC Oracle deployments on Kubernetes #1042

Closed
luisdavim opened this issue Nov 6, 2018 · 8 comments
Closed
Assignees
Labels

Comments

@luisdavim
Copy link

Please provide a simple way to deploy Oracle databases on Kubernetes

@Djelibeybi
Copy link
Member

Helm charts are on the roadmap, but there is no ETA for this yet.

@luisdavim
Copy link
Author

Thanks for the answer, maybe you could keep the ticket open to track the request and see if someone out there is interested in working on it. I might if I get some free time to do it.

@ctienshi
Copy link

Any update on this issue? I am also currently looking for helm chart to deploy Oracle database.

@dangrafic
Copy link

Hi any update on this topic? Is there any Helm Chart to deploy Oracle Database standalone or RAC on Kubernetes? By advance thanks

@n3mawashi
Copy link

Hi, Is there any update on this. Ideally we would like to pass ASM LUNS to it as well.

@Djelibeybi
Copy link
Member

Reopened and assigned to @gvenzl (for standalone) and @psaini79 (for RAC).

@MnrGreg
Copy link

MnrGreg commented Jul 6, 2020

Enabling some form of HA here (even Active/Passive with RAC-One-Node) would open a number of Test/Dev use-cases on Kubernetes. Most Kubernetes platforms are in a constant state of flux, whether it be Draining due to platform maintenance; or nodes coming and going through Cluster Autoscaling. The availability of a Standalone Oracle DB deployment in the above scenarios is likely not workable for application develop teams.

Is it worth starting a document to discuss approaches for moving an HA solution forward? Could start with some suggestions for simplifying this. For example:

  1. Develop raw yaml before templating into Helm
  2. Separate the manifests for Standalone, RAC One Node and RAC deployments
  3. Descope ASM and start with NFS
  4. Develop for a static number of instances (e.g. 3) and descope lifecycle changes such as joining or removing instances

Discuss possible approaches for Kubernetes challenges, for example:

  • Clusterware requirement: Public & Private interfaces within a Pod (possibly use Multus CNI)
  • Clusterware requirement: Private interface multicast/broadcast capability (again possibly use Multus CNI)
  • Which Kubernetes pattern and why: StatefulSet vs Deployment
  • ...

@Djelibeybi
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants