Hi folks, is there any guidance on this ? https://github.com/airbytehq/airbyte/issues/64560

The knowledge sources confirm that Bitnami will stop publishing their Docker images as of August 28th, which impacts Airbyte’s Helm charts—specifically, the use of the bitnami/kubectl image for pod-sweeper and other dependencies. Users have noted that simply switching to another kubectl image may not work as expected, especially if the replacement image lacks /bin/bash, which the Bitnami image included. A temporary workaround for self-hosters is to override the image repository to use bitnamilegacy/kubectl for the pod-sweeper, as shown:

yaml pod-sweeper:   enabled: true   image:     repository: bitnamilegacy/kubectl # <-- Override this

Additionally, it’s noted that the pod-sweeper Helm chart is no longer included in the latest Airbyte Helm charts (v1.8.x), with the last release being v1.5.x. There was an attempt to merge pod-sweeper functionality into the workload-launcher, but this was reverted. Users are seeking clarification on whether to continue deploying the airbyte-pod-sweeper chart separately or expect future changes to handle pod cleanup within another component. As of now, there is no official guidance or roadmap update provided in the knowledge sources regarding the long-term solution for pod-sweeper functionality or Bitnami dependency removal. In summary, the best available guidance is to use the bitnamilegacy/kubectl image as a temporary fix and monitor for future updates from the Airbyte team regarding a more permanent solution or changes to pod cleanup management. If you need more official direction, you may want to follow the GitHub issue for updates or reach out via Airbyte’s community channels for the latest information[Upcoming changes to the Bitnami catalog impacting Airbyte](https://github.com/airbytehq/airbyte/issues/64560).