2:34 p.m.
From my comments earlier today:
"The agent itself should only be using the Kubernetes API and shouldn't have
anything specific to OpenShift. So the agent here shouldn't care or know if its really
connecting to Kubernetes or OpenShift.
The problem is more that the Hawkular Metrics integration we have with OpenShift wont work
in plain Kubernetes and we don't test it there. It would be possible to make it work
on Kubernetes, but it wouldn't be a trivial change and would take some effort and
testing to get it working there. We don't have the spare cycles or manpower to support
the Kubernetes use case right now and this isn't even on our radar. It might be cool
to have something usable with the upstream Kubernetes community though."
Since we don't have a Hawkular Metrics version that is being used and tested in
Kubernetes, I would be against using a name with 'Kubernetes' in it at this
moment. Its going to be confusing to anyone who wants to try this in the Kubernetes
directly, as the agent may work, but what it writes to will not.
We may also want to add in some OpenShift specific features in there as well.
I would vote to call it the "Hawkular OpenShift Agent" rather than the
"Hawkular Kubernetes Agent" for these reasons.
----- Original Message -----
From: "John Mazzitelli" <mazz(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Wednesday, 19 October, 2016 10:31:07 AM
Subject: Re: [Hawkular-dev] open shift agent - what to call it?
I defer to Matt :)
He seems to have his finger on the pulse of Open Shift and could say if he
thinks there are some specific OS features (current or future features) we
will want to take advantage of.
----- Original Message -----
> How about the forseeable future ? I know it's a big question :)
>
> Thomas
>
> On Wed, Oct 19, 2016 at 4:21 PM, John Mazzitelli <mazz(a)redhat.com> wrote:
>
> > > As far as I can tell this agent (as of today, think of the demo I
> > > showed
> > > yesterday) does not use anything Open Shift specific. Its all k8s APIs
> > > we
> > > are calling. But I've only ever run it against an Open Shift
> > installation.
> >
> > Here's the Go imports - notice all k8s - so nothing OS specific:
> >
> > core "k8s.io/client-go/1.4/kubernetes/typed/core/v1"
> > "k8s.io/client-go/1.4/pkg/api"
> > "k8s.io/client-go/1.4/pkg/api/v1"
> > "k8s.io/client-go/1.4/pkg/fields"
> > "k8s.io/client-go/1.4/pkg/watch"
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> >
> >
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev