Sort by:  

Authors: Jared Burck, Valentina Rodriguez Sosa, James Bench, Christopher Nuland

tldr - powered by Generative AI

Lessons learned in implementing DevSecOps in large Enterprise IT
  • Take stock of inventory and work with security to change perception of secure software
  • Bring in security officers early on and provide education and training
  • Transitioning to agile methodology and tying it into deployment and build process takes culture change
  • Be mindful of tackling tech debt during migration
  • Learn from industry best practices and use relevant templates
Authors: Shahar Shmaram, Ran Mansoor

tldr - powered by Generative AI

The presentation discusses the challenges faced by a company during hyper growth and how they implemented a solution using GitHub's methodology and Backstage to manage their resources and visualize them in one place.
  • The company faced challenges during hyper growth such as lack of alignment, manually managed resources, unknown resource dependencies and ownership, exploding budget, and lack of technical documentation.
  • They implemented a solution using GitHub's methodology which emphasizes declarative infrastructure as code, versioning, immutability, automatic deployment pipelines, and continuous reconciliation.
  • They also used Backstage, an open platform for building developer portals, to manage their resources in one location, write documentation easily, search for information, use automated software templates, and create self-contained plugins.
  • The solution was auditable, declarative, had a single source of truth, was community-driven, self-serve, and provided visibility.
  • An anecdote was given about how the GitHub solution detected a drift in a policy and automatically brought it back to its desired state.
  • Tags: AI, Cybersecurity, DevOps, GitHub, Backstage, hyper growth, resource management, visualization, automation, documentation, self-serve, community-driven.
Authors: Vineeth Pothulapati

tldr - powered by Generative AI

Migrating from OpenTracing to OpenTelemetry for improved Tracer implementation and performance
  • Two levels of migration: instrumentation layer and collector layer
  • OpenTelemetry shim and complete re-instrumentation are two ways to migrate at the instrumentation layer
  • Complete re-instrumentation offers more capabilities and flexibility
  • OpenTelemetry SDK is more performant and has access to framework plugins
  • Context propagation using baggage and headers is easy in OpenTelemetry
  • OpenTelemetry supports multiple context propagations
  • Demo shows how to migrate from OpenTracing to OpenTelemetry
Authors: Tim Allclair, Sam Stoelinga

tldr - powered by Generative AI

The presentation discusses the migration from Pod Security Policy (PSP) to Pod Security Admission (PSA) in Kubernetes and the limitations of PSA.
  • PSA is a simpler and more secure way to manage pod security in Kubernetes
  • PSA is built into Kubernetes and guarantees that any new features added to Kubernetes will be constrained by PSA
  • The PSP Migrator tool can be used to detect and migrate from PSP to PSA
  • PSA has limitations such as using namespace labels to control it and lack of customization