Search
25 results for “marypcbuk”
-
I first came across Project Copacetic (#Copa for short) in @markrussinovich keynotes about Azure where they use it to patch vulns in millions of container images a month, internally and for Azure users and I thought 'doesn't everyone with container images need to do this'?
Turns out, that's exactly what the Copa team (who also worked on tools like #Radius and #Dapr) thought, and when they open sourced it, other tools like Kubescape started to use it; Anubhav Gupta told me why it's so useful for platform teams. @descopeinc built a whole self-patching registry on top of it. Copa isn't perfect but Vadim Bauer told me it might be a useful plugin for updating images in Harbor the way Microsoft does in ACR with Copa and Dalec.
Microsoft still uses it at massive scale: "every build that goes through our engineering system for any team, runs through Copa,” @sozercan told me.
Copa doesn't create patches but as soon as there is a patch for an issue Trivy (or other scanners) find, it can apply it as a patch layer so you don't have to wait for an official image or even an image rebuild; you can use it with GitHub Actions and Dependabot; it does OS patches, distroless and now app runtime patches for Node.js, Python, .NET and soon Go patching too.
One of the frustrating things with open source is you don't always know who's using it: Bank of America and thousands of other companies are using Copa, almost everyone who's heard of it loves is but it still feels like a bit of a hidden secret in the #CNCF sandbox; maybe this will help!
Extra thanks to everyone who talked to me for this piece, since it was either in the run up to or actually at #Kubecon when everyone is extra busy! Also, hit me up if you're on Mastodon and I haven't tagged you here because @ mentions are being weird for me today...
https://www.thestack.technology/copacetic-copa-patch-containers-automatic-scale/
-
We used to say airily that 'every company is a technology company now' and certainly almost every product from a car to a train ticket is at least partly digital now, so it's time we made companies do the security and support for those products better; that's what the EU Cyber Resilience Act is for.
TLDR starting this September, if you sell a digital product into the EU you have to have a proper vulnerability reporting process in place and report security incidents that affect your customers: by December 2027 you have to have SBOMs and conformity declarations and a minimum of 5 years support and security updates.
I argue that's a good thing that should make organisations shape up their software development practices and maybe, @kat.lol says, they'll do open source better, because now it's a board responsibility that you have to care about project health, be able to contribute any fixes you create upstream and generally act responsibly.
With the state of the software ecosystem and a new supply chain attack almost every week, sometimes from nation state actors, product safety has to cover the digital side of products as well as making sure they don't electrocute you or snap shut on your fingers; the CRA is a way to move that forward.
As @littledan points out to me, the standards to back this up are still in development and there is a push to water them down; we should resist that.
-
choosing a build system is a really technical choice that's all about the language you code in, not something strategic, right? not necessarily; the same principles that make #Bazel so powerful are showing up in other, broader tools for devops like Helm. but it's too hard to adopt, right? maybe not!
there are hardly any other companies that work exactly like Google, but Google is *really big* and uses a lot of languages, so tools written to help Google, like Bazel, have something for almost everyone Ulf Adams of #Engflow tells me - and almost every org has the 'works on my machine' problem when it comes to debugging.
Bazel promises fast, reproducible builds with artefacts you can cache and reuse and you can get the benefits without having to adopt all the rigour Alex Eagle of #AspectBuild explains to me, while Max Kanat-Alexander (who used to run Google's code health team) tells me why being hermetic and reproducible is so powerful when you can do more of it.
if you're not Adobe, Nvidia, Snowflake, LinkedIn or one of the other big companies adopting Bazel with the resources to do a huge migration, that doesn't mean it's not for you: there are JetBrains and VScode plugins and an entire ecosystem of companies run by people who worked on Bazel and Blaze - like EngFlow and Aspect Build.
Bazel is also a really interesting open source governance story. the usual tension between a founder company that needs to control the tool it relies on and a large and vocal open source community gets a possibly unique solution: an open source project for the engine and a foundation for the rules (written in Starlark, another powerful tool) that will be the voice of the community for Google, Helen Altshuler tells me.
will it work? well, that's the same split as inside Google itself, EngFlow's Luis Pino tells me, so there's a good chance it will,.
https://www.thestack.technology/why-everyone-is-moving-to-googles-bazel-build-system/
-
These are the recordings of #privacycamp 2023 Brussels
Salle des Arches
https://piped.kavin.rocks/watch?v=wMYinwWOGp0
Boudoir
https://piped.kavin.rocks/watch?v=9x8mL-izeZQThe videos are about 7:30 hours, each.
@edri The recordings are not clipped, basically they start at about 30 minutes …
-
Looking for an alternative Kubernetes dashboard? @marypcbuk looks at seven to consider https://www.fosslife.org/7-kubernetes-dashboards-consider #Kubernetes #dashboard #clusters #Headlamp #Skooner #Octant #Prometheus #containers
-
alas, by the time the #WindowsUglySweater reaches the UK it's always sold out, which means a lot of money raised for the Nature Conservancy (but I bet you can still call that number for an Easter egg) https://gear.xbox.com/pages/windows
-
and as soon as I unpacked it, Phryne took up her sentry post in the shipping box. this is a very different style of #WindowsUglySweater this year; not just Bliss rather than a cheesy Christmas design, but also softer yarn and smaller switches. still a double layer of knit to get the multiple colours but a much softer drape that makes it less a novelty and more pleasant to wear
-
this year's #WindowsUglySweater is as beautifully packed as ever
-
I first came across Project Copacetic (#Copa for short) in @markrussinovich keynotes about Azure where they use it to patch vulns in millions of container images a month, internally and for Azure users and I thought 'doesn't everyone with container images need to do this'?
Turns out, that's exactly what the Copa team (who also worked on tools like #Radius and #Dapr) thought, and when they open sourced it, other tools like Kubescape started to use it; Anubhav Gupta told me why it's so useful for platform teams. @descopeinc built a whole self-patching registry on top of it. Copa isn't perfect but Vadim Bauer told me it might be a useful plugin for updating images in Harbor the way Microsoft does in ACR with Copa and Dalec.
Microsoft still uses it at massive scale: "every build that goes through our engineering system for any team, runs through Copa,” @sozercan told me.
Copa doesn't create patches but as soon as there is a patch for an issue Trivy (or other scanners) find, it can apply it as a patch layer so you don't have to wait for an official image or even an image rebuild; you can use it with GitHub Actions and Dependabot; it does OS patches, distroless and now app runtime patches for Node.js, Python, .NET and soon Go patching too.
One of the frustrating things with open source is you don't always know who's using it: Bank of America and thousands of other companies are using Copa, almost everyone who's heard of it loves is but it still feels like a bit of a hidden secret in the #CNCF sandbox; maybe this will help!
Extra thanks to everyone who talked to me for this piece, since it was either in the run up to or actually at #Kubecon when everyone is extra busy! Also, hit me up if you're on Mastodon and I haven't tagged you here because @ mentions are being weird for me today...
https://www.thestack.technology/copacetic-copa-patch-containers-automatic-scale/
-
I first came across Project Copacetic (#Copa for short) in @markrussinovich keynotes about Azure where they use it to patch vulns in millions of container images a month, internally and for Azure users and I thought 'doesn't everyone with container images need to do this'?
Turns out, that's exactly what the Copa team (who also worked on tools like #Radius and #Dapr) thought, and when they open sourced it, other tools like Kubescape started to use it; Anubhav Gupta told me why it's so useful for platform teams. @descopeinc built a whole self-patching registry on top of it. Copa isn't perfect but Vadim Bauer told me it might be a useful plugin for updating images in Harbor the way Microsoft does in ACR with Copa and Dalec.
Microsoft still uses it at massive scale: "every build that goes through our engineering system for any team, runs through Copa,” @sozercan told me.
Copa doesn't create patches but as soon as there is a patch for an issue Trivy (or other scanners) find, it can apply it as a patch layer so you don't have to wait for an official image or even an image rebuild; you can use it with GitHub Actions and Dependabot; it does OS patches, distroless and now app runtime patches for Node.js, Python, .NET and soon Go patching too.
One of the frustrating things with open source is you don't always know who's using it: Bank of America and thousands of other companies are using Copa, almost everyone who's heard of it loves is but it still feels like a bit of a hidden secret in the #CNCF sandbox; maybe this will help!
Extra thanks to everyone who talked to me for this piece, since it was either in the run up to or actually at #Kubecon when everyone is extra busy! Also, hit me up if you're on Mastodon and I haven't tagged you here because @ mentions are being weird for me today...
https://www.thestack.technology/copacetic-copa-patch-containers-automatic-scale/
-
I first came across Project Copacetic (#Copa for short) in @markrussinovich keynotes about Azure where they use it to patch vulns in millions of container images a month, internally and for Azure users and I thought 'doesn't everyone with container images need to do this'?
Turns out, that's exactly what the Copa team (who also worked on tools like #Radius and #Dapr) thought, and when they open sourced it, other tools like Kubescape started to use it; Anubhav Gupta told me why it's so useful for platform teams. @descopeinc built a whole self-patching registry on top of it. Copa isn't perfect but Vadim Bauer told me it might be a useful plugin for updating images in Harbor the way Microsoft does in ACR with Copa and Dalec.
Microsoft still uses it at massive scale: "every build that goes through our engineering system for any team, runs through Copa,” @sozercan told me.
Copa doesn't create patches but as soon as there is a patch for an issue Trivy (or other scanners) find, it can apply it as a patch layer so you don't have to wait for an official image or even an image rebuild; you can use it with GitHub Actions and Dependabot; it does OS patches, distroless and now app runtime patches for Node.js, Python, .NET and soon Go patching too.
One of the frustrating things with open source is you don't always know who's using it: Bank of America and thousands of other companies are using Copa, almost everyone who's heard of it loves is but it still feels like a bit of a hidden secret in the #CNCF sandbox; maybe this will help!
Extra thanks to everyone who talked to me for this piece, since it was either in the run up to or actually at #Kubecon when everyone is extra busy! Also, hit me up if you're on Mastodon and I haven't tagged you here because @ mentions are being weird for me today...
https://www.thestack.technology/copacetic-copa-patch-containers-automatic-scale/
-
I first came across Project Copacetic (#Copa for short) in @markrussinovich keynotes about Azure where they use it to patch vulns in millions of container images a month, internally and for Azure users and I thought 'doesn't everyone with container images need to do this'?
Turns out, that's exactly what the Copa team (who also worked on tools like #Radius and #Dapr) thought, and when they open sourced it, other tools like Kubescape started to use it; Anubhav Gupta told me why it's so useful for platform teams. @descopeinc built a whole self-patching registry on top of it. Copa isn't perfect but Vadim Bauer told me it might be a useful plugin for updating images in Harbor the way Microsoft does in ACR with Copa and Dalec.
Microsoft still uses it at massive scale: "every build that goes through our engineering system for any team, runs through Copa,” @sozercan told me.
Copa doesn't create patches but as soon as there is a patch for an issue Trivy (or other scanners) find, it can apply it as a patch layer so you don't have to wait for an official image or even an image rebuild; you can use it with GitHub Actions and Dependabot; it does OS patches, distroless and now app runtime patches for Node.js, Python, .NET and soon Go patching too.
One of the frustrating things with open source is you don't always know who's using it: Bank of America and thousands of other companies are using Copa, almost everyone who's heard of it loves is but it still feels like a bit of a hidden secret in the #CNCF sandbox; maybe this will help!
Extra thanks to everyone who talked to me for this piece, since it was either in the run up to or actually at #Kubecon when everyone is extra busy! Also, hit me up if you're on Mastodon and I haven't tagged you here because @ mentions are being weird for me today...
https://www.thestack.technology/copacetic-copa-patch-containers-automatic-scale/
-
hey #Kubernetes and #VMware folks: is #Octant still under active development/maintained?
-
alas, by the time the #WindowsUglySweater reaches the UK it's always sold out, which means a lot of money raised for the Nature Conservancy (but I bet you can still call that number for an Easter egg) https://gear.xbox.com/pages/windows
-
alas, by the time the #WindowsUglySweater reaches the UK it's always sold out, which means a lot of money raised for the Nature Conservancy (but I bet you can still call that number for an Easter egg) https://gear.xbox.com/pages/windows
-
alas, by the time the #WindowsUglySweater reaches the UK it's always sold out, which means a lot of money raised for the Nature Conservancy (but I bet you can still call that number for an Easter egg) https://gear.xbox.com/pages/windows
-
alas, by the time the #WindowsUglySweater reaches the UK it's always sold out, which means a lot of money raised for the Nature Conservancy (but I bet you can still call that number for an Easter egg) https://gear.xbox.com/pages/windows
-
and as soon as I unpacked it, Phryne took up her sentry post in the shipping box. this is a very different style of #WindowsUglySweater this year; not just Bliss rather than a cheesy Christmas design, but also softer yarn and smaller switches. still a double layer of knit to get the multiple colours but a much softer drape that makes it less a novelty and more pleasant to wear
-
and as soon as I unpacked it, Phryne took up her sentry post in the shipping box. this is a very different style of #WindowsUglySweater this year; not just Bliss rather than a cheesy Christmas design, but also softer yarn and smaller switches. still a double layer of knit to get the multiple colours but a much softer drape that makes it less a novelty and more pleasant to wear
-
and as soon as I unpacked it, Phryne took up her sentry post in the shipping box. this is a very different style of #WindowsUglySweater this year; not just Bliss rather than a cheesy Christmas design, but also softer yarn and smaller switches. still a double layer of knit to get the multiple colours but a much softer drape that makes it less a novelty and more pleasant to wear
-
and as soon as I unpacked it, Phryne took up her sentry post in the shipping box. this is a very different style of #WindowsUglySweater this year; not just Bliss rather than a cheesy Christmas design, but also softer yarn and smaller switches. still a double layer of knit to get the multiple colours but a much softer drape that makes it less a novelty and more pleasant to wear
-
this year's #WindowsUglySweater is as beautifully packed as ever
-
this year's #WindowsUglySweater is as beautifully packed as ever
-
this year's #WindowsUglySweater is as beautifully packed as ever
-
this year's #WindowsUglySweater is as beautifully packed as ever