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

BACKUP_HOST and BACKUP_USER configuration issue in k8s #665

Open
xyfleet opened this issue Jul 31, 2024 · 0 comments
Open

BACKUP_HOST and BACKUP_USER configuration issue in k8s #665

xyfleet opened this issue Jul 31, 2024 · 0 comments

Comments

@xyfleet
Copy link

xyfleet commented Jul 31, 2024

描述
Hello team,
I installed the goInception using the chart [https://github.com/douban/charts/tree/master/charts/goinception] in my k8s cluster. (I installed the Archery and goinception together.)

In the Mysql DB instance, I have several databases, like archery and billing. The database billing is the one that needs archery to check.

The part of config for goInception is:

initEnv:
    - name: BACKUP_HOST
      value: "mysql_instance_endpoint"
    - name: BACKUP_PORT
      value: "3306"
    - name: BACKUP_USER
      value: "root"
    - name: BACKUP_PASSWORD
      value: "xxxxxx"

I found two new databases got created once I ran/committed a sql task successfully on Archery.

inception 
ql_1_xxxx_rds_yyyyy_amazonaws_com_3306_billing

Are all of the settings correct? Do we really need to use root in the section of initEnv? Is there any other account we can use here?

In the MySQL DB, I did not see a user called "inception_bak" or "inception". Is this OK?

Thanks.

重现
Install the chart in k8s, you can reproduce the issue.

环境

  • 数据库: [mysql]
  • 版本: [5.7]
  • goInception chart: 0.3.1

参数

@xyfleet xyfleet changed the title BACKUP_HOST and BACKUP_USER configuration did not take effect in k8s BACKUP_HOST and BACKUP_USER configuration issue in k8s Jul 31, 2024
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

1 participant