MySQL Bugs: #117953: MySQL Operator is unable to use Instance Principal or OKE Workload Identity on OCI

Bug #117953	MySQL Operator is unable to use Instance Principal or OKE Workload Identity on OCI
Submitted:	12 Apr 16:24	Modified:	15 Apr 12:38
Reporter:	Arnold Galovics	Email Updates:
Status:	Need Feedback	Impact on me:	None
Category:	MySQL Operator	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
Based on the docs and the code as well, MySQL Operator for Kubernetes is only capable to use direct configuration when running and backing up to OCI.

I'm not sure how this was not implemented before but if security is critical, you don't want to expose a direct configuration via environment variables to interact with OCI, rather you want to use Instance Principal or OKE Workload Identity.

How to repeat:
See description.

Hi,

Can you, please, define what would you like to change. We do accept feature requests for MySQL operator but I would appreciate if you can define it fully.

Thanks.