Hi Greg, Thanks for your suggestion. We saw the `images` code block you referred to. What was not intuitive was the `registry` code block which was where we defined the host and access credentials to access our internal registry. I will prepare a patch to improve the documentation. lewismc
On 2021/03/10 19:58:20, Greg Neiheisel <[email protected]> wrote: > Hey Lewis, that block is to populate the image pull secret if your > repository is protected. To override the image that is being pulled for the > Airflow pods I believe you need to override the values here - > https://github.com/apache/airflow/blob/master/chart/values.yaml#L30-L34. > > On Wed, Mar 10, 2021 at 1:54 PM Lewis John McGibbney <[email protected]> > wrote: > > > I found the `registry` key in values.yaml. > > https://github.com/apache/airflow/blob/master/chart/values.yaml#L626-L637 > > We are experimenting with this and I will update here if we get it to work. > > I'll then pull a documentation patch together. > > lewismc > > > > On 2021/03/10 18:34:17, Lewis John McGibbney <[email protected]> wrote: > > > Hello users@, > > > We wanted to turn on Airflow Sentry integration and deploying into K8s > > using Helm. > > > It is not clear how one would define the 'new/custom' Airflow container > > which resides in our internal enterprise container registry i.e. JFrog's > > Artifactory. > > > If someone can guide me on this then I will provide a documentation > > update. > > > Thank you > > > lewismc > > > > > > > > -- > *Greg Neiheisel* / Chief Architect Astronomer.io >
