I agree that creating a prototype is the best path forward.
We can split the work up for documenting that yaml format and the cli options.
I will wait to hear from RunzeXia and we can have further discussion (please 
reach out to me on gitter or via email).
Thanks kindly.
{     
   "regards" : {
        "name" : “marky”,
        "phone" : "+1 (408) 464 2965”,
        "email" : “[email protected]",
        "team" : "jackson5“
    }
}

> On Jan 20, 2019, at 2:22 AM, Oleg Nenashev <[email protected]> wrote:
> 
> Hi all,
> 
> After reading the proposal from RunzeXia in this pull request, I think that 
> the official Kubernetes Operator could be built on the top of the Custom 
> WAR/Docker Packager which already supports managing Jenkins versions, plugins 
> and configurations via JCasC/Groovy (blog). It's configured via YAML and it 
> can already produce Docker images and standalone WAR files. 
> 
> I believe that CWP could be adjusted to support the Kubernetes Operator mode, 
> even for Kubernetes deployments without Docker. The same Custom War Packager 
> is used in Jenkins X Serverless, so we can make the configurations somewhat 
> portable between "Serverless Jenkins" modes and more classic K8s operators. 
> What do you think?
> 
>> Who/how can we go about starting this? I will gladly upload my code but it 
>> might be best to have some guidelines or plan
> 
> If the Kubernetes Operator requires a lot of design and requires long-term 
> compatibility, it might be reasonable to create a prototype, agree on that in 
> this thread and then to create a specification Jenkins Enhancement Proposal 
> to document YAML formats and the command line options. 
> 
> Best regards,
> Oleg
> 
> 
>> On Sunday, January 20, 2019 at 3:05:27 AM UTC+1, [email protected] wrote:
>> Who/how can we go about starting this? I will gladly upload my code but it 
>> might be best to have some guidelines or plan
>> 
>>> On Thursday, January 17, 2019 at 9:25:27 PM UTC-8, 夏润泽 wrote:
>>> Very good, I think we can start working from your operator
>>> 
>>>> On Wednesday, January 16, 2019 at 12:42:38 AM UTC+8, Marky Jackson wrote:
>>>> I’ve done some current operator work and have submitted an upcoming talk 
>>>> on operators. 
>>>> I would love to even just tinker with this idea
>>>> 
>>>> {     
>>>>    "regards" : {
>>>>         "name" : “marky”,
>>>>         "phone" : "+1 (408) 464 2965”,
>>>>         "email" : “[email protected]",
>>>>         "team" : "jackson5“
>>>>     }
>>>> }
>>>> 
>>>>> On Jan 15, 2019, at 8:38 AM, Jesse Glick <[email protected]> wrote:
>>>>> 
>>>>>> On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <[email protected]> wrote:
>>>>>> we could use the k8s jenkins operator to do more things, such as the 
>>>>>> health status of jenkins (whether the configuration is consistent and 
>>>>>> the necessary components are normal)、 automatic update based on Jenkins 
>>>>>> Evergreen…
>>>>> 
>>>>> There is nothing being done in this area currently. Sounds like a
>>>>> sensible addition to
>>>>> 
>>>>> https://jenkins.io/sigs/cloud-native/#areas-for-improvement
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "Jenkins Developers" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>>> email to [email protected].
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/FEF32FB3-40C7-4876-BA07-9AAB2309A939%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to