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

When creating Autonomous or DBCS, it is not possible to specify region #93

Open
hyder opened this issue Apr 12, 2024 · 2 comments
Open

Comments

@hyder
Copy link
Member

hyder commented Apr 12, 2024

When creating a new Autonomous DB or Base DB system, it is currently not possible to specify the region where we want the database created. This is because the CRD itself doesn't define it and this imposes an unnecessary constraint of having to run a Kubernetes cluster in the same region just to provision the database in the target region.

It would be very desirable to be able to specify the target database's region and allow the operator to create it.

@laguvard
Copy link

I suppose you use instance principal. If you use the ociConfig section, you can create ADB in any tenancy & region. I've been doing that lately from a minikube cluster on my dev machine.

@anders-swanson
Copy link
Member

Instance principal, yes, region is not configurable. But that's OK, usually we want to use instance principal in the same region as the instance.

While ociConfig may be available for user principal and workload identity, I couldn't find the documentation specifying how to use ociConfig. E.g., I was looking for something like:

To authenticate with user principal, set ociConfig to a configmap and secret with the following values...

configmap, secret definitions

... another example for workload identity

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

No branches or pull requests

3 participants