Nomination for co-chair for the GitOps Working Group
Lee, Edward <Edward_Lee@...>
I would like to nominate Dan Garfield for the co-chair position for the GitOps Working Group.
Dan Garfield is the Chief Open Source Officer at Codefresh. His role is unique because it is focused on enabling open source, community, and related ecosystems. Codefresh is already heavily involved with the GitOps working group as well as the Argo Project.
Dan's background as an engineer, marketer, and technology leader as well as
his energy and dedication make him an ideal choice to represent the community at this formative time for the GitOps working group.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Nomination for GitOps WG co-chair
Cornelia Davis
Hello all. I would like to nominate our industry and my Weaveworks colleague, Scott Rigby, to be a co-chair of the GitOps Working Group. I've asked Scott to share a bit more of his background with all of you - see below. From me personally, I must share how delighted I am that Scott is willing to step up and serve in this capacity. I've had the opportunity to work quite closely with Scott and have seen his dedication to the technology user, whether it is in the helm community, helping users migrate from flux v1 to v2, or even in what this propeller-head sees as less technical (but probably is more tech than I give it credit for ;-). I place emphasis on the term "user" because I believe it exemplifies the spirit of community that permeates OSS. You can see in Scott's self-intro that this is nothing new for him - he is OSS to the core. Thank you all for your consideration. Cornelia ------------------- From Scott: I'm a Brooklyn based interdisciplinary artist and open source software engineer, co-developing experimental cultural projects and emerging technologies. I co-founded the Basekamp art and research group in 1998 and the massively collaborative Plausible Artworlds international network. In technology I enjoy helping develop open source software that anyone can use, these days focusing most of that attention on projects in the cloud native landscape, including Flux and Helm – as a community maintainer and project org maintainer respectively. In daily decisions large or small, I try to help make the world a better place for everyone. My path to GitOps is a fun but familiar one. In the mid 2000s I found my collaborative conflict resolution experience and systems thinking from cultural projects also applied to open source software, leading me directly into DevOps as a way to bridge otherwise siloed development and operations teams. My focus began shifting from primarily applications to software that powers systems, such as Kubernetes. As a human operator in subsequent years, and as the rough edges in CI and other scripted automation for delivery became harder to ignore, I wondered why the application lifecycle process couldn't be as declarative as the underlying infra now was. GitOps became a natural next area of focus, prompting my move to the Weaveworks DX team, and contributing whatever thinking, communication or legwork needed for projects like the GitOps Working Group. With the interest and enthusiasm from such a broad range of parties, I'm excited to see where GitOps, as a wider interconnected movement, is able to go. Cornelia Davis CTO, Weaveworks @cdavisafc +1 805 452 8941
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
GitOps Working Group co-chair nomination
Hi all, I would like to nominate Christian Hernandez as a GitOps WG co-chair. Christian has demonstrated a wide knowledge of GitOps and helps others embrace GitOps practices and tooling. I asked Christian for his bio for everyone: "Christian Hernandez has been in IT for over 16 years with experience in system administration, tech support, development, enterprise architecture, and management. He was the second OpenShift Field Engineer in North America hired, and has been involved with Kubernetes since its inception, and experienced the rewrite of OpenShift that took place. He's been focused on GitOps for the past two years and is passionate about bringing it to the forefront. In his free time, he loves to play guitar and is a bit of a wine snob." Thank you,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
GitOps Working Group Co-chair self nomination
Leonardo Murillo <leonardo@...>
Hello Community, I'd like to hereby self-nominate for Co-chair for the GitOps Working Group. My name is Leonardo Murillo, I'm Founder of Cloud Native Architects and CTO at Qwinix Technologies. Have over 20 years of experience in the IT industry, 10 of which have been mostly focused on cloud. I'm a DevOps Institute Ambassador and CNCF Speaker. I have ample experience managing teams and delivering technology products, all experience that I believe very well translates to the responsibilities of the co-chair role, additionally my current professional roles gives me a lot of freedom in terms of time management and autonomy in terms of participation. Thanks in advance for the consideration and please don't hesitate to request any further information. Leo
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Calling for nominations for GitOps Working Group (WG) Co-chairs
Cornelia Davis
Hello community. As I believe you are aware, the GitOps Working Group was formed late last year with the goal "to provide companies and individuals with the skills, knowledge and competency to implement GitOps tooling and methodologies which simplify the operation and management of infrastructure and cloud native applications" and care for the GitOps Working group sandbox project. While we've already gone to work on a number of initiatives, the time has come for us to elect co-chairs for the working group. While co-chairs are responsible for ensuring that meetings and other activities are conducted and progress continues to be made against the WG agenda, this role is not purely administrative. Co-chairs will have GitOps domain knowledge and will engage deeply in the work being done. That said, chairs are not expected to do all of the work of the WG - this is encouraged of all members and expected from those who have volunteered onto various workstreams. The time commitment for a co-chair will vary from week to week, but will likely average out to be roughly a half day's work per week. With this email I open the call for nominations for the co-chair positions for the GitOps Working Group. Details:
I will cross post this note to the #wg-gitops slack channel as well. Thank you all. Cornelia -- Cornelia Davis CTO, Weaveworks @cdavisafc +1 805 452 8941
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Operator Working Group chair(s)
Reitbauer, Alois
Ok, we should move forward with the chairs for the Operator WG. It seems that we have three people nominated which will already provide excellent contributions. I am all for make the change in chairs and have the team of
Act as co-chairs for the group.
If anybody disagrees please state your concerns. Please also show your support for the three of them.
// Alois
From:
Schuetz, Thomas <thomas.schuetz@...> Hello!
Thank you for the recommendations, really appreciate it. As she made a lot of contributions in the last few weeks and drives the progress in the working group, I recommend Jennifer Strejevich to become the third chair of the working group.
Thank you, Thomas Schuetz
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Invitation: SIG App-Delivery Operator Working Group @ Monthly from 9am to 9:50am on the second Wednesday (PST) (cncf-sig-app-delivery@lists.cncf.io)
Amye Scavarda Perrin
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Operator Working Group chair(s)
Thomas Schuetz
Hello!
Thank you for the recommendations, really appreciate it. As she made a lot of contributions in the last few weeks and drives the progress in the working group, I recommend Jennifer Strejevich to become the third chair of the working group.
Thank you,
Thomas Schuetz
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received
it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4020 Linz, Austria, Am Fünfundzwanziger Turm 20
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Operator Working Group chair(s)
Reitbauer, Alois
Having seen both of them drive this forward I think this is good idea and values their commitment. I would still ask whether there are other who are interested in chairing the working group. Just want to give everybody a chance to speak up.
// Alois
From: <cncf-sig-app-delivery@...> on behalf of "Marc Campbell via lists.cncf.io" <marc=replicated.com@...>
Hi everyone,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Invitation: SIG App-Delivery Operator Working Group - Security @ Thu Dec 17, 2020 9am - 9:50am (PST) (cncf-sig-app-delivery@lists.cncf.io)
Amye Scavarda Perrin
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Operator WG - Request for review
Omer Kahani
Hi everyone,
Just a reminder, this is the last day for the review, This is the document https://docs.google.com/document/d/1daXHyR2yG5ArjO1PO83v4a0fmLCLo2kYNT3TwGZksng/edit?usp=sharing The sections in this review cycle have: "Ready for Review - Current" in the headline.
Also, we have a Working Group meeting today at 17:00 GMT at: https://zoom.us/my/cncfsigappdelivery?pwd=R0RJMkRzQ1ZjcmE0WERGcTJTOEVyUT09
Thanks, Omer
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Operator WG - Survey
Thomas Schuetz
Hello!
To get some additional insights about problems and the usage of operators "in the real world", we created a survey. If you've got 3 mins, please fill it out and/or share the link. The insights gathered might be very useful for our whitepaper. The survey is available here: https://bit.ly/3gjHKOJ. Thanks in advance for your help! - Thomas
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Operator Working Group chair(s)
Marc Campbell
Hi everyone,
When the App Delivery Operator working group was formed, Gerred Dillon and I volunteered as co-chairs to lead the discussion and drive toward a draft of an operator definition. The meeting cadence and activity slowed down considerable over the summer. Recently, Thomas Schuetz and Omer Kahani have stepped up and taken over the management of this WG and have been leading the efforts to get a draft of the operator definition together. I'm recommending that Thomas and Omer become the new chairs of the Operator working group, replacing Gerred Dillon and myself. The recent progress in advancing the definition has been led by Omer and Thomas and they've graciously offered to assume the role and continue leading this working group. Thank you, Marc Campbell marc@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Operator WG - Request for review
Thomas Schuetz
Hello everyone!
Some sections of the Operator Document are about to be finished from a content-perspective. These sections are marked with "Ready for Review" and it would be very nice if you could add your comments/suggestions and additions to these sections until December 9th, 2020. Additionally, please review the structure of the document (from page 1 to 9 - until the break) and propose things we should add or change. In the next SIG meeting (December 2nd), we will present the current state of the document and how we would like to proceed. If you'd like to contribute to the document and participate on our (currently weekly) meetings, just reach out to me. - Thomas
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Working Group on GitOps proposed - Please declare your interest
alexis richardson
folks - in addition to updating the WG charter doc, please update the github page if you want to contribute to or potentially maintain the docs - https://github.com/fluxcd/gitops-working-group note that an application for CNCF Sandbox is in process, and (I hope) will not take too long On Mon, Nov 23, 2020 at 11:42 AM Reitbauer, Alois via lists.cncf.io <alois.reitbauer=dynatrace.com@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Working Group on GitOps proposed - Please declare your interest
Reitbauer, Alois
Hello everyone,
as you might have already heard the CNCF and SIG App Delivery was approached by to create a working group around GitOps. As GitOps is becoming a more central part of cloud-native application delivery this looks like a good fit.
If you are interested in this, please declare so in the working Google. Also feel free to provide your input (everyone should have comment rights) - https://docs.google.com/document/d/11EZfvB2FFI837nMmArnyv-wizsIJvc-4_xdgfoUXF4o/edit?ts=5fb68361#heading=h.tynxy1m53ozs
I expect the team to present more details during our next SIG call. In the meantime, please share your thoughts on this thread and provide input to the working group document.
// Alois
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [cncf-toc] Cloud native "reference/demo" application
Reitbauer, Alois
Hello everyone,
We have some initial progress around a demo application. Things are very rough around the edges right now but you can find a first version here: https://github.com/cncf/podtato-head
Right now this is a single, simple service. Obviously this will be extended in the future.
However, already today there is a good number of delivery tool examples that are showcased. \
If you are interested in contribution please let me so I can coordinate next steps.
// Alois
From: <cncf-toc@...> on behalf of "Reitbauer, Alois via lists.cncf.io" <alois.reitbauer=dynatrace.com@...>
I am using this list as it most likely reaches the widest audience in the CNCF.
In recent discussions in the app delivery SIG we came to the conclusion that a reference application would make sense that a) has most of the characteristics of real world applications b) can be used to demonstrate good practices and also how certain CNCF tools can be used to solve common problems.
Having a reference application – or multiple - when we are talking about app delivery makes a lot of sense.
Looking at the most widely used applications you undoubtedly end up with Hipstershop, Sockshop or one of their variants. While these apps are nice to demo what a cloud-native application can look like, they also miss key characteristics like stateful workloads, third party integrations, secrets, multi-stage configurations, databases, …. .
I also assume that many CNCF project have their own demo applications to demonstrate their capabilities.
Alexis made the proposal to fork one of more of the demo applications over in a CNCF demo-apps org. This, however, only makes sense if there is active development on this demo. It might be even better to have the demo app together with the development community behind actively participate in the CNCF – by e.g. donating the app as a sandbox project.
So, to get more concrete, a couple of questions to get feedback on:
Obviously, as this idea matures this need direction and discussion in the TOC. I am using this email to kick off the discussion and collect some first data points.
// Alois The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4020 Linz, Austria, Am Fünfundzwanziger Turm 20
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Operator WG Update
Thomas Schuetz
Hello,
as discussed in the meeting, we did some work on the Operator Document and are trying to make some progress. At the moment we focus on the essential things of the document (so what an operator is, but not what it not is), so we're keeping things as similar technologies out of the discussion at the moment. Call to action:
- Thomas
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Highlights from today's meeting
Reitbauer, Alois
For reference this was the continuous deliver radar done a while back by the CNCF: https://radar.cncf.io/2020-06-continuous-delivery
From: <cncf-sig-app-delivery@...> on behalf of "Lei Zhang via lists.cncf.io" <resouer=gmail.com@...>
Thanks Alois! The "podtato" is super awesome!
Btw, based on today's discussion, the SIG app delivery is also thinking for CNCF Radar for application delivery and management. This should be a informative approach to let the community know better the current status of the projects in app delivery area.
Though I personally don't want to restrict CNCF Radar to end user community only, since I can see the vendors can also bring many insightful feedback on the adoption of certain projects from different angles.
Feel free to let us know your thought on this iterm and we are egar to make it happen!
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Highlights from today's meeting
Lei Zhang
Thanks Alois! The "podtato" is super awesome!
Btw, based on today's discussion, the SIG app delivery is also thinking for CNCF Radar for application delivery and management. This should be a informative approach to let the community know better the current status of the projects in app delivery area.
Though I personally don't want to restrict CNCF Radar to end user community only, since I can see the vendors can also bring many insightful feedback on the adoption of certain projects from different angles.
Feel free to let us know your thought on this iterm and we are egar to make it happen!
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|