Re: [hono-dev] removal of fabric8 maven plugin

["Hudalla Kai (INST/ECS4)" <kai.hudalla@xxxxxxxxxxxx>]

Ok, based on the feedback I will start to remove the fabric8 plugin and create
resource descriptors manually. I will use the Kubernetes 1.8 API level. Given
that the current version is 1.10, this should be sufficiently old to support
existing deployments.

Let me know if you think otherwise ...

Kai

On Mon, 2018-06-18 at 12:27 +0200, Dejan Bosanac wrote:
> +1
> 
> As our deployments become more tuned and complex, it makes sense to maintain
> those resources directly.
> 
> On Mon, Jun 18, 2018 at 11:09 AM, Jens Reimann <jreimann@xxxxxxxxxx> wrote:
> > +1
> > 
> > I would prefer a set of well authored files over a few generated ones.
> > 
> > On Mon, Jun 18, 2018 at 9:43 AM, Hudalla Kai (INST/ECS4) <kai.hudalla@bosch-s
> > i.com> wrote:
> > > Hi committers,
> > > 
> > > we are currently using the fabric8 maven plugin [1] for building the Docker
> > > images for our services and generating the Kubernetes resource descriptors.
> > > 
> > > My original intention with using the fabric8 plugin for the latter purpose
> > > was to
> > > be able to completely rely on the plugin to create the descriptors.
> > > However, over
> > > time, this became more and more unrealistic because some of the interesting
> > > features of Kubernetes are not covered by the plugin, e.g. specification of
> > > volume mounts, explicit setting of selectors etc.
> > > 
> > > I have now discovered that it is also not possible to specify resource
> > > limits for
> > > CPU and memory consumption. Based on all of these shortcomings and the fact
> > > that
> > > the plugin seems to generate descriptors based on quite outdated kubernetes
> > > API
> > > (extensions/v1beta1) only, I would therefore suggest to drop the fabric8
> > > maven
> > > plugin and instead manually author and maintain the descriptors as part of
> > > our
> > > example module.
> > > 
> > > We would then also be able to get rid of the example module's dependencies
> > > on all
> > > the other service artifacts and this might also be a good first step
> > > towards
> > > providing Helm charts for the example deployment.
> > > 
> > > WDYT?
> > > 
> > > -- 
> > > Mit freundlichen Grüßen / Best regards
> > > 
> > > Kai Hudalla
> > > Chief Software Architect
> > > 
> > > Bosch Software Innovations GmbH
> > > Ullsteinstr. 128
> > > 12109 Berlin
> > > GERMANY
> > > www.bosch-si.com
> > > 
> > > Registered Office: Berlin, Registration Court: Amtsgericht Charlottenburg;
> > > HRB
> > > 148411 B
> > > Chairman of the Supervisory Board: Dr.-Ing. Thorsten Lücke; Managing
> > > Directors:
> > > Dr. Stefan Ferber, Michael Hahn
> > > _______________________________________________
> > > hono-dev mailing list
> > > hono-dev@xxxxxxxxxxx
> > > To change your delivery options, retrieve your password, or unsubscribe
> > > from this list, visit
> > > https://dev.eclipse.org/mailman/listinfo/hono-dev
> > 
> > 
> > 
> > -- 
> > Jens Reimann
> > Senior Software Engineer / EMEA ENG Middleware
> > Werner-von-Siemens-Ring 14
> > 85630 Grasbrunn
> > Germany
> > phone: +49 89 2050 71286
> > _____________________________________________________________________________
> > 
> > Red Hat GmbH, www.de.redhat.com,
> > Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB
> > 153243,
> > Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael
> > O'Neill
> > 
> > _______________________________________________
> > hono-dev mailing list
> > hono-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe from
> > this list, visit
> > https://dev.eclipse.org/mailman/listinfo/hono-dev
> > 
> 
> 
> 
> _______________________________________________
> hono-dev mailing list
> hono-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/hono-dev