Fork me on GitHub
Ann Perry - IT Revolution11:05:47

📣 Let's get ready to welcome @suzette.johnson5 and @robinyeman!

Ciaran Byrne11:05:47

@suzette.johnson5 and @robinyeman.. Yep, I love the way we can accurately predict the future via an Integrated Master Schedule 😬

Chris Gallivan, Stellantis, Value Stream Architect11:05:51

yet the requirements change request number in the thousands

Ciaran Byrne11:05:13

But that's OK, we'll still keep to the IMS schedule

👍 1
Arnab Nandi12:05:03

Involve technical people in org design! Love it, and miss it every time a reorg happens :-(

Chris Shuknecht12:05:24

I definitely see lack of a common language a large challenge on a daily basis. Attempts at creating central definition docs haven't helped as much as hoped.

Dave Reed (bp Product Manager)12:05:20

and compounded when you're a very technical company with lots of TLA's

👍 1
Suzette Johnson12:05:30

Anyone else involved in value stream mapping?

👍 2
Jim Tranquill12:05:36

@suzette.johnson5 do you see your gov't customers asking for Value Stream Management, or is it a concept that they are still trying to understand?

Suzette Johnson12:05:28

It is definitely an area that is growing rapidly in the agile/devops world

👍 1
James Simon12:05:02

We aren't government. I think what we can say is that seeing value stream mapped visually always shocks our teams and leaders. Even if they already knew the overall results.

Suzette Johnson12:05:05

It is not an easy undertaking with these complex systems

James Simon12:05:34

I think my partner Chris stumbled on a great tool for making it a little easier

Suzette Johnson12:05:38

it is sometimes difficult to allocate the time

Dave Reed (bp Product Manager)12:05:02

needs buy in from the business to allow us access to the people in the know

James Simon12:05:11

Oh that is true

Dave Reed (bp Product Manager)12:05:20

can be tricky in big orgs - certainly something I'm struggling with

James Simon12:05:23

Though we just started scheduling time with teams

James Simon12:05:32

Surprisingly, that has worked up to now

Dave Reed (bp Product Manager)12:05:53

Thats excellent, starting with smaller teams?

Chris Gallivan, Stellantis, Value Stream Architect12:05:09

it's funny, but these silos actually like talking to eachother

James Simon12:05:54

Yeah, we are isolating teams within our orgs and doing the mapping with them

Dave Reed (bp Product Manager)12:05:17

I've found as they're specialists they love to expand on their area. Just getting enough time with them, as well as your own time - knowing how far you need to map the stream

James Simon12:05:31

It can be difficult, especially in a delivery obsessed org

💯 1
Chris Gallivan, Stellantis, Value Stream Architect12:05:47

complicated branching and variant management are one of the pain points

Chris Shuknecht12:05:47

agreed. I like that behavior map visual

🙌 1
Katharine Chajka (Tasktop)12:05:13

how to access your white paper? sorry joined late

Ciaran Byrne12:05:21

Thank you @suzette.johnson5 and @robinyeman 👏

Chris Shuknecht12:05:29

Is there a link to the draft paper mentioned? ( I might have missed it)

Craig Cook - IBM12:05:30

I saw all of these barriers in my last role as a DevOps Coach. I'd be happy to learn more about your paper.

Arnab Nandi12:05:36

That was great, thank you @suzette.johnson5 and @robinyeman

Chris Gallivan, Stellantis, Value Stream Architect12:05:30

there are a lot of things that traditional software can bring to this space

John Willis12:05:27


👋 2
🙌 2
Ann Perry - IT Revolution12:05:46

Thank you, Suzette & Robin! And now, we're excited to have @jwillis join us!!

👋 1
Philip Day12:05:42

Anticipating high energy here

John Willis12:05:28

I do look forward to live presentations; however, virtual ain't that bad...

Philip Day12:05:41

:rain_cloud: :wind_blowing_face: where I am

John Willis12:05:16

Lake Martin AL

Nick Eggleston (free radical)12:05:07

Looks great @jwillis … best of both worlds

Daniel Cahill - Engineer - Ontario Systems12:05:43

I know this isn't the direction this talk is going, but it makes me wonder if part of the underlying solution is changing how audits work and replacing that with something faster to integrate and validate with not requiring as many manual investigations.

Andy Hinton12:05:48

We auditors definitely want to get to more automated assurance. Continuous monitoring has been a buzzword for a long time in the audit community.

Vlad Ukis12:05:23

Are there any references to look at (blog posts etc.)?

Andy Hinton12:05:12

There's quite a few articles on continuous monitoring and automated assurance or robotic process automation for audits on and but many require membership to read.

Vlad Ukis12:05:46

Thanks a lot!

Daniel Cahill - Engineer - Ontario Systems12:05:18

I think it was you who threw out the idea of having some endpoints that can spit out some of the details needed for audits to make it easier for auditors.

John Willis12:05:54

Yes.. that's why I"m a big fan of Automated Governance ... objective (digitally signed) evidence. That starts the changing of the game...

👍 5
❤️ 2
John Willis12:05:20

It's coming up in this presentation a few slides from now...

Olivier Jacques, DXC12:05:13

I was looking for the link for the papers. Here:

🔖 1
❤️ 2
Philipp Böschen, TUI, DevOps Coach, (he/him)12:05:07

Somehow I think OPA has a lot of potential for some of this, but I've always struggled to find good use cases for it

John Willis12:05:10

The paper I'm talking about is in the 2019 catalog .. Devops Automated Governance Reference Architecture paper.

John Willis12:05:50

Actually, OPA can and is mostly used as in the implementation of the defined reference architecure.

👀 1
Andy Hinton12:05:02

Very excited for the new paper

👍 1
Vlad Ukis12:05:12

Is it possible to get hold of a draft before September? 🙂

👆 1
John Willis12:05:40

Some orgs use a Risk as Code/Policy as Code as the interface and the align it with Rego/OPA as the implementation.

John Willis12:05:40

However, this architecture can and is used for more things than just K8. For example, Dataops, API Development flow, even model training.

Philipp Böschen, TUI, DevOps Coach, (he/him)12:05:46

Hmmm, I've had a few ideas around injecting it similar to the K8s admission webhooks into some of the AWS calls (reactively though) or in our pull requests for Terraform applies :thinking_face:

John Willis12:05:04

The thing is you want to decouple the attestations and gates from any specific technology. The model that works best is using the architecture as the reference and then use the specific technologies as the implementaion.

❤️ 2
Olivier Jacques, DXC12:05:50

Where do you blog @jwillis?

John Willis12:05:52

I think about this as common ingress and egress. Also, Gitops is a key part of these arechitectures.

Steve Smith12:05:44

@jwillis Why do you specifically single out GitOps there? Why isn't automated infra provisioning from version control enough? I don't see anything that GitOps offers on top of that

John Willis12:05:45

Unfortunately, I've been kind of lazy regarding blogging on this stuff. I've been taking a lot of Red Hat open source projects and putting them all together. Bill Bensing at Red Hat wrote DESORD for DOD and he has built a tool called Ploigos (also know as Software Factory). Also, Sigstore is another project that we are using for attestation (ingress).

Philipp Böschen, TUI, DevOps Coach, (he/him)12:05:15

@jwillis how do you deal with the usual deployment roles from your CI/CD system having basically sprawling admin permissions.. At some point the thing that's deploying needs to have fairly big amounts of trust 👀

John Willis12:05:26

@olivier.jacques feel free to reach out to me at <|> I'd love to chat..

Olivier Jacques, DXC12:05:03

Yes, we need to catch up for sure... Will do!

John Willis12:05:39

This is a longer answer.. However, this is why I really love Ploigos/Software factory. It is a framework for the opinionated structure of pipelines but it is unopinionated on implementaion.

John Willis14:05:06

@steve.smith agree DAG can be done w/o Gotops but it really helps for gating hooks that can't be synchronous.

John Willis12:05:33

btw.. I'm not in sales...

😍 3
John Willis12:05:13

@steve.smith Gitops for Automated Governance... Not sure what question you are asking..

Steve Smith12:05:16

Sorry I'll rephrase it Do you think automated governance can happen without GitOps? Isn't it enough to automate infra provisioning from version control?

Steve Smith12:05:58

Hmmm perhaps this is just my deep scepticism of GitOps shining through 🙂

Andreas Baernthaler - TNG Technology Consulting13:05:36

@steve.smith Are you sceptical because you don't lilke the hype or do you think there's something wrong with it?

Steve Smith13:05:07

@andreas.baernthaler That's a good question. I don't like the hype, but that's not all WeaveWorks. It's more that I don't like the idea that GitOps offers something new, when it doesn't. Automated infra provisioning with drift correction has been around since 2008, I personally saw it at LMAX in 2010 and it was mentioned in Dave and Jez's original CD book. I keep meaning to write it all down, for now I've only got

Steve Smith13:05:33

I'm a big fan of automated governance, I suspect it can be done with/without GitOps. I lack data, for now

Andreas Baernthaler - TNG Technology Consulting14:05:10

I totally agree that the concepts are not new and were nicely described in "Continuous Delivery". However, I think that tools under the GItOps umbrella just make implementing this easier. And pulling state into the target environment instead of "pushing" it from a CD tool was something that I learned from the GitOps community even though it might not have been new.

👍 1
Andreas Baernthaler - TNG Technology Consulting14:05:35

If anyone is interested in a good summary including references, I can recommend this page:

Steve Smith14:05:17

Agreed @andreas.baernthaler, I think I'd just say that CD principles and practices are universal, they apply to cloud native just like anything else. There are certainly tools that speed up cloud native support, that's for sure I'm not convinced the is necessary, YMMV

Andreas Baernthaler - TNG Technology Consulting14:05:17

Thanks @steve.smith, I appreciate your assessment.

Steve Smith14:05:17

That's OK @andreas.baernthaler, it's my own fault for not writing a "here's what I don't agree with" back in 2018, now it's hard for all of us (me included) to separate hype from reality I really do think this is separate from automated governance, which is a Good Thing regardless of the tech used 👍

Ferrix Hovi - Principal Engineering Avocado - SOK (S Group)12:05:25

Anyone write a paper about @jwillis presentations and cognitive load yet? So broad...

😂 2
John Willis12:05:22

Gitops models work well for gating.. Not all gates can be synchronous. W/Gitops you can validate a subset of attestation at each flow.

Nick Eggleston (free radical)12:05:20

Lots of items added to my research list. Thanks, @jwillis !!

John Willis12:05:20

@ferrix Team Topologies is a fantastic book on this and other great subjects.

Ferrix Hovi - Principal Engineering Avocado - SOK (S Group)12:05:53

I didn't remember them mentioning you specifically 😉

Olivier Jacques, DXC12:05:22

Thanks, very well put and instructive!

Saket Kulkarni, Coach, Capgemini (he/him)12:05:43

Thanks so much for that information-rich presentation, @jwillis!!

Philipp Böschen, TUI, DevOps Coach, (he/him)12:05:51

👏 Another firehose of information to dig through

👍 1
😅 2
Nick Eggleston (free radical)12:05:59

That’s what makes @jwillis talks so valuable 😊

💯 1
John Willis12:05:18

Feel free to reach out here, or on twitter @botchagalupe of email jwillis@redhat or <|>. I am passionate about this topic and it takes a village.

🙌 5
💯 2
John Willis12:05:04

Also, I am moderating the GRC BOF today in the BOF Room in GAther...

Ferrix Hovi - Principal Engineering Avocado - SOK (S Group)12:05:13

This is very helpful in filling a few colleagues' security learning backlogs for a while.

Daniel Cahill - Engineer - Ontario Systems12:05:18

That question of why we aren't improving with triple the budget is interesting. I know within the past year, my team has installed 6 new types of code scanners or container scanners, but haven't had the time for the teams to get their head around the pros and cons. And in a high regulated industry, I still don't feel like that scanning gets me closer to what our audits will need.

Nick Eggleston (free radical)12:05:32

Start with audit and work backwards…

John Willis12:05:24

@dacahill7 Someone yesterday mentioned this. A good approach is the bundle all your scanners into one system and give devs a sort of pre-check system. They just load the jar or container image into the system before they deploy. I call it the kitchen sink scanner model.

John Willis12:05:00

A decoupled model like Ploigos allows you to create a uniform interface structure. It also is a pipeline as code model so no direct human intervention. This interface model forces a lot of uniform structure for authority sprawl. If you also add Aufomtated Governance on this you have a fully functional *asCode implementation. This helps create admin conformity... .. I know that's a lot .. like I said feel free to reach out if you want to chat more about this..

Philip Day12:05:11

Big takeaway for me (non-technical) is: 3LD model - is it conducive to good collaboration? Are we missing things? Very possibly I can think of issues with our governance model which show up in Line 1 implementation. I'll recommend to our security people on that basis and they can work through the technical parts Thanks you @jwillis!

Gabriela Cavalcante da Silva12:05:22

Thanks @jwillis ! amazing talk

John Willis12:05:56

@philipday My argument is that if we don't change the basic tenets of how we do security all our DevSecOps fu isn't really going to help us in the long run. IMHO, 3LOD is a not collaborative (by design) structure that gives us (conways law) what we deserve from a security posture.

👆 1
Philip Day13:05:14

In our context it represented a big increase in collaboration and empowerment on security matters compared to what went before, so it's really interesting to hear this critique and for us to question do we need to continuously improve at that level - either by optimisation of 3LOD or by another big transformation

John Willis13:05:14

the 2LOD by design firewalls 1LOD and 3LOD. Therefore everything is a telephone game of communication.

Philip Day13:05:35

Tbf we do have (attempted) collaboration between lines 1 and 3 on certain specific projects, with mixed results My concern is more with the whole cycle of identifying risk -> ... -> doing work Is that process delivering? Are we self-reflecting on it?

John Willis13:05:09

BTW, I was asked where I blog. I'm actually focusing a lot of my energy on Dr. Deming these days. The ultimate goal is to tie his work to cyber...

Gene Kim, ITREV, Program Chair13:05:23

Hello! I’ll be presenting with Dr. @stephen on some super interesting work that we’ve done on researching software supply chains!

Stephen Magill [Sonatype]13:05:39

Super excited to be here!

Gene Kim, ITREV, Program Chair13:05:05

This was such a fun project to work on with you, @stephen!!! Year 2 of working together on this!!

Gene Kim, ITREV, Program Chair13:05:01

It was super fun being at GitHub Universe watching Nat Friedman, CEO, GitHub deliver that line of OSS inviting all those devs into your living room. Our reaction was 😱 ⁉️

Daniel Cahill - Engineer - Ontario Systems13:05:04

How long does it take you to put this research together?

Stephen Magill [Sonatype]13:05:12

Yes! And we’re always looking for ideas on what to investigate next. What practices do you think have made an impact at your organization in terms of achieving confidence in security AND keeping dev teams productive?

Philipp Böschen, TUI, DevOps Coach, (he/him)13:05:04

We've seen really helpful trends with "Inner sourcing" - Creating internal specific modules/libraries working together with our security experts to provide an easier starting point. Still in its infancy but I've seen some good things come from that!

Stephen Magill [Sonatype]13:05:09

that’s awesome, @philipp.boeschen650! Do the inner source teams operate differently than other internal dev teams? Different expectations / different processes?

Philipp Böschen, TUI, DevOps Coach, (he/him)13:05:15

Oh there is no teams doing that currently, it's mainly me and a few other likeminded people in a grass roots initiative sponsored and pushed by my boss 🙂

Stephen Magill [Sonatype]13:05:50

that’s how great things start — good luck!

❤️ 1
Philipp Böschen, TUI, DevOps Coach, (he/him)13:05:06

But the expectation and processes are definitely different, the templates being voluntary at the moment, lots to still be discovered there, learning a lot currently 🙂

Stephen Magill [Sonatype]13:05:39

(turning around the Q&A here 🙂 )

Gene Kim, ITREV, Program Chair13:05:57

This is year 2 — we’ll describe Year 1 and new Year 2 findings. This was made possible by the amazing team at Sonatype, who offered us the opportunity to study all the artifacts on Maven Central!

Stephen Magill [Sonatype]13:05:24

Still using Haskell 🙂

Gene Kim, ITREV, Program Chair13:05:38

(@stephen added Haskell onto that graph — wasn’t on the original! 🙂

Gene Kim, ITREV, Program Chair13:05:52

PS: @stephen: I saw this awesome talk about how so many people are using IO monad to stuff all their ugly, imperative code into — and thus leaving side effects in the middle of a mess, instead of pushing all side effects to the edge. Was super interest!

Stephen Magill [Sonatype]13:05:55

very interesting. we use a variety of monads to segregate IO / logging / interaction with external APIs / etc.

Gene Kim, ITREV, Program Chair13:05:05 by Eric Normand, who is quite prolific in Clojure space — he spent many years as a Haskell person. I’ve found him to be incredibly insightful and super smart.

Stephen Magill [Sonatype]13:05:09

makes it very clear what resources a particular function uses.

Gene Kim, ITREV, Program Chair13:05:18

Totally — his comment was that in his previous org, they still mixed I/O in a way that was opposite of “functional core, imperative shell.” This was my biggest aha that made me love functional programming — remember that conversation we had about “what does composable really mean?” That was the context!

Stephen Magill [Sonatype]13:05:53

very cool. whatever language you’re using, being aware of side effects and isolating them is hugely valuable.

Gene Kim, ITREV, Program Chair13:05:28

For sure!! Learning how to push side effects to the edges was a life-changer for me!

Philipp Böschen, TUI, DevOps Coach, (he/him)14:05:13

I've seen some link personally between projects with a very high release velocity and a fatigue on constantly patching up dependencies, so in some areas they just get left behind or pinned to auto pull in releases. Have you seen similar effect? Is there a downside to very high velocity? :thinking_face:

Stephen Magill [Sonatype]14:05:17

it can definitely be a challenge to stay up to date with everything. tools can help a lot here — e.g. automatically suggesting pull requests to update dependencies.

Stephen Magill [Sonatype]14:05:44

Pinning to latest is better than pinning to a fixed old version, but with supply chain attacks increasing (things like malicious actors adding code to open source projects) it’s a practice people are starting to reconsider.

Philipp Böschen, TUI, DevOps Coach, (he/him)14:05:06

Tooling really helps a ton! I've found up until a certain point it's doable for a team to stay on pinned versions and upgrade asap for new ones.

Philipp Böschen, TUI, DevOps Coach, (he/him)14:05:21

Or is the vector of attack here to really try to leverage something like semVer to allow for patch releases to flow through

Gene Kim, ITREV, Program Chair14:05:07

Great point, @philipp.boeschen650 — one of our suspicions is that semver is actually a very poor predictor of breakage during updates. My genuine hope is that we can research this over the next year!

Daniel Cahill - Engineer - Ontario Systems14:05:29

I dislike that theory a lot, but I don't disagree :white_frowning_face:

😁 1
Saket Kulkarni, Coach, Capgemini (he/him)14:05:39

I sadly don’t have any answers, but the issue with semver is that it is largely dependent on the maintainer’s rigor in terms of following the conventions. It’d be a lot nicer if there was wider spread adoption of provider contract testing in some way so that you could actually test if there was breakage.

AlignedDev (Omnitech Engineer)14:05:49

MTTU (Mean Time to Update)

Philipp Böschen, TUI, DevOps Coach, (he/him)14:05:57

Interesting! I've started to feel something similar, we've recently started wrapping some tooling around Renovate ( and while it's amazing help in showing outdated deps, there is a non trivial amount of pipelines failing after bumping the versions. Dependency management really is something intense

Stephen Magill [Sonatype]14:05:58

Yeah, being able to predict breaking changes is becoming really important. Definitely something we want to research soon.

Stephen Magill [Sonatype]14:05:40

There’s been some work on this at Sonatype actually: There’s a feature in there to point out whether an update is likely to go smoothly or have breaking changes.

Philipp Böschen, TUI, DevOps Coach, (he/him)14:05:48

Even the trivial check of "does it still compile and run it's unitests" really helps out a ton in quickly judging dependency updates

Gene Kim, ITREV, Program Chair14:05:21

Ah, @philipp.boeschen650, here’s a paper on what you just mentioned!

😱 1
Philipp Böschen, TUI, DevOps Coach, (he/him)14:05:00

Scheduling dependency upgrades to be part of the daily work seems like a good case of "If it hurts do it more often"

💯 3
AlignedDev (Omnitech Engineer)14:05:51

is it even better if it's a normal daily work thing, we're checking often and just taking care of it?

AlignedDev (Omnitech Engineer)14:05:13

with enough automated test, I feel it should be safe to upgrade

❤️ 1
Philipp Böschen, TUI, DevOps Coach, (he/him)14:05:38

That's definitely the way to go anyway

Philipp Böschen, TUI, DevOps Coach, (he/him)14:05:38

Now to get the security team to help build that 🙏

Ilkka Turunen14:05:43

Yup, the results of this make me think this is is is a rare case of “Doing the right thing for productivity” also prepares you to be ready to do the right thing by security - being able to produce fast means being able to respond fast to security events too

💯 1
Gene Kim, ITREV, Program Chair14:05:24

That is on of my favorite words: “centroids’. It’s what helped me understand clustering in 2005!

Randy Shoup14:05:52

Contour maps around the centroids are awesome

Gene Kim, ITREV, Program Chair14:05:48

@stephen gets all the credit for that one — we moved totally away from SPSS, and I think he did all that in SciKitLearn!

Philipp Böschen, TUI, DevOps Coach, (he/him)14:05:06

Only had a glancing view and thought the arrow downwards in the slides meant that involving in OSS was bad 😆

Ann Perry - IT Revolution14:05:27

📣 And now, let's welcome @cornelia!!

Daniel Cahill - Engineer - Ontario Systems14:05:34

Talking to each other during the presentation is very engaging

Gene Kim, ITREV, Program Chair14:05:51

Hi, @cornelia!!! We’ll be vacating this track in just a second!! cc @stephen!!!

Cornelia Davis14:05:11

Great talk @stephen and @genek!

Gene Kim, ITREV, Program Chair14:05:31

Looking forward to yours, @cornelia!!! 🎉

Randy Shoup14:05:44

Great talk, very timely and actionable @genek @stephen

thankyou 2
AlignedDev (Omnitech Engineer)14:05:49

is there a tool that compares OSS libraries in this way? It seems like it'd be a great app or browser extension

Philipp Böschen, TUI, DevOps Coach, (he/him)14:05:56

👏 really good information and food for thought

Siddharth, NatWest Group, DevOps CoE (he/him)14:05:10

@cornelia #gitops how is bridging the gap between the development & delivery cycle / stream.

Vaidik Kapoor (Speaker) - Technology Consultant14:05:40

I was wondering about this the other day and may be I going beyond my understanding. But it fels like it took us so long to understand what Puppet and Chef had already started doing ages back. They really started pushing Git as the way to manage infrastructure state and could also do drift detection and sync the state back.

Cornelia Davis14:05:09

Yup. Gitops doesn’t replace CI at all. It overlaps with many CD practices (we think GitOps is a better way to do CD) AND goes all the way to what I like to call CO - continuous operations.

🙌 1
Vaidik Kapoor (Speaker) - Technology Consultant14:05:16

the kubernetes ecosystem perhaps made it really fast but it feels like Gitops was always there in some way

Vaidik Kapoor (Speaker) - Technology Consultant14:05:13

“Using git as the interface for ops” - a perspective I feel often operators often fail to understand

Cornelia Davis14:05:36

Yes, I’ve started using another expression - that what we are aiming for is “self service operations” NOT “self service infrastructure”

💯 1
Gene Kim, ITREV, Program Chair14:05:51

My thanks to @cornelia for helping me finally understand what GitOps is and isn’t! 🙂

👍 2
Cornelia Davis14:05:38

We’ve historically been self-serving application teams (developers) with “stuff” to help them do DevOps but just giving them infra - i.e. we give them a Kubernetes environment (and say “good luck. And, oh, BTW, please keep this secure”). What we are aiming for with GitOps is allowing these devops teams to do operations without burdening them with the infra. self-service operations.

👍 1
Olivier Jacques, DXC14:05:48

One technique I used was to declare that production was not accessible outside of a CD pipeline. In other words, your only path to production is GIT + some sort of an orchestrator => GitOps.

Cornelia Davis14:05:07

Yup. And we are quite insistent that the “some sort” has to be convergent.

🤯 1
Olivier Jacques, DXC14:05:25

I find GIT is (relatively) easy to get adopted by developers. It is a longer journey to get it adopted across the various functions. But at least, we know where we are going. GIT.

Cornelia Davis14:05:27

Oh yeah - totally agree. Git is freakin hard. Developers are Git power users. Everyone else, not so much.

Cornelia Davis14:05:44

GitOps does not preclude a different UI over Git than the ones that developers love.

Olivier Jacques, DXC14:05:40

Ahhh. Centralized CD systems and the best attack surface ever. Thanks for bringing that up!

Saket Kulkarni, Coach, Capgemini (he/him)14:05:16

Moving from a push to a pull model

Olivier Jacques, DXC14:05:49

Push on the left, pull on the right

Kim Wallis14:05:59

Can be difficult in practice though? How would you do it for something like Lambdas/Azure Functions or similar applications? :thinking_face: Create a separate service that updates other services..?

Erik Sackman14:05:13

this works great in combination with platform teams, you get a better separation of concerns

Erik Sackman14:05:04

we use k8s operators to deploy other cloud resources via the gitops principle

Andreas Baernthaler - TNG Technology Consulting14:05:58

For me audit requirements were one of the motivations to dig into GitOps. It would be so interesting to discuss GitOps with the auditors currently presenting in track 1.

Cornelia Davis14:05:14

Totally agree! @genek - intro please.

Saket Kulkarni, Coach, Capgemini (he/him)14:05:37

Also, John Willis is exploring “Modern Governance” in his presentation and talks about automated proof of compliance, etc.

Cornelia Davis14:05:15

Thanks, I’ll have a look.

Andreas Baernthaler - TNG Technology Consulting15:05:16

@cornelia Please ping me if you can convince them. I might be able to use that as an agrument to convince clients to do GitOps 😄 .

Saket Kulkarni, Coach, Capgemini (he/him)14:05:10

Is the app configuration in this diagram referring to configurations in containers (since we’ve got Kubernetes on the right)? Are we pulling versions of code directly into our environments or would that typically be running via versioned/tagged container images?

Saket Kulkarni, Coach, Capgemini (he/him)14:05:35

Ah. Never mind. I see the Docker icon. 😁

Randy Shoup14:05:42

Very clearly presented, @cornelia. Thanks!

Vaidik Kapoor (Speaker) - Technology Consultant14:05:42

@cornelia very inspiring talk that I am going to share with my entire team. I feel it will help bring a lot more focus on adopting GitOps because of your explanation

David Read14:05:32

Super @cornelia. I've really struggled with really 'getting' GitOps, rereading WW site and papers, but this presentation was the clearest yet 🙏

🙏 1
💯 2
Saket Kulkarni, Coach, Capgemini (he/him)14:05:47

This is the first explanation of GitOps that finally made clear to me what it is and how it might be useful beyond being a trend. 😁

Andreas Baernthaler - TNG Technology Consulting14:05:42

Here is one reference regarding GitOps I can highly recommend:

🔖 4
Siddharth, NatWest Group, DevOps CoE (he/him)15:05:44

#gitops is one next best thing amongst the other few things that organizations are finally yeah finally moving to with no other option left similar to for e.g. Kubernetes. Good we had this discussion rolling here. thanks to @cornelia 🙂

Siddharth, NatWest Group, DevOps CoE (he/him)20:05:27

Here is the collection of all the reference links that were shared / discussed during the #DOES21 event. Enjoy Reading 🙂