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

Script is not able to pull elasticsearch init container #9

Open
sanketnagdive opened this issue Feb 22, 2024 · 2 comments
Open

Script is not able to pull elasticsearch init container #9

sanketnagdive opened this issue Feb 22, 2024 · 2 comments

Comments

@sanketnagdive
Copy link
Collaborator

Elastic search init container was pulling image from a repo bitnami-shell which is moved to archival(name bitnami-shell-archived). Updated the scripts to use same image from repo bitnami-shell-archived.
cc @gandham-santhosh @mohitga @vinukumar-vs @santhosh-tg @keshavprasadms

@mohitga
Copy link

mohitga commented Feb 23, 2024

@keshavprasadms do we need to use the archived image of elastic search?

@lazylua
Copy link
Contributor

lazylua commented Feb 26, 2024

Hi @sanketnagdive Thank you for bringing this to notice. We're using standard bitnami charts for most dbs, and the es version we're using is not the latest. That's why we're using the bitnami-shell, which come packaged with the version specific chart. It'll get updated, once we change the verison of elastic search. For now, the image is only archived, and the usage is just to bootstrap the container, not to run any apps. So I don't think there are any issues. But if you want to use the latest image, you can override the global-values.yaml file to change the init container in elasticsearch block.

elastisearch:
  volumePermissions:
      image:
        registry: docker.io
        repository: bitnami/os-shell
        tag: latest

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