New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

147 views
Skip to first unread message

Akram Ben Aissi

unread,
Nov 10, 2020, 12:32:57 PM11/10/20
to jenkin...@googlegroups.com, Jawed Khelil, Siamak Sadeghianfar, Vibhav Bobade, Jitendar Singh
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





--

AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: +33.6.31.57.08.60       T: @akrambenaissi

E: aben...@redhat.com    #: Akram      


Gavin Mogan

unread,
Nov 10, 2020, 12:44:15 PM11/10/20
to Jenkins Developers, Jawed Khelil, Siamak Sadeghianfar, Vibhav Bobade, Jitendar Singh
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


--
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%40mail.gmail.com.

Oleg Nenashev

unread,
Nov 11, 2020, 2:18:43 AM11/11/20
to Jenkins Developers
It is me who asked for a developer mailing list thread. There is no problem with the hosting itself, I can create repos when there is a consensus. I asked for a more public process (not so many contributors watch HOSTING), because it is a follow-up to the Jenkins Kubernetes Operator: Open Governance Proposal that got stuck due to the lack of public response from Virtus Lab. As discussed at the governance board meetings in August and October, hosting a new operator is an alternative to getting the upstream https://github.com/jenkinsci/kubernetes-operator unblocked. So this request basically applies an alternate plan.
 
I am +1 for hosting a new operator, because I see no clear way for unblocking https://github.com/jenkinsci/kubernetes-operator. We got some private response from Virtus Lab to the Jenkins Board on Oct 16, but I have no permission to share it. Although this response is somewhat promising, it does not immediately unblocks contributions to the repository. There is no public response from Virtus Lab as they intended to do, and there is little activity in the repository. Although there is a declared intent to introduce changes in November, I am not sure it is . Having an alternate repository is how we could unblock contributors while we keep communicating with Virtus Lab and trying to unlock the upstream.

No strong opinion about naming

Best regards,
Oleg

Oleg Nenashev

unread,
Nov 11, 2020, 3:38:30 PM11/11/20
to Jenkins Developers
Hi all, any additional feedback about the hosting request?

Thanks in advance,
Oleg

Mark Waite

unread,
Nov 11, 2020, 3:41:38 PM11/11/20
to jenkinsci-dev

Ullrich Hafner

unread,
Nov 11, 2020, 3:52:11 PM11/11/20
to Jenkins Developers

slide

unread,
Nov 11, 2020, 4:23:05 PM11/11/20
to Jenkins Developers
+1

Oleg Nenashev

unread,
Nov 11, 2020, 5:20:41 PM11/11/20
to JenkinsCI Developers
I will create the new repository tomorrow if there is no negative feedback in this thread

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/oAWCXDbgcG4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cbf5ca2a-d09e-4e13-8044-1539bb2098e9n%40googlegroups.com.

Victor Martinez

unread,
Nov 11, 2020, 6:32:16 PM11/11/20
to Jenkins Developers
+1 That's brilliant! 

Slide

unread,
Nov 11, 2020, 8:03:01 PM11/11/20
to Jenkins Developer List
Do we want them to go through the normal hosting process?

Oleg Nenashev

unread,
Nov 12, 2020, 6:07:29 AM11/12/20
to Jenkins Developers
> Do we want them to go through the normal hosting process?

Since this is a request for a new repo creation (not a fork/move) && there is a consensus here, I do not see a particular need. A HOSTING ticket would be useful to understand the desired permissions, but we can figure it out as we go.

Right now only Akram has access.



Daniel Beck

unread,
Nov 12, 2020, 7:34:45 AM11/12/20
to JenkinsCI Developers
On Thu, Nov 12, 2020 at 12:07 PM Oleg Nenashev <o.v.ne...@gmail.com> wrote:
Since this is a request for a new repo creation (not a fork/move) && there is a consensus here, I do not see a particular need. A HOSTING ticket would be useful to understand the desired permissions, but we can figure it out as we go.

So are you saying that anyone can circumvent hosting processes by asking for a new repo "to push existing code"? Because that's what I'm hearing.

(FWIW we stopped doing this several years ago because we customize repos in the ircbot code, set up permissions – which you've already noticed is a problem now – and apply some other custom defaults. Plus having empty repos around that never got populated for months or years is also not great.) 

Oleg Nenashev

unread,
Nov 12, 2020, 8:22:42 AM11/12/20
to JenkinsCI Developers
Hi Daniel,

I agree that I bypassed a few steps in the Hosting process for this repo.
I am happy to discuss why in another channel, but please be sure it is not about "anyone".
If you or other Hosting team members want me to revert my actions, I will do so.

Best regards,
Oleg


--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/oAWCXDbgcG4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.

Oleg Nenashev

unread,
Dec 1, 2020, 4:15:55 AM12/1/20
to Jenkins Developers
Hi Akram,

I have noticed that the repo was renamed to https://github.com/jenkinsci/jenkins-automation-operator . We briefly discussed the potential renaming at the previous Cloud Native SIG meeting, but AFAICT there was no finalized decision.  Although the maintainers have admin permissions and can rename repos, naming agreements are a part of the hosting process.  So it would be great to agree on the name here.

The code has not been pushed there yet as well. I highlighted this issue to Vibhav at the last Cloud Native SIG meeting on Nov 20, and IIUC there was a plan to move the code to the new upstream shortly. 

P.S: It highlights the importance of the formal hosting process. Although it does not prevent from all issues, it helps to ensure that everyone is on the same page.

BR, Oleg

aben...@redhat.com

unread,
Dec 1, 2020, 4:27:11 AM12/1/20
to Jenkins Developers
Hi Oleg et all,

sorry, this was a mistake. We were thinking of another name but despite not reaching a consensus there was a misunderstanding and one of the team member renamed it.
I just reverted the name to the original one and notified all the team members.

aben...@redhat.com

unread,
Dec 3, 2020, 1:00:48 PM12/3/20
to Jenkins Developers
Hi Jenkinsers,

after discussions, our team has agreed in using a different name instead of simple-jenkins-operator which may be too restrictive.

We conducted a poll internally and it seems that we have a consensus around "jenkins-automation-operator" .
Could you please, folks, consider that change and give any feedback?

After that, please let us know about the change. At the moment, we haven't pushed any code yet, and we have still our code base in a public github repository.

Greetings
Akram




Oleg Nenashev

unread,
Dec 11, 2020, 11:22:23 AM12/11/20
to Jenkins Developers
Anyone? Personally I am not against renaming. 
"simple-jenkins-operator" and "jenkins-automation-operator" are approximately the same in terms of potential confusion


Marky Jackson

unread,
Dec 11, 2020, 11:23:49 AM12/11/20
to 'Olblak' via Jenkins Developers
I am not against renaming

-- 

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/5c5bcd45-3a09-4591-8e25-2b14c86a3afdn%40googlegroups.com.

Gavin Mogan

unread,
Dec 11, 2020, 12:25:11 PM12/11/20
to Jenkins Developers
from a SEO type point of view, it doesn't really tell me anything about what it does, but if the <name> field in the pom is more detailed it'll probably be fine to do whatever

aben...@redhat.com

unread,
Dec 15, 2020, 2:45:27 AM12/15/20
to Jenkins Developers
Thank you for these feedbacks. So, we can go ahead an operate the naming right?

Oleg Nenashev

unread,
Dec 15, 2020, 3:46:46 AM12/15/20
to JenkinsCI Developers
Yes, please go ahead. I think getting code there and development going is more important at the moment.
Since VirtusLab is now active in the original repo again, it would be great if both repositories clearly distinguish projects on the README pages and docsites.




You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/oAWCXDbgcG4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/00ed894c-bc9c-4e60-b926-e66bdab4b00en%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages