Chef Ideas

We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.

We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.

Thanks for collaborating with us!

Allow for Container-based Deployment of Chef Infra/Automate Stack

It would be ideal if Chef Automate (and Infra Server) were able to be deployed as a (series of) container(s).

A great deal of organizations have begun to standardize on containers as their preferred mechanism for deploying services within their infrastructure. Unfortunately, Chef is very much a "legacy" system insofar that container-based deployments simply are not feasible.

By allowing for deployment of the Chef stack via containers, it could reduce the time-to-deploy the service(s) -- as well as increase resiliency -- for some organizations.

While I understand this request does not jive well with the Habitat paradigm, I still think it is a valid request that should be considered for future iterations of Chef.

  • Austin Culter
  • Jun 22 2021
  • Currently Declined
  • Attach files
  • Dustin Davis commented
    1 Jun, 2022 08:17pm

    Im also unable to view A2-I-33, but we would love to have this feature.

  • Austin Culter commented
    1 Jun, 2022 08:50am

    @Ankur Mundhra => I am unable to view the A2-I-33 feature request/Idea; is it perhaps only viewable by internal Progress folks? Or is there a corresponding Aha idea that is externally viewable?

  • Ankur Mundhra commented
    28 Jun, 2021 06:45am

    Hey Austin,
    Thanks for raising this request. This is contained by A2-I-33. Grouping them and encourage more upvotes on the same.