Code Monkey home page Code Monkey logo

Comments (7)

austince avatar austince commented on May 24, 2024 2

We needed this over at FinTech Studios, so we've published an image here: https://hub.docker.com/r/fintechstudios/helm-s3

Happy to donate this back if you would like!

from helm-s3.

hypnoglow avatar hypnoglow commented on May 24, 2024 1

I think having the bleeding-edge master builds available as some tag is quite helpful when testing bug fixes/ new features before officially including them in a release.

BTW master image is already available under tags like master-helm2.15.

from helm-s3.

hypnoglow avatar hypnoglow commented on May 24, 2024

Hi,

This is a great idea. I was using my in-house docker image with this plugin, but haven't added the Dockerfile to this repo yet.

I think I'll include the Dockerfile and the official docker image in the next release.

from helm-s3.

austince avatar austince commented on May 24, 2024

Looks great! Is it possible to push a latest tag as well so pulling the repository without specifying a tag will work?

> docker pull hypnoglow/helm-s3

Using default tag: latest
Error response from daemon: manifest for hypnoglow/helm-s3:latest not found: manifest unknown: manifest unknown

from helm-s3.

hypnoglow avatar hypnoglow commented on May 24, 2024

@austince In your opinion, what versions should the latest tag represent? The latest tagged release with the latest supported Helm? Or the master branch?

I'm usually against this because it is pretty much unclear what latest is. In some repos, the latest is just bleeding-edge master builds, in other it is the latest stable version. I'm towards the latter.

But to support pulling the image without explicit tag (docker pull hypnoglow/helm-s3) we could support it, hoping for user responsibility to use proper tags in their "production" use cases.

from helm-s3.

austince avatar austince commented on May 24, 2024

Yeah, I would agree with you that latest is ambiguous and should never be used in production environments, and would also agree that it makes sense as the latest stable version. I've seen next , or similar, used as a tag for the bleeding-edge master builds. I think having the bleeding-edge master builds available as some tag is quite helpful when testing bug fixes/ new features before officially including them in a release.

from helm-s3.

austince avatar austince commented on May 24, 2024

Great, that checks that box then.

from helm-s3.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.