jenkins official kubernetes operator

classic Classic list List threaded Threaded
41 messages Options
123
Reply | Threaded
Open this post in threaded view
|

jenkins official kubernetes operator

夏润泽-2
Hi dev:
   In the cloud native domain, kubernetes is an important part, and now many software are using kubernetes operator to manage applications in kubernetes.
   Now we can manage jenkins through groovy scripts, casc plugins, etc.In particular, the casc plugin allows us to manage jenkins with declarative code.
   But I think there are still some problems in it. I deployed my jenkins in the kubernetes cluster and managed my jenkins through the groovy script and the casc plugin. But once the jenkins is started, I need to modify the configuration of the casc, then I need to submit the configuration to the jenkins dashborad, and the submitted configuration is not necessarily successful, and there is no failure record. In other words, although I have a casc configuration file, it is difficult for me to ensure that my environment is consistent with the casc configuration. Or at least let me know that my current configuration is incorrect, I need to fix it.
   If we can provide an official jenkins operator to manage jenkins in kubernetes, it must be great.
   I hope to hear your opinions.

Best wishes 
RunzeXia

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

Carlos Sanchez
I thought about it, and yes it would be interesting to have an operator that watches a configmap and ensures jenkins is always updated.
However with serverless jenkins[1] you wouldn't need to worry about that anymore (if you can use serverless).



On Tue, Jan 15, 2019 at 6:37 AM 夏润泽 <[hidden email]> wrote:
Hi dev:
   In the cloud native domain, kubernetes is an important part, and now many software are using kubernetes operator to manage applications in kubernetes.
   Now we can manage jenkins through groovy scripts, casc plugins, etc.In particular, the casc plugin allows us to manage jenkins with declarative code.
   But I think there are still some problems in it. I deployed my jenkins in the kubernetes cluster and managed my jenkins through the groovy script and the casc plugin. But once the jenkins is started, I need to modify the configuration of the casc, then I need to submit the configuration to the jenkins dashborad, and the submitted configuration is not necessarily successful, and there is no failure record. In other words, although I have a casc configuration file, it is difficult for me to ensure that my environment is consistent with the casc configuration. Or at least let me know that my current configuration is incorrect, I need to fix it.
   If we can provide an official jenkins operator to manage jenkins in kubernetes, it must be great.
   I hope to hear your opinions.

Best wishes 
RunzeXia

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

nicolas de loof-2
Introducing a watcher to reload changes has been proposed for Configuration-as-Code: https://github.com/jenkinsci/configuration-as-code-plugin/issues/76
just need to be implemented ...

Le mar. 15 janv. 2019 à 09:17, Carlos Sanchez <[hidden email]> a écrit :
I thought about it, and yes it would be interesting to have an operator that watches a configmap and ensures jenkins is always updated.
However with serverless jenkins[1] you wouldn't need to worry about that anymore (if you can use serverless).



On Tue, Jan 15, 2019 at 6:37 AM 夏润泽 <[hidden email]> wrote:
Hi dev:
   In the cloud native domain, kubernetes is an important part, and now many software are using kubernetes operator to manage applications in kubernetes.
   Now we can manage jenkins through groovy scripts, casc plugins, etc.In particular, the casc plugin allows us to manage jenkins with declarative code.
   But I think there are still some problems in it. I deployed my jenkins in the kubernetes cluster and managed my jenkins through the groovy script and the casc plugin. But once the jenkins is started, I need to modify the configuration of the casc, then I need to submit the configuration to the jenkins dashborad, and the submitted configuration is not necessarily successful, and there is no failure record. In other words, although I have a casc configuration file, it is difficult for me to ensure that my environment is consistent with the casc configuration. Or at least let me know that my current configuration is incorrect, I need to fix it.
   If we can provide an official jenkins operator to manage jenkins in kubernetes, it must be great.
   I hope to hear your opinions.

Best wishes 
RunzeXia

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


--
Nicolas De Loof

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzmk-ULGcGcPTpCoURQnTwEqwnuwxv6a_ZCFudD6a57g5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

夏润泽-2
CasC support observer mode is a very powerful and useful function. But 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…………

On Tuesday, January 15, 2019 at 4:19:53 PM UTC+8, nicolas de loof wrote:
Introducing a watcher to reload changes has been proposed for Configuration-as-Code: <a href="https://github.com/jenkinsci/configuration-as-code-plugin/issues/76" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fconfiguration-as-code-plugin%2Fissues%2F76\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEXPzje-OZrcNtUGPtk2IH_StE42w&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fconfiguration-as-code-plugin%2Fissues%2F76\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEXPzje-OZrcNtUGPtk2IH_StE42w&#39;;return true;">https://github.com/jenkinsci/configuration-as-code-plugin/issues/76
just need to be implemented ...

Le mar. 15 janv. 2019 à 09:17, Carlos Sanchez <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="zIHbA2kaCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">car...@...> a écrit :
I thought about it, and yes it would be interesting to have an operator that watches a configmap and ensures jenkins is always updated.
However with serverless jenkins[1] you wouldn't need to worry about that anymore (if you can use serverless).


[1] <a href="https://medium.com/@jdrawlings/serverless-jenkins-with-jenkins-x-9134cbfe6870" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fmedium.com%2F%40jdrawlings%2Fserverless-jenkins-with-jenkins-x-9134cbfe6870\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH9ZwsTYcS9yFjzJP4c6F5zDq7bTA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fmedium.com%2F%40jdrawlings%2Fserverless-jenkins-with-jenkins-x-9134cbfe6870\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH9ZwsTYcS9yFjzJP4c6F5zDq7bTA&#39;;return true;">https://medium.com/@jdrawlings/serverless-jenkins-with-jenkins-x-9134cbfe6870

On Tue, Jan 15, 2019 at 6:37 AM 夏润泽 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="zIHbA2kaCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">junw...@...> wrote:
Hi dev:
   In the cloud native domain, kubernetes is an important part, and now many software are using kubernetes operator to manage applications in kubernetes.
   Now we can manage jenkins through groovy scripts, casc plugins, etc.In particular, the casc plugin allows us to manage jenkins with declarative code.
   But I think there are still some problems in it. I deployed my jenkins in the kubernetes cluster and managed my jenkins through the groovy script and the casc plugin. But once the jenkins is started, I need to modify the configuration of the casc, then I need to submit the configuration to the jenkins dashborad, and the submitted configuration is not necessarily successful, and there is no failure record. In other words, although I have a casc configuration file, it is difficult for me to ensure that my environment is consistent with the casc configuration. Or at least let me know that my current configuration is incorrect, I need to fix it.
   If we can provide an official jenkins operator to manage jenkins in kubernetes, it must be great.
   I hope to hear your opinions.

Best wishes 
RunzeXia

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="zIHbA2kaCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="zIHbA2kaCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.


--
Nicolas De Loof

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/50fe6f42-9d2a-443b-ad95-4b0c660f1fe4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

夏润泽-2
In reply to this post by Carlos Sanchez
Jenkins of serverless cannot meet my needs at present, but I have to say that when it becomes more perfect, it will be a very cool features.

On Tuesday, January 15, 2019 at 4:17:19 PM UTC+8, Carlos Sanchez wrote:
I thought about it, and yes it would be interesting to have an operator that watches a configmap and ensures jenkins is always updated.
However with serverless jenkins[1] you wouldn't need to worry about that anymore (if you can use serverless).


[1] <a href="https://www.google.com/url?q=https%3A%2F%2Fmedium.com%2F%40jdrawlings%2Fserverless-jenkins-with-jenkins-x-9134cbfe6870&amp;sa=D&amp;sntz=1&amp;usg=AFQjCNH9ZwsTYcS9yFjzJP4c6F5zDq7bTA" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fmedium.com%2F%40jdrawlings%2Fserverless-jenkins-with-jenkins-x-9134cbfe6870\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH9ZwsTYcS9yFjzJP4c6F5zDq7bTA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fmedium.com%2F%40jdrawlings%2Fserverless-jenkins-with-jenkins-x-9134cbfe6870\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH9ZwsTYcS9yFjzJP4c6F5zDq7bTA&#39;;return true;">https://medium.com/@jdrawlings/serverless-jenkins-with-jenkins-x-9134cbfe6870

On Tue, Jan 15, 2019 at 6:37 AM 夏润泽 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="BDbOTkUaCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">junw...@...> wrote:
Hi dev:
   In the cloud native domain, kubernetes is an important part, and now many software are using kubernetes operator to manage applications in kubernetes.
   Now we can manage jenkins through groovy scripts, casc plugins, etc.In particular, the casc plugin allows us to manage jenkins with declarative code.
   But I think there are still some problems in it. I deployed my jenkins in the kubernetes cluster and managed my jenkins through the groovy script and the casc plugin. But once the jenkins is started, I need to modify the configuration of the casc, then I need to submit the configuration to the jenkins dashborad, and the submitted configuration is not necessarily successful, and there is no failure record. In other words, although I have a casc configuration file, it is difficult for me to ensure that my environment is consistent with the casc configuration. Or at least let me know that my current configuration is incorrect, I need to fix it.
   If we can provide an official jenkins operator to manage jenkins in kubernetes, it must be great.
   I hope to hear your opinions.

Best wishes 
RunzeXia

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="BDbOTkUaCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3278c9bb-a74d-47cf-b695-46da5cef3685%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

Jesse Glick-4
In reply to this post by 夏润泽-2
On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <[hidden email]> 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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

Marky Jackson
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" : "<a href="tel:+1%20(408)%20464%202965" dir="ltr" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="0">+1 (408) 464 2965”,
        "email" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 15, 2019, at 8:38 AM, Jesse Glick <[hidden email]> wrote:

On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <[hidden email]> 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 [hidden email].
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/BA076E0F-B247-4118-B930-A36CF4A46297%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

夏润泽-2
In reply to this post by Jesse Glick-4
Recently there are a lot of things in the company, I will submit relevant PR on the weekend.

On Wednesday, January 16, 2019 at 12:38:24 AM UTC+8, Jesse Glick wrote:
On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="Vw9KUp01CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">junw...@...> 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

<a href="https://www.google.com/url?q=https%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement&amp;sa=D&amp;sntz=1&amp;usg=AFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0bc3ccce-b1df-4d9d-8442-2ebedc393ee1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

夏润泽-2
In reply to this post by Marky Jackson
非常好,我想我们可以从您的运营商开始工作

周一,2019年1月16日星期三上午12:42:38 UTC + 8,Marky Jackson写道:
我已完成了一些当前的操作员工作,并提交了关于操作员的即将到来的演讲。 
我很想甚至只是修补这个想法

{     
   “问候”:{
        “name”:“marky”,
        “phone”:“ + 1(408)464 2965 ”,
        “email”:“ <a href="javascript:" dir="ltr" target="_blank" gdf-obfuscated-mailto="1UTTX9g1CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">marky.r ... @ gmail.com ”,
        “team”:“杰克逊5“
    }
}

在2019年1月15日上午8:38,Jesse Glick < <a href="javascript:" target="_blank" gdf-obfuscated-mailto="1UTTX9g1CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jgl ... @ cloudbees.com >写道:

在2019年1月15日星期二上午7:56夏润泽< <a href="javascript:" target="_blank" gdf-obfuscated-mailto="1UTTX9g1CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">junw ... @ gmail.com >写道:
我们可以使用k8s jenkins运算符来做更多的事情,比如jenkins的健康状态(配置是否一致以及必要的组件是否正常),基于Jenkins Evergreen的自动更新......

目前在这个领域没有做任何事情。听起来像是一个
明智的补充

<a href="https://jenkins.io/sigs/cloud-native/#areas-for-improvement" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;">https://jenkins.io/sigs/cloud-native/#areas-for-improvement

-
您收到此邮件是因为您订阅了Google网上论坛“Jenkins Developers”群组。
要取消订阅此论坛并停止接收来自该论坛的电子邮件,请发送电子邮件至<a href="javascript:" target="_blank" gdf-obfuscated-mailto="1UTTX9g1CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de ... @ googlegroups.com
要在网络上查看此讨论,请访问<a href="https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/ msgid / jenkinsci-dev / CANfRfr24Y6Vpq2YnUXT3BubDuuzpT Xmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com
有关更多选项,请访问<a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/57f120ee-2691-4668-ae37-afa5ef0b8748%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

nicolas de loof-2
I guess you might be interested by https://github.com/VirtusLab/jenkins-operator

Le jeu. 17 janv. 2019 à 15:06, 夏润泽 <[hidden email]> a écrit :
非常好,我想我们可以从您的运营商开始工作

周一,2019年1月16日星期三上午12:42:38 UTC + 8,Marky Jackson写道:
我已完成了一些当前的操作员工作,并提交了关于操作员的即将到来的演讲。 
我很想甚至只是修补这个想法

{     
   “问候”:{
        “name”:“marky”,
        “phone”:“ + 1(408)464 2965 ”,
        “email”:“ marky.r ... @ gmail.com ”,
        “team”:“杰克逊5“
    }
}

在2019年1月15日上午8:38,Jesse Glick < jgl ... @ cloudbees.com >写道:

在2019年1月15日星期二上午7:56夏润泽< junw ... @ gmail.com >写道:
我们可以使用k8s jenkins运算符来做更多的事情,比如jenkins的健康状态(配置是否一致以及必要的组件是否正常),基于Jenkins Evergreen的自动更新......

目前在这个领域没有做任何事情。听起来像是一个
明智的补充

https://jenkins.io/sigs/cloud-native/#areas-for-improvement

-
您收到此邮件是因为您订阅了Google网上论坛“Jenkins Developers”群组。
要取消订阅此论坛并停止接收来自该论坛的电子邮件,请发送电子邮件至jenkinsci-de ... @ googlegroups.com
要在网络上查看此讨论,请访问https://groups.google.com/d/ msgid / jenkinsci-dev / CANfRfr24Y6Vpq2YnUXT3BubDuuzpT Xmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com
有关更多选项,请访问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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/57f120ee-2691-4668-ae37-afa5ef0b8748%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
Nicolas De Loof

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzmNZ4SGauE6M1EV2Woyrdt4tba88csvxrByoBwsNyRCFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

夏润泽-2
In reply to this post by Marky Jackson
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" : “<a href="javascript:" dir="ltr" target="_blank" gdf-obfuscated-mailto="1UTTX9g1CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">marky.r...@...",
        "team" : "jackson5“
    }
}

On Jan 15, 2019, at 8:38 AM, Jesse Glick <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="1UTTX9g1CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jgl...@...> wrote:

On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="1UTTX9g1CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">junw...@...> 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

<a href="https://jenkins.io/sigs/cloud-native/#areas-for-improvement" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="1UTTX9g1CAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/77ad66c8-7364-4937-a375-9422e935ed75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

Marky Jackson
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" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 15, 2019, at 8:38 AM, Jesse Glick <[hidden email]> wrote:

On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <[hidden email]> 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

<a href="https://jenkins.io/sigs/cloud-native/#areas-for-improvement" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;">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 <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/294a0e29-a75d-43b6-b421-b5c76f8b940d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

Oleg Nenashev
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, [hidden email] 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" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 15, 2019, at 8:38 AM, Jesse Glick <[hidden email]> wrote:

On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <[hidden email]> 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

<a href="https://jenkins.io/sigs/cloud-native/#areas-for-improvement" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;">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 <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

Marky Jackson
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" : "<a href="tel:+1%20(408)%20464%202965" dir="ltr" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="0">+1 (408) 464 2965”,
        "email" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 20, 2019, at 2:22 AM, Oleg Nenashev <[hidden email]> 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, 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" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 15, 2019, at 8:38 AM, Jesse Glick <[hidden email]> wrote:

On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <[hidden email]> 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 [hidden email].
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 [hidden email].
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 | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

夏润泽-2
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" : “<a href="javascript:" dir="ltr" target="_blank" gdf-obfuscated-mailto="ln_W6x37FAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">marky.r...@...",
        "team" : "jackson5“
    }
}

On Jan 20, 2019, at 2:22 AM, Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="ln_W6x37FAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.ne...@...> wrote:

Hi all,

After reading the proposal from RunzeXia in <a href="https://github.com/jenkins-infra/jenkins.io/pull/2055" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2055\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFmlVi2FwbvVQzVjncAmTlonAVQtQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2055\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFmlVi2FwbvVQzVjncAmTlonAVQtQ&#39;;return true;">this pull request, I think that the official Kubernetes Operator could be built on the top of the <a href="https://github.com/jenkinsci/custom-war-packager" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fcustom-war-packager\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGZ8p07iUV2ifEZVyat2n2EvCQjpQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fcustom-war-packager\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGZ8p07iUV2ifEZVyat2n2EvCQjpQ&#39;;return true;">Custom WAR/Docker Packager which already supports managing Jenkins versions, plugins and configurations via JCasC/Groovy (<a href="https://jenkins.io/blog/2018/10/16/custom-war-packager/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fblog%2F2018%2F10%2F16%2Fcustom-war-packager%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE3mNTw0eCWV2XhKAtnFzZGSvQlKg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fblog%2F2018%2F10%2F16%2Fcustom-war-packager%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE3mNTw0eCWV2XhKAtnFzZGSvQlKg&#39;;return true;">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 <a href="https://github.com/jenkinsci/jep" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHu9RZgOvMHcAd6kq-X5ZTU9uJTNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHu9RZgOvMHcAd6kq-X5ZTU9uJTNw&#39;;return true;">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, marky.r...@<a href="http://gmail.com" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://gmail.com&#39;;return true;" onclick="this.href=&#39;http://gmail.com&#39;;return true;">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" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 15, 2019, at 8:38 AM, Jesse Glick <[hidden email]> wrote:

On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <[hidden email]> 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

<a href="https://jenkins.io/sigs/cloud-native/#areas-for-improvement" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;">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 <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="ln_W6x37FAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1e0a676d-efe6-4734-8d4f-0786f1941d12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

Marky Jackson
夏润泽 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" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 20, 2019, at 2:22 AM, Oleg Nenashev <[hidden email]> wrote:

Hi all,

After reading the proposal from RunzeXia in <a href="https://github.com/jenkins-infra/jenkins.io/pull/2055" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2055\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFmlVi2FwbvVQzVjncAmTlonAVQtQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2055\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFmlVi2FwbvVQzVjncAmTlonAVQtQ&#39;;return true;">this pull request, I think that the official Kubernetes Operator could be built on the top of the <a href="https://github.com/jenkinsci/custom-war-packager" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fcustom-war-packager\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGZ8p07iUV2ifEZVyat2n2EvCQjpQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fcustom-war-packager\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGZ8p07iUV2ifEZVyat2n2EvCQjpQ&#39;;return true;">Custom WAR/Docker Packager which already supports managing Jenkins versions, plugins and configurations via JCasC/Groovy (<a href="https://jenkins.io/blog/2018/10/16/custom-war-packager/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fblog%2F2018%2F10%2F16%2Fcustom-war-packager%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE3mNTw0eCWV2XhKAtnFzZGSvQlKg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fblog%2F2018%2F10%2F16%2Fcustom-war-packager%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE3mNTw0eCWV2XhKAtnFzZGSvQlKg&#39;;return true;">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 <a href="https://github.com/jenkinsci/jep" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHu9RZgOvMHcAd6kq-X5ZTU9uJTNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHu9RZgOvMHcAd6kq-X5ZTU9uJTNw&#39;;return true;">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, marky.r...@<a href="http://gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://gmail.com&#39;;return true;" onclick="this.href=&#39;http://gmail.com&#39;;return true;">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" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 15, 2019, at 8:38 AM, Jesse Glick <[hidden email]> wrote:

On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <[hidden email]> 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

<a href="https://jenkins.io/sigs/cloud-native/#areas-for-improvement" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;">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 <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 <a href="https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3e6edab7-ea9f-42aa-90ab-c07ac8eb9dde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

Rick
I'm in

On Monday, January 21, 2019 at 6:44:11 AM UTC+8, [hidden email] 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" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 20, 2019, at 2:22 AM, Oleg Nenashev <[hidden email]> wrote:

Hi all,

After reading the proposal from RunzeXia in <a href="https://github.com/jenkins-infra/jenkins.io/pull/2055" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2055\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFmlVi2FwbvVQzVjncAmTlonAVQtQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fjenkins.io%2Fpull%2F2055\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFmlVi2FwbvVQzVjncAmTlonAVQtQ&#39;;return true;">this pull request, I think that the official Kubernetes Operator could be built on the top of the <a href="https://github.com/jenkinsci/custom-war-packager" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fcustom-war-packager\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGZ8p07iUV2ifEZVyat2n2EvCQjpQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fcustom-war-packager\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGZ8p07iUV2ifEZVyat2n2EvCQjpQ&#39;;return true;">Custom WAR/Docker Packager which already supports managing Jenkins versions, plugins and configurations via JCasC/Groovy (<a href="https://jenkins.io/blog/2018/10/16/custom-war-packager/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fblog%2F2018%2F10%2F16%2Fcustom-war-packager%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE3mNTw0eCWV2XhKAtnFzZGSvQlKg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fblog%2F2018%2F10%2F16%2Fcustom-war-packager%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE3mNTw0eCWV2XhKAtnFzZGSvQlKg&#39;;return true;">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 <a href="https://github.com/jenkinsci/jep" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHu9RZgOvMHcAd6kq-X5ZTU9uJTNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjep\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHu9RZgOvMHcAd6kq-X5ZTU9uJTNw&#39;;return true;">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, marky.r...@<a href="http://gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://gmail.com&#39;;return true;" onclick="this.href=&#39;http://gmail.com&#39;;return true;">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" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 15, 2019, at 8:38 AM, Jesse Glick <[hidden email]> wrote:

On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <[hidden email]> 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

<a href="https://jenkins.io/sigs/cloud-native/#areas-for-improvement" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fsigs%2Fcloud-native%2F%23areas-for-improvement\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH8hPH-ZW89lICk7alunQLaoQFNwg&#39;;return true;">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 <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr24Y6Vpq2YnUXT3BubDuuzpTXmw-fCgoeeVpM0PTMx%3Dsw%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 <a href="https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/9ea9a62b-382d-48c0-8ed0-28e930198086%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7ad5a2bf-067c-4ef8-9149-ad9207f25af6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

nicolas de loof-2
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 <[hidden email]> a écrit :
I'm in

On Monday, January 21, 2019 at 6:44:11 AM UTC+8, [hidden email] 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" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 20, 2019, at 2:22 AM, Oleg Nenashev <[hidden email]> 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, 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" : “[hidden email]",
        "team" : "jackson5“
    }
}

On Jan 15, 2019, at 8:38 AM, Jesse Glick <[hidden email]> wrote:

On Tue, Jan 15, 2019 at 7:56 AM 夏润泽 <[hidden email]> 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 [hidden email].
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 [hidden email].
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7ad5a2bf-067c-4ef8-9149-ad9207f25af6%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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

夏润泽-2
I have checked this repo, I think some of the function points are coincident, such as the integration of CasC.
But the final features may not be consistent, perhaps we should discuss their ideas about  the operator?
On Monday, January 21, 2019 at 2:34:01 PM UTC+8, nicolas de loof wrote:
Have you checked overlap with <a href="https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FVirtusLab%2Fjenkins-operator&amp;sa=D&amp;sntz=1&amp;usg=AFQjCNE9Xi-CmIfmjoDjA9HzOXdEkZz9_w" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FVirtusLab%2Fjenkins-operator\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE9Xi-CmIfmjoDjA9HzOXdEkZz9_w&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FVirtusLab%2Fjenkins-operator\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE9Xi-CmIfmjoDjA9HzOXdEkZz9_w&#39;;return true;">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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b954b9f4-fdd8-4865-b869-3ecee8aff880%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: jenkins official kubernetes operator

Tomasz Sęk
In reply to this post by 夏润泽-2
Hi all,

My name is Tomasz Sęk and I work in Virtuslab company as a senior DevOps engineer. I'm the main maintainer of https://github.com/VirtusLab/jenkins-operator project.
We've been provide Jenkins for customers(programmer teams) in our custom Kubernetes distribution for two years. 
As we discussed with Nicolas I would like to describe our implementation and talk about plans, and possible improvements we can make.

Architecture:
- language golang 1.10(Kubernetes uses it)
- we use operator-sdk
- try to not use custom docker images and support jenkins/jenkins:lts, of course user can define own docker master image
- use plugins to manage Jenkins(jcasc, job backups - to store on AWS S3 we use aws-java-sdk ...)
- every single plugin and it's depended plugins have to be installed with specific version, auto update have to be turn off(we had many situations where after plugins update Jenkins can't build any job)
- use Kubernetes plugin to build jobs(every new job spins up new pod in Kubernetes, you can scale yours build through Kubernetes)
- make backup of jobs history before Jenkins master pod deletion and restore it in new pod
- use job-dsl-plugin for managing jobs definitions
- encapsulate configuration of Jenkins in jobs(it make errors visible to users)

Plans:
- implement more backup mechanisms(PVC, Azure Blob Storage, GCP)
- TLS/SSL for Jenkins Master(to secure connection jenkins-operator->jenkins master API)
- improve JNLP agent to handle Jenkins master pod restarts

Improvements:
In current solution only one Jenkins master can be run at the same time, the old goes down then the new one can be created.
I thought we can spin up new Jenkins master pod when the old one have to be killed and then switch traffic to the new one.

Feel free to ask questions. I will prepare JEP draft.

Best regards,
Tomasz

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/fd5679b9-e782-4a61-898f-5fc795ca140c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
123