|
Re: Platforms definition whitepaper ready for review
Hey all, this far I've been an observer and I'm looking forward to participating in meetings going forward.
Just want to confirm the date for Tue the 17th, as I had 2nd and 4th Tuesdays in my
Hey all, this far I've been an observer and I'm looking forward to participating in meetings going forward.
Just want to confirm the date for Tue the 17th, as I had 2nd and 4th Tuesdays in my
|
By
Friel
·
#314
·
|
|
Re: Platforms definition whitepaper ready for review
Hi Aaron,
Thanks for the question. This is an extra "working" meeting specifically to focus on the whitepaper *content*. The regularly scheduled meeting couldn't go that deep on hot topics and seeking
Hi Aaron,
Thanks for the question. This is an extra "working" meeting specifically to focus on the whitepaper *content*. The regularly scheduled meeting couldn't go that deep on hot topics and seeking
|
By
Josh Gavant
·
#313
·
|
|
Re: Platforms definition whitepaper ready for review
Hi folks - we'll be reviewing hot topics related to the whitepaper's content and seeking owners for section reviews in a meeting this Tuesday Jan. 17 @ 1600 UTC.
Here's the meeting event page to add
Hi folks - we'll be reviewing hot topics related to the whitepaper's content and seeking owners for section reviews in a meeting this Tuesday Jan. 17 @ 1600 UTC.
Here's the meeting event page to add
|
By
Josh Gavant
·
#312
·
|
|
Re: Platforms definition whitepaper ready for review
this is actually a really nice validation of the initial assumptions of CNCF, that an industry platform could emerge from collections of loosely coupled cloud native tools.
this is actually a really nice validation of the initial assumptions of CNCF, that an industry platform could emerge from collections of loosely coupled cloud native tools.
|
By
alexis richardson
·
#311
·
|
|
Platforms definition whitepaper ready for review
Hi TAG and happy new year! WG Platforms finished 2022 by building the whitepaper described in https://github.com/cncf/tag-app-delivery/issues/246 to define what a cloud-native platform is, why it's
Hi TAG and happy new year! WG Platforms finished 2022 by building the whitepaper described in https://github.com/cncf/tag-app-delivery/issues/246 to define what a cloud-native platform is, why it's
|
By
Josh Gavant
·
#310
·
|
|
[gitops-wg] 📢 GitOpsCon relocates to Open Source Summit
Hi everyone!
You may have heard the news: GitOpsCon is joining forces with CdCon and moving from KubeCon + CloudNativeCon to Open Source Summit starting in 2023!
Check out this blog post which
Hi everyone!
You may have heard the news: GitOpsCon is joining forces with CdCon and moving from KubeCon + CloudNativeCon to Open Source Summit starting in 2023!
Check out this blog post which
|
By
Scott Rigby
·
#309
·
|
|
Re: [gitops-wg] GitOps & Environmental Sustainability Subgroup meeting
Thanks Niklas, Niki, and everyone involved in this subgroup 🌎
--
Scott Rigby
Developer Experience, Weaveworks
Thanks Niklas, Niki, and everyone involved in this subgroup 🌎
--
Scott Rigby
Developer Experience, Weaveworks
|
By
Scott Rigby
·
#308
·
|
|
[gitops-wg] GitOps & Environmental Sustainability Subgroup meeting
Hey everyone,
for the first GitOps & Environmental Sustainability Subgroup 🌱 meeting Niki created an issue in the project's repository. We want to meet Tuesday 15th November at 6pm CET/12pm ET/9am
Hey everyone,
for the first GitOps & Environmental Sustainability Subgroup 🌱 meeting Niki created an issue in the project's repository. We want to meet Tuesday 15th November at 6pm CET/12pm ET/9am
|
By
Niklas
·
#307
·
|
|
[gitops-wg] Maintainer and Governance updates
Hello everyone!
Please see this PR which updates OpenGitOps governance to Move top level power to maintainers #123.
While there are overlapping members, once that PR is merged, the OpenGitOps project
Hello everyone!
Please see this PR which updates OpenGitOps governance to Move top level power to maintainers #123.
While there are overlapping members, once that PR is merged, the OpenGitOps project
|
By
Scott Rigby
·
#306
·
|
|
Today's TAG App Delivery meeting
Who is planning to join the meeting today? If you have a agenda item, feel to add it for today.
// AloisThis email may contain confidential information. If it appears this message was sent to you
Who is planning to join the meeting today? If you have a agenda item, feel to add it for today.
// AloisThis email may contain confidential information. If it appears this message was sent to you
|
By
Reitbauer, Alois
·
#305
·
|
|
New Maintainers OpenGitOps Working Group
For transparency, New Maintainers have been nominated for the OpenGitOps Working Group
https://github.com/open-gitops/project/pull/107
Christian Hernandez
(626) 502-8310
Developer Experience and
For transparency, New Maintainers have been nominated for the OpenGitOps Working Group
https://github.com/open-gitops/project/pull/107
Christian Hernandez
(626) 502-8310
Developer Experience and
|
By
Christian Hernandez
·
#304
·
|
|
Re: [gitops-wg] Improving GitOps usability
BTW, on GUIs being necessary:
A GUI isn't strictly necessary, but this makes it Possible. It also makes other types of automation possible.
It eliminates the requirement of manual editing of
BTW, on GUIs being necessary:
A GUI isn't strictly necessary, but this makes it Possible. It also makes other types of automation possible.
It eliminates the requirement of manual editing of
|
By
Brian Grant
·
#303
·
|
|
Re: [gitops-wg] Improving GitOps usability
Will watch video for sure.
To be clear, you don't have to use git, any object store that's versioned will do. If git is in the way, use something that works and is versioned.
Also, I think it was Dan
Will watch video for sure.
To be clear, you don't have to use git, any object store that's versioned will do. If git is in the way, use something that works and is versioned.
Also, I think it was Dan
|
By
Chris Short <cbshort@...>
·
#302
·
|
|
Re: [gitops-wg] Improving GitOps usability
I tried to respond to this message yesterday, but the reply didn't go through.
The similar twitter thread is here:
https://twitter.com/joshugav/status/1529208719594110979
There are a number of other
I tried to respond to this message yesterday, but the reply didn't go through.
The similar twitter thread is here:
https://twitter.com/joshugav/status/1529208719594110979
There are a number of other
|
By
Brian Grant
·
#301
·
|
|
Re: [gitops-wg] Improving GitOps usability
The Backstage plugin is in its early stages. The review/approval flow needs to have at least diffs added. Some of that functionality can be seen in our earlier
The Backstage plugin is in its early stages. The review/approval flow needs to have at least diffs added. Some of that functionality can be seen in our earlier
|
By
Brian Grant
·
#300
·
|
|
Re: [gitops-wg] Improving GitOps usability
Thank you for bringing this to the group. I legit wish I had this when I was working in the Duke Health system. Would've made our lives much easier.
I can see extensive use of this being made in
Thank you for bringing this to the group. I legit wish I had this when I was working in the Duke Health system. Would've made our lives much easier.
I can see extensive use of this being made in
|
By
Chris Short
·
#299
·
|
|
Re: [gitops-wg] Improving GitOps usability
Flux can write back to Git, but only for container image update automation. Flux image-reflector-controller scans container registries to find new versions, then Flux image-automation-controller
Flux can write back to Git, but only for container image update automation. Flux image-reflector-controller scans container registries to find new versions, then Flux image-automation-controller
|
By
Stefan Prodan
·
#298
·
|
|
Re: [gitops-wg] Improving GitOps usability
Thanks for sharing Brian. The most significant bit to consider IMO is that kpt enables syncing back to the git repo, whereas the likes of Flux and ArgoCD are one-way only (AFAIK) - the ArgoCD and Flux
Thanks for sharing Brian. The most significant bit to consider IMO is that kpt enables syncing back to the git repo, whereas the likes of Flux and ArgoCD are one-way only (AFAIK) - the ArgoCD and Flux
|
By
Josh Gavant
·
#297
·
|
|
[gitops-wg] Improving GitOps usability
Hi. It was suggested to me that this topic may be of interest to the GitOps WG. I'd be happy to come discuss it during a meeting, or on the mailing list.
We created a WYSIWYG GUI experience layered
Hi. It was suggested to me that this topic may be of interest to the GitOps WG. I'd be happy to come discuss it during a meeting, or on the mailing list.
We created a WYSIWYG GUI experience layered
|
By
Brian Grant
·
#296
·
|
|
[gitops-wg] Welcome Chris Short as co-chair 🎉
Hi everyone!
This is a follow-up to "[gitops-wg] Co-Chair voting" on this list.
Chris Short has been voted in as GitOps WG co-chair, along with Dan Garfield and myself. 🎉
See CHAIRS.md for the list
Hi everyone!
This is a follow-up to "[gitops-wg] Co-Chair voting" on this list.
Chris Short has been voted in as GitOps WG co-chair, along with Dan Garfield and myself. 🎉
See CHAIRS.md for the list
|
By
Scott Rigby
·
#295
·
|