Create accountLogin

Recent searches

No recent searches

Search options

Not available on dice.camp.
dice.camp is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon server for RPG folks to hang out and talk. Not owned by a billionaire.

Administered by:

Server stats:

1.8K
active users

dice.camp: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#devops

41 posts34 participants0 posts today
Public
Esk 🐌⚡💜

hey, fediverse friends - i'm excited that we're finally announcing our Fediverse Security Fund over at @nivenly to help make fedi software more secure.

we're starting off super small to see if the Fund is a thing that can help. along the way we'll learn and improve our intake/payout process. and if there's solid interest and we see good impact, we'll hold a member vote near the end of the experiment to decide if we'll renew/expand the program.

thanks to @thisismissem for her contributions and being the first disclosure to validate the process.

let's close some vulns! :blobfoxscience:

#fediverse#security#devops
Public
Jonathan Matthews

If you're at #KubeCon today (or the rest of the week?) do go say hi to the #CUE folks 😀 I help write their open-source docs (cuelang.org/docs) 'cos I *really* want the awesome tech to succeed!

If you're a #SysAdmin or #DevOps in #YAML config hell go and have a chat with them - next to the CNCF corner store at stall S761 😀

CUEDocumentationWelcome to CUE! CUE is an open-source data validation language with its roots in logic programming. It combines succinct yet clear syntax with powerful, flexible constraints that enable data, schema, and policy constraints to coexist seamlessly: Copied! example.cue Copy code Copied! area: length * width area: <100 // Must be less than 100. width: 33.3 & >10 // Must be greater than 10. length: 5 & !=width // Reject square areas.
#PlatformEngineering#SRE#platform
Public
Jan Bartosik

#hiring update:

Vážení,
pořád sháním 2 devopsáky:

1. anglicky hovořící seniorního Devopsáka na pozici "Azure Architect" na full #remote klientský projekt.
Azure DevOps jako takový tam není, mají Gitlab CICD.
ASAP, of course :)

2. seniorní "Devops a Infra Specialist" do interního týmu, hybrid #Praha, leadership skills vítány.
Je to DevOps role rozkročená mezi team leaderem, kontzultantem a cloud architektem.
Chceme vybrat dobře, ne rychle.

#devops#infrastructure#azure
Public
Ivo Limmen

This is a nice write up on my stance with #AI as well: sgnt.ai/p/hell-out-of-llms/. I have nothing against #machinelearning but against #llm's that are general can't be great at everything. It's what is the problem with #IT in general: everyone must be great at everything (#devops) and that will not be the case; #software #craftsmanship is suffering.

sgnt.aiGet the hell out of the LLM as soon as possible | sgnt.aiDon’t let an LLM make decisions or implement business logic: they suck at that.
Public *
Bo Morgan

Just set up my first Jenkins pipeline Debian package build process for a project using podman. I love the SCM declarative pipeline description. Created my first devops-specific git repo to hold the pipeline script and the podman dockerfile.

Although it is set up to be trigger from pushes to the main branch on my codeberg git repo, I'm just pressing build occasionally for the fun of watching it turn green.

I've only set up the first stage of the pipeline, but it gives me a solid sense of accomplishment.

The image displays a "Stage View" from a software development tool, showing the average stage times for a series of builds. The top section of the image includes a table with columns labeled "Declarative: Checkout SCM," "Build," "Test," "Create Image," and "Deploy." The "Checkout SCM" column shows a consistent time of 3 seconds for each build. The "Build" column shows varying times, with the most recent build at 1 minute and 34 seconds, highlighted in blue. The "Test" column shows times ranging from 72ms to 93ms, while the "Create Image" and "Deploy" columns show times ranging from 65ms to 85ms. The left side of the image lists six builds with their respective timestamps and the number of commits. The most recent build (#45) is at 18:20 with no changes, while the build (#40) at 05:29 has 2 commits. The average stage time is displayed as 3 seconds, with a full run time of approximately 3 minutes and 40 seconds. The background is dark, with the text and bars in various shades of blue and green, providing a clear contrast for readability.
#jenkins#pipeline#devops
Public
ReynardSec

Gentle reminder 👉 If you're looking to level up your #kubernetes security skills, check out this guide!

reynardsec.com/en/kubernetes-s

It's a free, no-BS resource filled with practical tips and even comes with a tool to spin up your own local lab cluster

ReynardSec · Kubernetes Security Guide (Kubernetes Hardening) - ReynardSecThis article discusses the topic of securing the configuration of Kubernetes clusters. This software is considered quite challenging to manage due to the multitude of settings and areas that need to be addressed. The challenges associated with this can impact the security level of the applied configuration. As usual, my goal is not merely to present a dry list of parameters and ready-made configuration snippets but to provide the reader with a fuller context. I want the reader to understand why certain modifications are necessary and what benefits their implementation will bring. Theory and practice must go hand in hand! Therefore, I have prepared a tool that will allow you to test everything I write about here in your local environment. You will find a script here that will easily start your Kubernetes cluster. The information contained in this text should be treated as a set of basic issues that need to be addressed in the context of securely configuring a Kubernetes cluster. It is possible that your specific application will require additional work.
#devops#programming#webdev
ExploreLive feeds
About