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

binpath and variant #189

Open
tisonkun opened this issue Feb 20, 2024 · 1 comment
Open

binpath and variant #189

tisonkun opened this issue Feb 20, 2024 · 1 comment

Comments

@tisonkun
Copy link
Contributor

I wonder if gtctl can -

  • specify the binpath of greptimedb in use
  • specify the variant (with PyO3 backend, centos image) in use

.. or we are currently fixedly using some default. If so, what's the default?

cc @zyy17

@zyy17
Copy link
Collaborator

zyy17 commented Feb 22, 2024

@tisonkun, the gtctl will choose the binary and docker images that users mostly use; for example, we use the binary without the pyo3 backend(it's easy to set up) and the ubuntu-based docker image as the default option. Also, the gtctl has the option to specify the binary or docker image, for example:

  • bare-metal deployment: you can use the config file to control the local binary;

  • K8s deployment: you can use the following command to set image:

    gtctl cluster create mycluster \
      --set cluster.image.repository=greptime/greptimedb \
     --set cluster.image.tag=latest
    

Both configurations are not easy to use. I think we should refactor the configurations in the future.

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

2 participants