Have you checked overlap with https://github.com/VirtusLab/jenkins-operator
?
I was discussing with the authors to get this contributed in jenkinsci
organization. Should avoid a concurrent effort to happen on same topic.
Le lun. 21 janv. 2019 à 05:54, Rick <linuxsu...@gmail.com> a écrit :
> I'm in
>
> On Monday, January 21, 2019 at 6:44:11 AM UTC+8, marky.r...@gmail.com
> wrote:
>>
>> 夏润泽 and I started documenting this JEP and initial code. If anyone is
>> interested in helping let us know.
>>
>> On Sunday, January 20, 2019 at 5:55:45 AM UTC-8, 夏润泽 wrote:
>>>
>>> I also think that creating a prototype is a good suggestion, we can
>>> contact on gitter
>>>
>>> On Sunday, January 20, 2019 at 8:05:51 PM UTC+8, Marky Jackson wrote:
>>>>
>>>> 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" : “marky.r...@gmail.com",
>>>> "team" : "jackson5“
>>>> }
>>>> }
>>>>
>>>> On Jan 20, 2019, at 2:22 AM, Oleg Nenashev <o.v.ne...@gmail.com> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> After reading the proposal from RunzeXia in this pull request
>>>> <https://github.com/jenkins-infra/jenkins.io/pull/2055>, I think that
>>>> the official Kubernetes Operator could be built on the top of the Custom
>>>> WAR/Docker Packager <https://github.com/jenkinsci/custom-war-packager>
>>>> which already supports managing Jenkins versions, plugins and
>>>> configurations via JCasC/Groovy (blog
>>>> <https://jenkins.io/blog/2018/10/16/custom-war-packager/>). 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 <https://github.com/jenkinsci/jep> to document
>>>> YAML formats and the command line options.
>>>>
>>>> Best regards,
>>>> Oleg
>>>>
>>>>
>>>> On Sunday, January 20, 2019 at 3:05:27 AM UTC+1, marky.r...@gmail.com
>>>> 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" : “marky.r...@gmail.com",
>>>>>>> "team" : "jackson5“
>>>>>>> }
>>>>>>> }
>>>>>>>
>>>>>>> On Jan 15, 2019, at 8:38 AM, Jesse Glick <jgl...@cloudbees.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <junw...@gmail.com> 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 jenkinsci-de...@googlegroups.com.
>>>>>>> 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 jenkinsci-de...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/7ad5a2bf-067c-4ef8-9149-ad9207f25af6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/7ad5a2bf-067c-4ef8-9149-ad9207f25af6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzmyaQ%3DjSCaSTH%2BYDgA4qQMpqb_BDswDDKHYZAhynzgSfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
