search

oracle / oracle-database-operator

The Oracle Database Operator for Kubernetes (a.k.a. OraOperator) helps developers, DBAs, DevOps and GitOps teams reduce the time and complexity of deploying and managing Oracle Databases. It eliminates the dependency on a human operator or administrator for the majority of database operations.
Universal Permissive License v1.0
141 stars 45 forks source link

CDB and PDB resources cannot be operated in other namespaces than the one for OraOperator #79

Closed ilfur closed 1 month ago

ilfur commented 11 months ago

OraOperator is installed in namespace "oracle-database-operator-system". CDB resource is installed in another namespace, like "central-database". PDB resource is installed in another namespace, like "myappdeployment".

The PDB resource needs to reference the CDB in charge to have create/clone/delete operations performed. But the PDB YAML does not allow to specify the CDB's namespace, only the CDB name: when specifying a namespace plus name (dot separated syntax), OraOperator cannot find the CDB resource.

When putting the PDB into the same namespace as the CDB (so it can be referenced properly), then OraOperator is unable to contact the ORDS container because of the missing namespace in it's DNS name. It should be "https://.:"

Please make OraOperator respect the namespaces of it's managed resources, where they are located in. Please do NOT make OraOperator capable of having it installed multiple times. Operators should exist only once system-wide, or there may be many follow-up problems...

mmalvezz commented 1 month ago

Fixed pls have a look at docs/multitenant/usecase03

ilfur commented 3 days ago

Check! Using it heavily in Workshops, good feature of Version 1.1 

   

Gesendet: Dienstag, 01. Oktober 2024 um 09:14 Uhr Von: "matteo malvezzi" @.> An: "oracle/oracle-database-operator" @.> Cc: "ilfur" @.>, "Author" @.> Betreff: Re: [oracle/oracle-database-operator] CDB and PDB resources cannot be operated in other namespaces than the one for OraOperator (Issue #79)

 

Fixed pls have a look at docs/multitenant/usecase03

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>