Continuous Delivery and Automated Operations on k8s with keptn
Download as pptx, pdf1 like394 views
The document discusses the development of Keptn, a tool designed to address challenges in cloud-native delivery and operations, which are often error-prone and difficult to manage. Keptn aims to automate continuous delivery and operations through a control plane that facilitates self-healing deployments, automated pipelines, and operational efficiency. The text highlights features such as gitops-enabled delivery, automated quality gates, and a separation of delivery and operations processes.
1 of 24
Downloaded 14 times
![13
Config ChatOps IT Autom
Deploy Test Observe
Zero-Touch Cloud Native Services: $ keptn onboard service myservice [xxx.yaml]
S
T
A
G
I
N
G
P
R
O
D
DirectUpdateC D
Blue/GreenUpdateC D
PLACEHOLDER
PLACEHOLDER](https://image.slidesharecdn.com/keptnmeetupviennadevopssept2019-190925183208/85/Continuous-Delivery-and-Automated-Operations-on-k8s-with-keptn-12-320.jpg)
Ad
Recommended
Jenkins Online Meetup - Automated SLI based Build Validation with Keptn
Jenkins Online Meetup - Automated SLI based Build Validation with KeptnAndreas Grabner This document discusses automating SLI/SLO based build validation with Keptn and Jenkins. It begins by outlining the challenges of lengthy manual approval processes for promoting builds. It then provides inspiration from Google's SRE practices of using Service Level Indicators (SLIs), Service Level Objectives (SLOs), and Service Level Agreements (SLAs). The document demonstrates how Keptn can automate SLI/SLO-based evaluation to integrate with Jenkins pipelines. It includes demos of using Keptn for self-service SLI validation, automating existing Jenkins tests, and enabling performance as a self-service. The document promotes starting resources on GitHub and joining the Keptn community slack channel
Keptn - Automated Operations & Continuous Delivery for k8s
Keptn - Automated Operations & Continuous Delivery for k8sAndreas Grabner The document discusses Keptn, a tool designed to facilitate autonomous cloud management and streamline the continuous delivery and operations processes for cloud-native applications. It emphasizes features like automated multi-stage delivery, self-healing operations, and integration with existing CI/CD pipelines, targeting the reduction of manual interventions and increasing deployment speed and reliability. The content also highlights the importance of monitoring, automated quality gates, and event-driven methodologies in modern cloud operations.
A Guide to Event-Driven SRE-inspired DevOps
A Guide to Event-Driven SRE-inspired DevOpsAndreas Grabner The document provides a guide on event-driven Site Reliability Engineering (SRE) inspired DevOps using Keptn to streamline delivery and operations. It addresses common challenges in monolithic delivery pipelines and proposes event-driven solutions for efficient integration, quality gate automation, and incident management. The guide emphasizes leveraging Service Level Indicators (SLIs) and Service Level Objectives (SLOs) to improve continuous delivery processes and automate quality assessments.
Shipping Code like a keptn: Continuous Delivery & Automated Operations on k8s
Shipping Code like a keptn: Continuous Delivery & Automated Operations on k8sAndreas Grabner The document discusses automation in software delivery and operations, highlighting the challenges of cloud-native environments and the need for streamlined delivery pipelines. It introduces Keptn, a tool designed to facilitate continuous delivery and operational tasks, enabling features like automated testing, multistage delivery, and integration with various tools. The document outlines installation steps and encapsulates key functionalities of Keptn, emphasizing its role in reducing deployment times and enhancing operational efficiency.
Release Readiness Validation with Keptn for Austrian Online Banking Software
Release Readiness Validation with Keptn for Austrian Online Banking SoftwareAndreas Grabner The document discusses the implementation of release readiness validation using Keptn for Austrian online banking software, detailing the tools and processes involved. It covers continuous testing, metrics for service level indicators (SLIs), and service level objectives (SLOs), including examples of configuration using Dynatrace. The presentation also highlights the current state of the project, ongoing developments, and next steps for future enhancements.
Top Performance Problems in Distributed Architectures
Top Performance Problems in Distributed ArchitecturesAndreas Grabner When moving to a more distributed architecture, you introduce more dependencies and potential for failures to impact services. Common anti-patterns that can arise include making excessive duplicate calls or queries (N+1 patterns), transmitting unnecessary payload data, having services with tight coupling, and inefficient service flows. It is important to understand dependencies between services and automate performance tests and validations as part of continuous integration/deployment pipelines to identify issues and prevent regressions.
Monitoring as a Self-Service in Atlassian DevOps Toolchain
Monitoring as a Self-Service in Atlassian DevOps ToolchainAndreas Grabner This document discusses how Dynatrace provides monitoring as a self-service through integrations with Atlassian tools, allowing developers to monitor applications throughout the development lifecycle. It explains that Dynatrace automatically monitors the full stack, from the cloud infrastructure to mobile apps. Dynatrace also enables fearless deployments through tracking feature success in JIRA, incident response in chat tools like HipChat, and triaging incidents in JIRA with root cause information from Dynatrace.
Applying AI to Performance Engineering: Shift-Left, Shift-Right, Self-Healing
Applying AI to Performance Engineering: Shift-Left, Shift-Right, Self-HealingAndreas Grabner The document discusses how artificial intelligence can be applied to performance engineering to make it self-healing and self-service. It describes how monitoring needs have evolved from just looking at dashboards and logs to dealing with dynamic cloud environments. It outlines how AI can be used for full-stack monitoring with one agent, automated end-to-end tracing, automated log analytics and change detection. It then discusses how AI can enable shifting work left to break the pipeline earlier, improve mean time to resolution with auto-mitigation, and shift work right with tags, deployments and events to create actionable feedback loops across development, operations and business teams.
Moving beyond DevOps with automated cloud-native platforms
Moving beyond DevOps with automated cloud-native platformsDirk Wallerstorfer The document discusses the transition from traditional DevOps to autonomous cloud operations, emphasizing automation and tool consolidation to enhance performance monitoring and resource efficiency. It outlines strategies for implementing continuous deployment (CD) pipelines, auto-remediation, and shift-left/right practices to increase speed and quality in software development. The goal is to foster a culture of 'no operations' (noops) by integrating cloud and container platforms while improving customer satisfaction through proactive issue resolution.
Performance Metrics Driven CI/CD - Introduction to Continuous Innovation and ...
Performance Metrics Driven CI/CD - Introduction to Continuous Innovation and ...Mike Villiger The document discusses performance metrics-driven CI/CD strategies, emphasizing continuous innovation and optimization in software delivery. It outlines challenges faced by teams moving from monolithic architectures to microservices, highlighting deployment complexities and the importance of automated testing. Key metrics and processes are proposed to enhance quality, scalability, and user satisfaction in the development lifecycle.
Metrics-driven Continuous Delivery
Metrics-driven Continuous DeliveryAndrew Phillips 1. The document discusses metrics-driven continuous delivery and focuses on using metrics throughout the development and delivery process.
2. It emphasizes using architectural metrics in addition to functional metrics to help determine if a new version is likely to cause catastrophic failures before deploying to production.
3. It also argues that the concept of continuous delivery pipelines should extend beyond production deployments to help evaluate user experience and gain feedback on new features beyond just technical metrics.
DevOps Pipelines and Metrics Driven Feedback Loops
DevOps Pipelines and Metrics Driven Feedback LoopsAndreas Grabner The document discusses metrics-driven pipelines and testing in DevOps, emphasizing the importance of minimizing cycle time to enhance delivery and user experience. It highlights successful case studies of continuous delivery practices, illustrating significant improvements in deployment frequency and software quality. Additionally, it advocates for 'shift-left' performance strategies to identify and resolve issues early in the development process, ultimately leading to faster lead times and business success.
Keptn: Unbreakable Continuous Delivery - Berlin CI/CD Meetup
Keptn: Unbreakable Continuous Delivery - Berlin CI/CD MeetupJürgen Etzlstorfer Keptn is an open source framework that aims to solve the challenges of cloud native continuous delivery by automating multi-stage unbreakable delivery pipelines, self-healing blue/green deployments, and event-driven runbook automation. It uses GitOps principles and Kubernetes-native technologies to allow developers to focus on building code and operations to focus on automating tasks. Keptn handles tasks like creating development, staging, and production environments; onboarding and deploying services; running automated tests; evaluating deployments; and promoting changes between environments through a series of events and actions.
DevOps Days Toronto: From 6 Months Waterfall to 1 hour Code Deploys
DevOps Days Toronto: From 6 Months Waterfall to 1 hour Code DeploysAndreas Grabner The document details Dynatrace's transformation journey from a six-month deployment cycle to a one-hour code deployment process, emphasizing the importance of user-driven feedback and continuous delivery. Key lessons included the need for increased deployment velocity, automated error analysis, and better collaboration between development and operations teams. It highlights the company's achievements in terms of feature releases and deployment frequency, showcasing a significant enhancement in product quality and customer satisfaction.
How to explain DevOps to your mom
How to explain DevOps to your momAndreas Grabner The document discusses how to explain DevOps to non-technical individuals, using examples from companies like Facebook and PayPal. It outlines the shift from traditional development practices to a continuous delivery model, emphasizing immediate customer feedback and the importance of collaboration between development and operations teams. The presentation highlights the role of monitoring tools, trends in DevOps, and the impact of automated communication on productivity and overall user experience.
Building Autonomous Operations for Kubernetes with keptn
Building Autonomous Operations for Kubernetes with keptnJohannes Bräuer Keptn is a framework for automating continuous delivery and operations of Kubernetes applications. It uses a GitOps-based approach with event-driven automation to enable unbreakable delivery pipelines and self-healing deployments. Keptn provides autonomous control plane capabilities including automated testing, deployment, evaluation and operations through reusable services. The demo shows how keptn can onboard a service, deploy new versions through the stages, and enable automated remediation through integration with monitoring and runbook tools.
How to build your own auto-remediation workflow - Ansible Meetup Munich
How to build your own auto-remediation workflow - Ansible Meetup MunichJürgen Etzlstorfer This document discusses building an auto-remediation workflow for applications using Ansible. It begins by explaining what auto-remediation is and why it is needed given the increasing complexity of modern applications. It then outlines the key components needed for self-healing applications, including monitoring, root cause analysis, and automated remediation actions. The presentation demonstrates how to build an auto-remediation workflow using Ansible and API calls, and provides an example playbook for rolling back a bad deployment. It concludes by discussing best practices for starting to implement auto-remediation and embedding it within a CI/CD pipeline to enable faster response times to issues.
AWS Summit - Trends in Advanced Monitoring for AWS environments
AWS Summit - Trends in Advanced Monitoring for AWS environmentsAndreas Grabner Dynatrace is an AI-based monitoring solution designed for AWS environments, capable of monitoring thousands of servers efficiently. The document outlines the evolution of monitoring techniques, emphasizing the need for continuous delivery and the role of automation in DevOps practices. Key statistics highlight Dynatrace's impact with a high rate of deployments and the use of advanced analytics for problem detection and remediation.
Flux is incubating + the road ahead
Flux is incubating + the road aheadLibbySchulze This document discusses Flux, an open source tool for Kubernetes continuous delivery. It summarizes Flux version 2 updates, how Flux enables GitOps practices, and how Flux can be used by different roles like cluster operators, platform engineers, and app developers to automate infrastructure and application deployments. Key features of Flux discussed include multi-cluster management, observability integrations, and the GitOps toolkit for building custom continuous delivery systems.
Metrics driven dev ops 2017
Metrics driven dev ops 2017Jerry Tan Metrics-Driven DevOps discusses how Dynatrace has shifted to continuous delivery of software using a DevOps approach. Some key points:
- Dynatrace has moved to releasing major updates 26 times per year with 170 production deployments daily, up from a previous model of major releases every 6 months.
- They implemented practices like continuous integration/delivery, performance testing pipelines, and monitoring of production metrics to optimize lead time and catch issues earlier.
- Dynatrace uses its own products to monitor pipelines and applications, enabling teams to get feedback and fail builds quickly when issues arise.
- Culture change and collaboration across teams was important to align engineers as the company transformed practices to support continuous delivery at
Canary Analyze All The Things: How We Learned to Keep Calm and Release Often
Canary Analyze All The Things: How We Learned to Keep Calm and Release OftenC4Media The document discusses the importance and implementation of canary analysis in deployment processes, particularly at Netflix, highlighting its role in gradually rolling out changes with checkpoints for monitoring. It emphasizes the benefits of this strategy in improving software deployment safety, speed, and ease, while mentioning the culture of innovation at Netflix. The author presents a detailed overview of best practices and metrics for successful canary deployments and automation in the analysis process.
Modern Operations at Scale within Viasat – How to Structure Teams and Build A...
Modern Operations at Scale within Viasat – How to Structure Teams and Build A...Atlassian 1. ViaSat implemented a DevOps model and tools like Splunk, xMatters, Jira and HipChat to improve incident response times and enable automated collaboration across teams.
2. Use cases described how full closed loop incidents could be managed from initial alert to resolution. CI/CD pipelines allowed for automated deployments and documentation updates.
3. Benefits included reducing response times from 10 minutes to 30 seconds on average, empowering on-call staff to focus on fixing issues rather than administrative tasks, and enabling seamless escalation to ChatOps teams.
Continuous integration testing 2019 08
Continuous integration testing 2019 08David Stanke The document discusses the importance of continuous integration testing in software development, emphasizing the need to shift testing processes earlier in the development cycle. It outlines various integration testing methods and their trade-offs in terms of fidelity, isolation, speed, scalability, and cost. The author encourages informed risk analysis to optimize integration testing practices while acknowledging the complexities involved with microservices architecture.
Continuous Integration Testing: Fully test your microservices application, ea...
Continuous Integration Testing: Fully test your microservices application, ea...David Stanke The document discusses the importance of continuous integration and testing in microservices development, emphasizing that early bug detection is more cost-effective. It outlines various integration testing techniques and the challenges associated with testing in production environments. The author encourages developers to assess their risk tolerance and select the best practices for their specific integration testing needs.
Canary releases & Blue green deployment
Canary releases & Blue green deploymentSQUADEX This document discusses canary releases and blue-green deployments to eliminate downtime when updating products. It introduces only reliable, tested features to small groups of live users before broad rollout. This allows the updated product to perform reliably at large scale immediately. The document also lists benefits like decreasing costs of innovation and failure while enabling A/B testing and reliable deployments. It proposes a 3-month, $60k project to implement continuous monitoring, canary releases, and blue-green deployments.
Boston DevOps Days 2016: Implementing Metrics Driven DevOps - Why and How
Boston DevOps Days 2016: Implementing Metrics Driven DevOps - Why and HowAndreas Grabner The document discusses the importance of metrics-driven DevOps, highlighting how availability, user experience, resource consumption, scalability, and performance impact overall success. It emphasizes the transition from monolithic applications to a service-oriented architecture to enhance performance and facilitate faster deployments. Key insights include the necessity of measuring success and not blindly automating processes without assessing their effectiveness.
What's Missing? Microservices Meetup at Cisco
What's Missing? Microservices Meetup at CiscoAdrian Cockcroft The document discusses key components and challenges in microservices architecture, focusing on aspects like failure injection testing, versioning, routing, and data models. It emphasizes the importance of monitoring, tracing, and the need for simplicity and reliability in distributed systems. The insights provided are based on experiences and techniques developed at Netflix, and they include various tools and practices to enhance microservices management.
Metrics Driven DevOps - Automate Scalability and Performance Into your Pipeline
Metrics Driven DevOps - Automate Scalability and Performance Into your PipelineAndreas Grabner The document discusses metrics-driven DevOps practices, emphasizing the importance of automating scalability and performance checks within the development pipeline. It highlights the challenges faced when applications do not scale effectively under increased loads and the necessity for re-architecting monolithic applications into services for better performance management. Additionally, it outlines various strategies for preventing bad code deployments through robust testing and monitoring processes, ultimately aiming for efficient app delivery and user satisfaction.
Ship code like a keptn
Ship code like a keptnRob Jahn Keptn is an open-source project that provides tools to enable continuous delivery and automation for modern applications using Kubernetes. It allows developers to focus on code and DevOps teams to focus on tools rather than building custom pipelines. Keptn provides automated multi-stage delivery pipelines, automated quality gates, self-healing deployments, and enables zero-touch toolchain integration and updates. It also supports automated problem remediation in production for continuous operations. Keptn follows cloud-native design principles and provides a common way for organizations to achieve autonomous delivery and operations.
Chicago DevOps Meetup Nov2019
Chicago DevOps Meetup Nov2019Mike Villiger The document discusses the need for autonomous cloud management to reduce mean time to innovation and remediation by automating operations, deployment, monitoring, and quality using tools like Keptn. Keptn is a control plane that uses a declarative GitOps-based approach with standardized CloudEvents to define delivery and operations processes to enable continuous delivery and operations. It integrates with various tools to automate testing, deployment, monitoring and remediation through event-driven workflows.
More Related Content
What's hot (20)
Moving beyond DevOps with automated cloud-native platforms
Moving beyond DevOps with automated cloud-native platformsDirk Wallerstorfer The document discusses the transition from traditional DevOps to autonomous cloud operations, emphasizing automation and tool consolidation to enhance performance monitoring and resource efficiency. It outlines strategies for implementing continuous deployment (CD) pipelines, auto-remediation, and shift-left/right practices to increase speed and quality in software development. The goal is to foster a culture of 'no operations' (noops) by integrating cloud and container platforms while improving customer satisfaction through proactive issue resolution.
Performance Metrics Driven CI/CD - Introduction to Continuous Innovation and ...
Performance Metrics Driven CI/CD - Introduction to Continuous Innovation and ...Mike Villiger The document discusses performance metrics-driven CI/CD strategies, emphasizing continuous innovation and optimization in software delivery. It outlines challenges faced by teams moving from monolithic architectures to microservices, highlighting deployment complexities and the importance of automated testing. Key metrics and processes are proposed to enhance quality, scalability, and user satisfaction in the development lifecycle.
Metrics-driven Continuous Delivery
Metrics-driven Continuous DeliveryAndrew Phillips 1. The document discusses metrics-driven continuous delivery and focuses on using metrics throughout the development and delivery process.
2. It emphasizes using architectural metrics in addition to functional metrics to help determine if a new version is likely to cause catastrophic failures before deploying to production.
3. It also argues that the concept of continuous delivery pipelines should extend beyond production deployments to help evaluate user experience and gain feedback on new features beyond just technical metrics.
DevOps Pipelines and Metrics Driven Feedback Loops
DevOps Pipelines and Metrics Driven Feedback LoopsAndreas Grabner The document discusses metrics-driven pipelines and testing in DevOps, emphasizing the importance of minimizing cycle time to enhance delivery and user experience. It highlights successful case studies of continuous delivery practices, illustrating significant improvements in deployment frequency and software quality. Additionally, it advocates for 'shift-left' performance strategies to identify and resolve issues early in the development process, ultimately leading to faster lead times and business success.
Keptn: Unbreakable Continuous Delivery - Berlin CI/CD Meetup
Keptn: Unbreakable Continuous Delivery - Berlin CI/CD MeetupJürgen Etzlstorfer Keptn is an open source framework that aims to solve the challenges of cloud native continuous delivery by automating multi-stage unbreakable delivery pipelines, self-healing blue/green deployments, and event-driven runbook automation. It uses GitOps principles and Kubernetes-native technologies to allow developers to focus on building code and operations to focus on automating tasks. Keptn handles tasks like creating development, staging, and production environments; onboarding and deploying services; running automated tests; evaluating deployments; and promoting changes between environments through a series of events and actions.
DevOps Days Toronto: From 6 Months Waterfall to 1 hour Code Deploys
DevOps Days Toronto: From 6 Months Waterfall to 1 hour Code DeploysAndreas Grabner The document details Dynatrace's transformation journey from a six-month deployment cycle to a one-hour code deployment process, emphasizing the importance of user-driven feedback and continuous delivery. Key lessons included the need for increased deployment velocity, automated error analysis, and better collaboration between development and operations teams. It highlights the company's achievements in terms of feature releases and deployment frequency, showcasing a significant enhancement in product quality and customer satisfaction.
How to explain DevOps to your mom
How to explain DevOps to your momAndreas Grabner The document discusses how to explain DevOps to non-technical individuals, using examples from companies like Facebook and PayPal. It outlines the shift from traditional development practices to a continuous delivery model, emphasizing immediate customer feedback and the importance of collaboration between development and operations teams. The presentation highlights the role of monitoring tools, trends in DevOps, and the impact of automated communication on productivity and overall user experience.
Building Autonomous Operations for Kubernetes with keptn
Building Autonomous Operations for Kubernetes with keptnJohannes Bräuer Keptn is a framework for automating continuous delivery and operations of Kubernetes applications. It uses a GitOps-based approach with event-driven automation to enable unbreakable delivery pipelines and self-healing deployments. Keptn provides autonomous control plane capabilities including automated testing, deployment, evaluation and operations through reusable services. The demo shows how keptn can onboard a service, deploy new versions through the stages, and enable automated remediation through integration with monitoring and runbook tools.
How to build your own auto-remediation workflow - Ansible Meetup Munich
How to build your own auto-remediation workflow - Ansible Meetup MunichJürgen Etzlstorfer This document discusses building an auto-remediation workflow for applications using Ansible. It begins by explaining what auto-remediation is and why it is needed given the increasing complexity of modern applications. It then outlines the key components needed for self-healing applications, including monitoring, root cause analysis, and automated remediation actions. The presentation demonstrates how to build an auto-remediation workflow using Ansible and API calls, and provides an example playbook for rolling back a bad deployment. It concludes by discussing best practices for starting to implement auto-remediation and embedding it within a CI/CD pipeline to enable faster response times to issues.
AWS Summit - Trends in Advanced Monitoring for AWS environments
AWS Summit - Trends in Advanced Monitoring for AWS environmentsAndreas Grabner Dynatrace is an AI-based monitoring solution designed for AWS environments, capable of monitoring thousands of servers efficiently. The document outlines the evolution of monitoring techniques, emphasizing the need for continuous delivery and the role of automation in DevOps practices. Key statistics highlight Dynatrace's impact with a high rate of deployments and the use of advanced analytics for problem detection and remediation.
Flux is incubating + the road ahead
Flux is incubating + the road aheadLibbySchulze This document discusses Flux, an open source tool for Kubernetes continuous delivery. It summarizes Flux version 2 updates, how Flux enables GitOps practices, and how Flux can be used by different roles like cluster operators, platform engineers, and app developers to automate infrastructure and application deployments. Key features of Flux discussed include multi-cluster management, observability integrations, and the GitOps toolkit for building custom continuous delivery systems.
Metrics driven dev ops 2017
Metrics driven dev ops 2017Jerry Tan Metrics-Driven DevOps discusses how Dynatrace has shifted to continuous delivery of software using a DevOps approach. Some key points:
- Dynatrace has moved to releasing major updates 26 times per year with 170 production deployments daily, up from a previous model of major releases every 6 months.
- They implemented practices like continuous integration/delivery, performance testing pipelines, and monitoring of production metrics to optimize lead time and catch issues earlier.
- Dynatrace uses its own products to monitor pipelines and applications, enabling teams to get feedback and fail builds quickly when issues arise.
- Culture change and collaboration across teams was important to align engineers as the company transformed practices to support continuous delivery at
Canary Analyze All The Things: How We Learned to Keep Calm and Release Often
Canary Analyze All The Things: How We Learned to Keep Calm and Release OftenC4Media The document discusses the importance and implementation of canary analysis in deployment processes, particularly at Netflix, highlighting its role in gradually rolling out changes with checkpoints for monitoring. It emphasizes the benefits of this strategy in improving software deployment safety, speed, and ease, while mentioning the culture of innovation at Netflix. The author presents a detailed overview of best practices and metrics for successful canary deployments and automation in the analysis process.
Modern Operations at Scale within Viasat – How to Structure Teams and Build A...
Modern Operations at Scale within Viasat – How to Structure Teams and Build A...Atlassian 1. ViaSat implemented a DevOps model and tools like Splunk, xMatters, Jira and HipChat to improve incident response times and enable automated collaboration across teams.
2. Use cases described how full closed loop incidents could be managed from initial alert to resolution. CI/CD pipelines allowed for automated deployments and documentation updates.
3. Benefits included reducing response times from 10 minutes to 30 seconds on average, empowering on-call staff to focus on fixing issues rather than administrative tasks, and enabling seamless escalation to ChatOps teams.
Continuous integration testing 2019 08
Continuous integration testing 2019 08David Stanke The document discusses the importance of continuous integration testing in software development, emphasizing the need to shift testing processes earlier in the development cycle. It outlines various integration testing methods and their trade-offs in terms of fidelity, isolation, speed, scalability, and cost. The author encourages informed risk analysis to optimize integration testing practices while acknowledging the complexities involved with microservices architecture.
Continuous Integration Testing: Fully test your microservices application, ea...
Continuous Integration Testing: Fully test your microservices application, ea...David Stanke The document discusses the importance of continuous integration and testing in microservices development, emphasizing that early bug detection is more cost-effective. It outlines various integration testing techniques and the challenges associated with testing in production environments. The author encourages developers to assess their risk tolerance and select the best practices for their specific integration testing needs.
Canary releases & Blue green deployment
Canary releases & Blue green deploymentSQUADEX This document discusses canary releases and blue-green deployments to eliminate downtime when updating products. It introduces only reliable, tested features to small groups of live users before broad rollout. This allows the updated product to perform reliably at large scale immediately. The document also lists benefits like decreasing costs of innovation and failure while enabling A/B testing and reliable deployments. It proposes a 3-month, $60k project to implement continuous monitoring, canary releases, and blue-green deployments.
Boston DevOps Days 2016: Implementing Metrics Driven DevOps - Why and How
Boston DevOps Days 2016: Implementing Metrics Driven DevOps - Why and HowAndreas Grabner The document discusses the importance of metrics-driven DevOps, highlighting how availability, user experience, resource consumption, scalability, and performance impact overall success. It emphasizes the transition from monolithic applications to a service-oriented architecture to enhance performance and facilitate faster deployments. Key insights include the necessity of measuring success and not blindly automating processes without assessing their effectiveness.
What's Missing? Microservices Meetup at Cisco
What's Missing? Microservices Meetup at CiscoAdrian Cockcroft The document discusses key components and challenges in microservices architecture, focusing on aspects like failure injection testing, versioning, routing, and data models. It emphasizes the importance of monitoring, tracing, and the need for simplicity and reliability in distributed systems. The insights provided are based on experiences and techniques developed at Netflix, and they include various tools and practices to enhance microservices management.
Metrics Driven DevOps - Automate Scalability and Performance Into your Pipeline
Metrics Driven DevOps - Automate Scalability and Performance Into your PipelineAndreas Grabner The document discusses metrics-driven DevOps practices, emphasizing the importance of automating scalability and performance checks within the development pipeline. It highlights the challenges faced when applications do not scale effectively under increased loads and the necessity for re-architecting monolithic applications into services for better performance management. Additionally, it outlines various strategies for preventing bad code deployments through robust testing and monitoring processes, ultimately aiming for efficient app delivery and user satisfaction.
Similar to Continuous Delivery and Automated Operations on k8s with keptn (20)
Ship code like a keptn
Ship code like a keptnRob Jahn Keptn is an open-source project that provides tools to enable continuous delivery and automation for modern applications using Kubernetes. It allows developers to focus on code and DevOps teams to focus on tools rather than building custom pipelines. Keptn provides automated multi-stage delivery pipelines, automated quality gates, self-healing deployments, and enables zero-touch toolchain integration and updates. It also supports automated problem remediation in production for continuous operations. Keptn follows cloud-native design principles and provides a common way for organizations to achieve autonomous delivery and operations.
Chicago DevOps Meetup Nov2019
Chicago DevOps Meetup Nov2019Mike Villiger The document discusses the need for autonomous cloud management to reduce mean time to innovation and remediation by automating operations, deployment, monitoring, and quality using tools like Keptn. Keptn is a control plane that uses a declarative GitOps-based approach with standardized CloudEvents to define delivery and operations processes to enable continuous delivery and operations. It integrates with various tools to automate testing, deployment, monitoring and remediation through event-driven workflows.
Keptn- A Cloud-native application life-cycle orchestration.pdf
Keptn- A Cloud-native application life-cycle orchestration.pdfKnoldus Inc. The document discusses Keptn, a cloud-native application life-cycle orchestration tool that simplifies DevOps automation through a declarative approach. It addresses challenges in traditional automation pipelines such as complexity and maintainability while separating the processes defined by Site Reliability Engineers (SREs) from the tooling used by DevOps engineers. The agenda includes an overview of Keptn's features, how it works architecturally, and its integration with various tools and use cases.
Cloud Native Summit 2019 Summary
Cloud Native Summit 2019 SummaryEverett Toews The document summarizes key topics from the Cloud Native Summit conference, including:
- Distributed tracing and Zipkin, which allows visibility into request paths and troubleshooting of latency issues. Zipkin is an open source distributed tracing system.
- Production ready Kubernetes clusters on Catalyst Cloud, which provides security, high availability, and scalability for containerized applications.
- Building serverless applications at scale using services like AWS Lambda, and addressing concurrency bottlenecks when autoscaling.
- Istio service mesh, which provides control of traffic policies, authentication, and observability across distributed services through its control plane and sidecar proxy architecture.
- GitOps for infrastructure as code deployments on Open
GCP Meetup #3 - Approaches to Cloud Native Architectures
GCP Meetup #3 - Approaches to Cloud Native Architecturesnine The document discusses the evolution of application development towards cloud-native architecture, highlighting key shifts such as the move from monolithic to microservices and the adoption of serverless technologies. It emphasizes the importance of CI/CD practices for effective software delivery and outlines Google's Anthos as a hybrid solution that integrates Kubernetes management across different environments. Additionally, it presents best practices for scaling, resilience, and securing applications while leveraging modern cloud technologies.
Reliability Pipelines With Keptn Quality Gates
Reliability Pipelines With Keptn Quality GatesPaul Balogh The document provides a first look at the Keptn project, focusing on its cloud-native application lifecycle orchestration capabilities, which include automating deployment and operations. It highlights the lifecycle toolkit's use of observability, automation, and GitOps principles, while indicating a shift from the original Keptn v1 framework. The author expresses initial confusion about the project’s messaging and documentation but sees great potential for future contributions.
Observability and Orchestration of your GitOps Deployments with Keptn
Observability and Orchestration of your GitOps Deployments with KeptnAndreas Grabner Andreas Grabner discusses the challenges of operational complexity in GitOps and presents Keptn as a solution for managing cloud-native deployments through automated orchestration and observability. Keptn facilitates integration with various tools and enhances event-based sequencing for deployment and remediation. The presentation highlights the importance of application awareness and well-defined workflows, showcasing the capabilities of the Keptn lifecycle toolkit for seamless operations.
OSO Confluent GitOps Demo
OSO Confluent GitOps DemoSion Smith The document outlines a strategy for adopting Kafka as a centralized service within organizations using Kubernetes operators, emphasizing standardization and reduced operational complexities. It details the design and benefits of using Confluent for Kubernetes, including support for multi-tenancy and automation through GitOps for configuration management. The goal is to facilitate successful event streaming implementations by lowering entry barriers and boosting confidence in technology adoption.
Container and Test Automation Management Practices in TrendMicro
Container and Test Automation Management Practices in TrendMicroJen-Chieh Ko The document discusses containerization and test automation practices at Trend Micro. It describes how the company uses containers, Kubernetes, and related tools to improve their continuous delivery processes. Key practices include using TestRail for test case management and automatically syncing test cases with a robot framework; implementing blue/green deployments in Kubernetes for faster, safer releases; leveraging Kubernetes features like configmaps, secrets, and ingress for configuration management and routing; and monitoring containerized services with Prometheus and Grafana. Testing is also containerized for easier replication of environments and parallel test execution.
Dipping Your Toes Into Cloud Native Application Development
Dipping Your Toes Into Cloud Native Application DevelopmentMatthew Farina The document discusses cloud native application development, explaining its importance, core principles, and methodologies for transitioning from traditional applications. It highlights the roles of microservices, containers, and DevOps practices like CI/CD in enhancing application speed and flexibility. Additionally, various paths to achieving cloud native architecture, including migration, greenfield, and additive approaches, are outlined with practical examples and tools.
Don't Deploy Into the Dark: DORA Metrics for your K8s GitOps Deployments
Don't Deploy Into the Dark: DORA Metrics for your K8s GitOps DeploymentsAndreas Grabner The document discusses the importance of observability and orchestration in DevOps practices, specifically within Kubernetes environments using the Keptn project. It outlines key DORA metrics (deployment frequency, lead time, change failure rate, and time to restore service) and introduces the Keptn lifecycle toolkit for managing application deployment and lifecycle with a focus on automation and integration. Additionally, it emphasizes the challenges posed by GitOps and how Keptn aims to simplify operational complexity through effective orchestration and observability solutions.
Automated Deployment with Capistrano
Automated Deployment with CapistranoSumit Chhetri The document discusses the importance of embracing automated deployment, specifically using Capistrano, to simplify and improve the deployment process in software engineering. It highlights deployment goals such as ease of use, reliability, and scalability, as well as presenting Capistrano as a popular tool for remote server automation. Additionally, the document outlines the requirements and terminology associated with Capistrano, along with future trends in deployment.
Azure meetup cloud native concepts - may 28th 2018
Azure meetup cloud native concepts - may 28th 2018Jim Bugwadia This document provides an overview of cloud-native concepts and technologies like containers, microservices, and Kubernetes. It discusses how containers package applications and provide isolation using technologies like Docker. Microservices are described as a way to build applications as independent, interoperable services. Kubernetes is presented as an open-source system for automating deployment and management of containerized workloads at scale. The document outlines Kubernetes concepts like pods, deployments, services and how they help developers and operations teams manage applications in a cloud-native way.
Salvatore Incandela, Fabio Marinelli - Using Spinnaker to Create a Developmen...
Salvatore Incandela, Fabio Marinelli - Using Spinnaker to Create a Developmen...Codemotion The document presents an overview of continuous deployment with Spinnaker and Kubernetes, highlighting key components such as the Pivotal Container Service (PKS) and Kubernetes architecture. It outlines essential practices for automated application deployment, scaling, and management in a cloud-native environment. The material also emphasizes the importance of using Helm charts for software distribution and Spinnaker for continuous delivery pipelines.
Adding Security to your SLO-based Release Validation with Keptn
Adding Security to your SLO-based Release Validation with KeptnAndreas Grabner The document discusses the integration of security into release validation using Keptn, highlighting its role in automating DevOps tasks such as deployment and performance testing. It provides insights into the challenges of managing CI/CD pipelines and emphasizes Keptn's capability to reduce complexity by separating processes, tools, and configurations. The content includes examples of automating performance sequences and security remediation within a cloud-native environment, encouraging the use of best practices for service-level objectives.
Gitlab ci e kubernetes, build test and deploy your projects like a pro
Gitlab ci e kubernetes, build test and deploy your projects like a prosparkfabrik This document discusses using GitLab CI and Kubernetes together for continuous integration, delivery, and deployment. It provides an overview of Kubernetes and GitLab, describes how to set up a GitLab runner using the Kubernetes executor, and provides an example YAML configuration. It also covers continuous deployment workflows, running GitLab on Kubernetes, and some tips and tricks as well as techniques for troubleshooting Kubernetes and GitLab CI/CD pipelines.
Sergio Seabra - Red Hat - OSL19
Sergio Seabra - Red Hat - OSL19marketingsyone This document discusses various Red Hat technologies for enabling cloud native applications and GitOps workflows. It introduces concepts like Knative for serverless workloads, Istio for microservices control, CodeReady Workspaces for developers, and CodeReady Containers for local development. Examples are given of technologies like Quarkus and GraalVM for optimized Java applications, and Tekton and OpenShift Pipelines for CI/CD automation. References are also provided for further exploring these Red Hat technologies.
Automated Deployments
Automated DeploymentsMartin Etmajer The document outlines the principles and practices of automated deployments, focusing on the transition from continuous integration to continuous delivery. It emphasizes the benefits of automation, such as repeatability, reduced risks during deployments, and integration into build pipelines, while also discussing different deployment solutions like agent-based and agentless methods. Additionally, it introduces Ansible as an automation tool, highlighting its core concepts, including inventories and playbooks.
Kubo (Cloud Foundry Container Platform): Your Gateway Drug to Cloud-native
Kubo (Cloud Foundry Container Platform): Your Gateway Drug to Cloud-nativecornelia davis The document discusses how Kubo can be used as a gateway to running cloud-native workloads. It outlines different types of workloads like code developed internally which may change frequently or code from third parties. For internally developed code, Kubo allows maintaining existing processes while deploying container images instead of infrastructure. For external code and data-centric workloads, Kubo provides benefits like health management, multi-cloud support, and operating system/Kubernetes upgrades without affecting applications. The document calls developers to run workloads on Cloud Foundry Container Runtime and share experiences.
Kubo (Cloud Foundry Container Platform): Your Gateway Drug to Cloud-native
Kubo (Cloud Foundry Container Platform): Your Gateway Drug to Cloud-nativeVMware Tanzu The document discusses Kubo, a cloud-native platform designed to help organizations manage their workloads more efficiently and effectively. It highlights the transition from traditional Infrastructure as a Service (IaaS) to cloud-native architectures, utilizing containers, microservices, and event-driven functions to optimize deployments and developer productivity. Key considerations include maintaining operational efficiency, using standardized images, and implementing effective health management and logging strategies within Kubernetes environments.
Ad
More from Andreas Grabner (13)
KCD Munich - Cloud Native Platform Dilemma - Turning it into an Opportunity
KCD Munich - Cloud Native Platform Dilemma - Turning it into an OpportunityAndreas Grabner The document discusses the importance of platform engineering in improving software delivery by addressing expertise bottlenecks and enabling organizations to become more efficient and productive. It emphasizes the creation of internal developer platforms (IDPs) that simplify the development process, encourage self-service, and measure success through various KPIs. Key takeaways include starting with a minimum viable product, leveraging community wisdom, and ensuring platform observability.
OpenTelemetry For GitOps: Tracing Deployments from Git Commit to Production
OpenTelemetry For GitOps: Tracing Deployments from Git Commit to ProductionAndreas Grabner The document discusses the use of OpenTelemetry for improving GitOps workflows in Kubernetes, addressing challenges like unmeasurable change impact, chaotic pipelines, and observability tool sprawl. It highlights how Keptn can provide app-aware change traceability, enforce delivery checks natively in Kubernetes, and unify observability data access. The goal is to enhance the deployment process through event-driven delivery tasks and standardized observability metrics.
DevOps Transformation at Dynatrace and with Dynatrace
DevOps Transformation at Dynatrace and with DynatraceAndreas Grabner The document outlines Dynatrace's DevOps transformation journey, highlighting their transition from traditional software deployment methods to continuous innovation through automation and cultural shifts. Key achievements include significantly increased release frequency and deployment velocity, enhanced collaboration among teams, and improved product quality and stability. The document also discusses challenges faced, strategic solutions implemented, and the importance of integrating customer feedback into the development process.
Top Java Performance Problems and Metrics To Check in Your Pipeline
Top Java Performance Problems and Metrics To Check in Your PipelineAndreas Grabner The document discusses performance optimization techniques for software applications, emphasizing the importance of monitoring and analyzing key metrics like response time, resource usage, and SQL query performance. It highlights common performance pitfalls such as excessive logging, data loading inefficiencies, and architectural mistakes in migrating to microservices. Various tools and strategies, including Dynatrace, are suggested for identifying and addressing performance issues effectively.
Four Practices to Fix Your Top .NET Performance Problems
Four Practices to Fix Your Top .NET Performance ProblemsAndreas Grabner The document outlines best practices for addressing performance issues in .NET applications using Dynatrace. It includes tips on monitoring CPU, memory, and thread hotspots, as well as common mistakes in instrumentation and database execution analysis. Additionally, it provides information on community engagement and learning resources related to Dynatrace products.
OOP 2016 - Building Software That Eats The World
OOP 2016 - Building Software That Eats The WorldAndreas Grabner The document discusses the shift towards service-oriented architectures in software development, emphasizing the need for metrics-driven deployment processes. It highlights the importance of scalability, automation, and performance monitoring to improve load times and reduce technical debt. Additionally, it covers the organizational changes necessary to adapt to agile methodologies and the consolidation of infrastructure for efficiency.
Docker/DevOps Meetup: Metrics-Driven Continuous Performance and Scalabilty
Docker/DevOps Meetup: Metrics-Driven Continuous Performance and ScalabiltyAndreas Grabner The document discusses the importance of application quality metrics in the development pipeline, highlighting various case studies and metrics-driven approaches to DevOps. It emphasizes the need for monitoring and analyzing backend performance to avoid common pitfalls such as poor resource management and bad architectural decisions. Key takeaways include focusing on measurable quality metrics, continuous integration improvements, and avoiding assumptions about system performance.
JavaOne 2015: Top Performance Patterns Deep Dive
JavaOne 2015: Top Performance Patterns Deep DiveAndreas Grabner The document discusses performance optimization in web applications, emphasizing the importance of monitoring and analyzing frontend and backend performance to identify common issues such as slow load times and excessive database calls. It provides various tools and metrics for tracking performance, as well as practical tips for avoiding architectural mistakes and improving resource usage during development. The content encourages developers to utilize performance metrics as quality gates in continuous integration processes to ensure overall application effectiveness.
Application Quality Gates in Continuous Delivery: Deliver Better Software Fas...
Application Quality Gates in Continuous Delivery: Deliver Better Software Fas...Andreas Grabner The document discusses best practices for application quality in software deployments, emphasizing the importance of metrics and learning from past mistakes. It provides examples of poor performance in web and Java deployments and outlines strategies to improve quality, such as avoiding blind automation and integrating comprehensive metrics into the CI/CD pipeline. Key takeaways include focusing on resource management, monitoring third-party calls, and addressing architectural issues to enhance application performance.
Deploy Faster Without Failing Faster - Metrics-Driven - Dynatrace User Groups...
Deploy Faster Without Failing Faster - Metrics-Driven - Dynatrace User Groups...Andreas Grabner The document discusses the evolution from waterfall to agile methodologies in DevOps, highlighting the importance of minimizing cycle times and increasing deployment frequency for high performance. It emphasizes metrics-based decisions to enhance reliability and efficiency while addressing challenges such as technical debt and quality assurance. Additionally, the text outlines strategies like automation, collaborative environments, and continuous quality integration as key components of modern DevOps practices.
BTD2015 - Your Place In DevTOps is Finding Solutions - Not Just Bugs!
BTD2015 - Your Place In DevTOps is Finding Solutions - Not Just Bugs!Andreas Grabner The document discusses the importance of minimizing cycle time and improving deployment processes in software development, highlighting strategies such as automation and performance testing. It emphasizes learning from failures, sharing performance expertise, and ensuring proper testing to maintain quality while deploying rapidly. The insights also include metrics for measuring application performance and the significance of collaboration among developers and testers.
Mobile User Experience: Auto Drive through Performance Metrics
Mobile User Experience: Auto Drive through Performance MetricsAndreas Grabner The document discusses strategies for minimizing feature cycle time and enhancing mobile user experience by deploying software rapidly and efficiently, with examples of metrics and practices from successful organizations. It emphasizes the importance of automated processes, continuous deployment, and the role of metrics-based decision-making in reducing outages and improving performance. Key challenges include faster deployment while ensuring reliability, learning from failures, and effective use of 3rd party components.
HSPS 2015 - SharePoint Performance Santiy Checks
HSPS 2015 - SharePoint Performance Santiy ChecksAndreas Grabner The document provides an overview of key performance sanity checks for SharePoint, including 7 steps to check SharePoint health, how to analyze SharePoint usage, and how to identify slow pages. It discusses checking end user health, site health, system health, IIS health, AppPool health, SQL and service health, and web parts. The document also covers avoiding common deployment mistakes and provides a real-life example of troubleshooting a slow page load for a frustrated user.
Ad
Recently uploaded (20)
Humans vs AI Call Agents - Qcall.ai's Special Report
Humans vs AI Call Agents - Qcall.ai's Special ReportUdit Goenka Humans vs Agentic AI Cost Comparison: Cut 85% Support Costs
TL;DR: Agentic AI crushes human costs in L1/L2 support with 85% savings, 300% efficiency gains, and 90%+ success rates.
Your CFO just asked: "Why spend $2.3M annually on L1 support when competitors automated 80% for under $200K?" The humans vs agentic AI cost debate isn't theoretical - it's happening now.
Real Cost Breakdown:
- India L1/L2 Agent: ₹6,64,379 ($8,000) annually (full cost)
- US L1/L2 Agent: $70,000 annually (loaded cost)
- Qcall.ai Agentic AI: ₹6/min ($0.07/min) = 85% savings
Game-Changing Results:
- 47 human agents → 8 agents + AI system
- Operating costs: $2.8M → $420K (85% reduction)
- Customer satisfaction: 78% → 91%
- First call resolution: 72% → 94%
- Languages: 2-3 → 15+ fluently
Why Agentic AI Wins:
- Human Limitations: 8hrs/day, 1-2 languages, 30-45% attrition, mood-dependent, 6-12 weeks training
- Qcall.ai Advantages: 24/7 availability, 97% humanized voice, <60 second response, intelligent qualification, seamless handoff
Industry Impact:
- E-commerce: 82% cost reduction
- Healthcare: 90% appointment automation
- SaaS: 23% satisfaction improvement
- Financial: 95% inquiry automation
Implementation:
- Setup: 2-5 days vs 6-12 weeks hiring
- ROI: Break-even in 3 months
- Scaling: Instant global expansion
Competitive Gap:
- Early Adopters: 85% cost advantage, superior metrics, faster expansion
Late Adopters: Higher costs, limited scalability, compounding disadvantage
Similar automation patterns emerge across industries.
Marketing teams use autoposting.ai for social media automation - same human-AI collaboration model driving L1/L2 transformation.
"We reduced support costs by 78% while improving satisfaction by 31%. ROI was immediate and keeps compounding." - COO, Global SaaS Company
Getting Started:
Calculate current L1/L2 costs
Assess repetitive tasks
Request Qcall.ai demo
Plan 20% pilot
Bottom Line: Companies avoiding this shift hemorrhage millions while competitors scale globally with fraction of costs. The question isn't whether agentic AI will replace routine tasks - it's whether you'll implement before competitors gain insurmountable advantage.
Ready to transform operations? This reveals complete cost analysis, implementation strategy, and competitive advantages.
Heat Treatment Process Automation in India
Heat Treatment Process Automation in IndiaReckers Mechatronics Automate your heat treatment processes for superior precision, consistency, and cost savings. Explore solutions for furnaces, quench systems. Heat treatment is a critical manufacturing process that alters the microstructure and properties of materials, typically metals, to achieve desired characteristics such as hardness, strength, ductility, and wear resistance.
Why Edge Computing Matters in Mobile Application Tech.pdf
Why Edge Computing Matters in Mobile Application Tech.pdfIMG Global Infotech This PDF explores the critical role of edge computing in modern mobile application technology. Learn how edge enhances app speed, reduces latency, improves data privacy, and supports real-time performance. Ideal for developers, tech strategists, and mobile innovators looking to stay ahead in the evolving mobile ecosystem.
How Automation in Claims Handling Streamlined Operations
How Automation in Claims Handling Streamlined OperationsInsurance Tech Services Claims processing automation reduces manual work, cuts errors, and speeds up resolutions. Using AI, RPA, and OCR, it enables faster data handling and smoother workflows—boosting efficiency and customer satisfaction. Visit https://www.damcogroup.com/insurance/claims-processing-automation for more details!
ERP Systems in the UAE: Driving Business Transformation with Smart Solutions
ERP Systems in the UAE: Driving Business Transformation with Smart Solutionsdheeodoo ERP solutions are driving innovative change for businesses across the UAE through improved efficiency, reduced operational costs, and provide real-time visibility of operational data. By offering native Arabic language support, VAT compliance, and some level of cloud readiness, ERP solutions also supports and are consistent with the initiative for Smart Dubai 2030. Odoo is an example of a flexible & scalable solution. If you're looking for expert support with implementation contact Banibro. www.banibro.com
Simplify Task, Team, and Project Management with Orangescrum Work
Simplify Task, Team, and Project Management with Orangescrum WorkOrangescrum Streamline project workflows, team collaboration, and time tracking with orangescrum work, your all-in-one tool for smarter and faster project execution.
Zoho Creator Solution for EI by Elsner Technologies.docx
Zoho Creator Solution for EI by Elsner Technologies.docxElsner Technologies Pvt. Ltd. Working with Elsner’s Zoho Creator experts, Educational Initiatives implemented a custom asset management system that: Our Zoho Creator solutions have made real changes across the company, and each team has felt the difference.
MOVIE RECOMMENDATION SYSTEM, UDUMULA GOPI REDDY, Y24MC13085.pptx
MOVIE RECOMMENDATION SYSTEM, UDUMULA GOPI REDDY, Y24MC13085.pptxMaharshi Mallela Movie recommendation system is a software application or algorithm designed to suggest movies to users based on their preferences, viewing history, or other relevant factors. The primary goal of such a system is to enhance user experience by providing personalized and relevant movie suggestions.
Azure AI Foundry: The AI app and agent factory
Azure AI Foundry: The AI app and agent factoryMaxim Salnikov Discover how Azure AI Foundry is transforming the way organizations innovate and operate. This session explores the pivotal role of AI in reshaping business processes, enhancing employee experiences, and redefining customer engagement. Attendees will gain insights into the strategic value of AI investments, including the measurable returns and the growing momentum behind generative AI experimentation.
The talk introduces the emerging paradigm of agentic AI - intelligent agents that are revolutionizing how we build, manage, and interact with software. Through real-world examples, the session demonstrates how Azure AI Foundry empowers teams to design, customize, and scale AI applications and agents, unlocking new levels of efficiency and creativity across industries.
Best MLM Compensation Plans for Network Marketing Success in 2025
Best MLM Compensation Plans for Network Marketing Success in 2025LETSCMS Pvt. Ltd.
Discover the top MLM compensation plans including Unilevel, Binary, Matrix, Board, and Australian Plans. Learn how to choose the best plan for your business growth with expert insights from MLM Trees. Explore hybrid models, payout strategies, and earning potential.
Learn more: https://www.mlmtrees.com/mlm-plans/
Download Adobe Illustrator Crack free for Windows 2025?
Download Adobe Illustrator Crack free for Windows 2025?grete1122g COPY & PASTE LINK 👉👉👉 https://click4pc.com/after-verification-click-go-to-download-page/
Adobe Illustrator CC Crack will make your illustration level upgrade by moving toward real modification purpose using adobe pro tools there ..
CodeCleaner: Mitigating Data Contamination for LLM Benchmarking
CodeCleaner: Mitigating Data Contamination for LLM Benchmarkingarabelatso The pdf version of "CodeCleaner: Mitigating Data Contamination for LLM Benchmarking" presented in Internetware 2025.
declaration of Variables and constants.pptx
declaration of Variables and constants.pptxmeemee7378 Rules of declaration of variables and constants
Streamlining CI/CD with FME Flow: A Practical Guide
Streamlining CI/CD with FME Flow: A Practical GuideSafe Software Join us as we explore how to deploy a fault-tolerant FME Flow installation using FME Flow’s IaC templates alongside Terraform, AWS, and GitHub in a CI/CD workflow. This session will also cover how to leverage FME’s CI/CD capabilities for FME Flow upgrades and FME object migration between different environments, ensuring seamless automation and scalability.
Why Every Growing Business Needs a Staff Augmentation Company IN USA.pdf
Why Every Growing Business Needs a Staff Augmentation Company IN USA.pdfmary rojas U.S. staff augmentation companies excel at providing IT professionals with expertise in development, cybersecurity, AI, and more. Whether you need to fill a short-term gap or enhance your team’s capabilities long-term, these firms deliver pre-vetted talent tailored to your tech stack and industry. With an understanding of both global technologies and local compliance, U.S.-based IT staff augmentation bridges the gap between talent shortage and project demand efficiently.
Digital Transformation: Automating the Placement of Medical Interns
Digital Transformation: Automating the Placement of Medical InternsSafe Software Discover how the Health Service Executive (HSE) in Ireland has leveraged FME to implement an automated solution for its “Order of Merit” process, which assigns medical interns to their preferred placements based on applications and academic performance. This presentation will showcase how FME validates applicant data, including placement preferences and academic results, ensuring both accuracy and eligibility. It will also explore how FME automates the matching process, efficiently assigning placements to interns and distributing offer letters. Beyond this, FME actively monitors responses and dynamically reallocates placements in line with the order of merit when offers are accepted or declined. The solution also features a self-service portal (FME Flow Gallery App), enabling administrators to manage the entire process seamlessly, make adjustments, generate reports, and maintain audit logs. Additionally, the system upholds strict data security and governance, utilising FME to encrypt data both at rest and in transit.
Y - Recursion The Hard Way GopherCon EU 2025
Y - Recursion The Hard Way GopherCon EU 2025Eleanor McHugh In most modern programming languages, including Go, it's possible for a function to call itself recursively. It's such a mainstream technique that we've come to take it for granted.
But what if functions couldn't call themselves?
There's a branch of mathematics called Combinatorics which answers just these kinds of questions, and this presentation takes these ideas and phrases them in Go to teach a deeper view of computation through the medium of code.
Continuous Delivery and Automated Operations on k8s with keptn
- 1. What is Andreas Grabner, Dynatrace @grabnerandi @keptnProject https://keptn.sh https://github.com/keptn
- 2. Confidential 2 That is why we are building Because cloud native delivery and operations is a BIG challenge for enterprises! Cloud Native
- 3. Confidential 3 MTTI Mean Time to Innovation MTTR Mean Time to Remediate 4.8 days 4 hours ~ 10min 12.5 days 2 days ~ 1 hour The reality and evidence supports it! https://dynatrace.ai/acsurvey Only < 5% is „Cloud Native“
- 4. Confidential 4 Quote: “Pipelines seem to be becoming our new future un-managable legacy code!“ First: solves the Continuous Delivery Problem!
- 5. Confidential 5 Quote: “We spend more time in manual communicaton than remediating issues“ Second: has Continuous Operations at its Core! ENGAGE TRIAGE FIND & ASSEMBLE RESOLVE RESTORE MANUAL COMMUNICATION MANUAL COMM Before After RESTORERESOLVE NUMBER OF ISSUES CURRENT STATE: mostly manual DESIRED STATE: mostly automated
- 6. 6 To Sum Up: Why we are building Keptn Continuous Delivery - and even more Continuous Operations - is an area where many enterprise struggle to implement proper solutions. Many approaches today are brittle, error-prone and hard to maintain Most approaches today
- 7. 8 Mission Control “Automated Operations” = Day 2 Ops Launch Control “Continuous Deployment” = Day 1 Ops Keptn is a Control Plane for Automate Delivery and Operations Event-driven runbook automation Productionproblemscan beautomaticallyremediatedin real-timebyexecutingrunbooksthatrequirenomanual intervention. Self-healing blue/green deployments Deploymentsthatfollowthe“Operationsas Code” paradigmautomaticallyremediateproblemsandget yourdeploymentpipelineworkingagain inundera minute. Automated multistage unbreakable delivery pipelines GitOps-enableddeliverypipelineswithautomated qualitygates supportautomatedtestingandmonitoring- as-a-service. Declarative Delivery (Shipyard) Declarative Tooling (Uniform) Declarative SLI / SLO / SLA
- 8. 9 Keptn architecture Platform keptn cli api eventbroker REST API bridge mongodb- datastore gitconfiguration-service internal- keptn- services distributor distributor keptn services Continuous Delivery Container Registry Operations Automation AIOps GitOps Test Automation ChatOps Data Provider dev staging production keptnNamespaces: distributor
- 9. 10 Config ChatOps IT Autom Deploy Test Observe One-Line Installation: $ keptn install
- 10. 11 Config ChatOps IT Autom Deploy Test Observe Zero-Touch Toolchain Integration: $ keptn wear uniform uniform.yaml
- 11. 12 Config ChatOps IT Autom Deploy Test Observe Re-Think Pipelines: $ keptn create project keptn-sample shipyard.yaml S T A G I N G P R O D DirectUpdateC D Blue/GreenUpdateC D
- 12. 13 Config ChatOps IT Autom Deploy Test Observe Zero-Touch Cloud Native Services: $ keptn onboard service myservice [xxx.yaml] S T A G I N G P R O D DirectUpdateC D Blue/GreenUpdateC D PLACEHOLDER PLACEHOLDER
- 13. 14 Config ChatOps IT Autom Deploy Test Observe Automated Multi-Stage Delivery: $ keptn new artifact myservice:1.0.0 S T A G I N G P R O D ScoreDirect PerformanceUpdate Promote?C D T O ScoreBlue/GreenUpdate Keep?C D T O PLACEHOLDER PLACEHOLDER 1.0.0 1 1 90 / 100 1.0.0 1 1 1 75 / 100 P R O M O T E K E E P
- 14. 15 A Quick word on Pitometer: Automated Deployment Validation Metric Source & Query Grading Details & Metric Score Pitometer Specfile Total Scoring Objectives 2GB Allocated Bytes (from Prometheus) > 2GB: 0 Points < 2GB: 20 Points 5% 2% < 2%: 0 Points < 5%: 10 Points > 5%: 20 Points Conversion Rate (Dynatrace) GraderSource If value: 3GB Score: 0 If value: 3.9% Score: 10 Total Score: 10
- 15. 16 Config ChatOps IT Autom Deploy Test Observe Automated Quality Gates: $ keptn new artifact myservice:2.0.0 S T A G I N G P R O D ScoreDirect PerformanceUpdate Promote?C D T O ScoreBlue/GreenUpdate Keep?C D T O 1.0.0 1 1 45 / 100 1.0.0 1 1 1 2.0.0 2 2 A B O R T
- 16. 17 Config ChatOps IT Autom Deploy Test Observe Self-Healing Blue/Green Deployments: $ keptn new artifact myservice:3.0.0 S T A G I N G P R O D ScoreDirect PerformanceUpdate Promote?C D T O ScoreBlue/GreenUpdate Keep?C D T O 1.0.0 1 1 85 / 100 1.0.0 1 1 1 2.0.0 2 2 3.0.0 3 3 3.0.0 3 3 3 80 / 100 P R O M O T E R E V E R T
- 17. 18 Config ChatOps IT Autom Deploy Test Observe Zero-Touch Toolchain Updates: $ keptn update uniform <+neo,+end2end,+spinnaker> S T A G I N G P R O D ScoreDirect PerformanceUpdate Promote?C D T O ScoreBlue/GreenUpdate Keep?C D O 1.0.0 1 1 1.0.0 1 1 1 2.0.0 2 2 3.0.0 3 3 End2EndT
- 18. 19 Config ChatOps IT Autom Deploy Test Observe Mastering Continuous Delivery: $ keptn new artifact myservice:4.0.0 S T A G I N G P R O D ScoreDirect PerformanceUpdate Promote?C D T O ScoreBlue/GreenUpdate Keep?C D O 1.0.0 1 1 1.0.0 1 1 1 2.0.0 2 2 3.0.0 3 3 4 4 4 End2EndT 4.0.0 4.0.0 4 4 95 / 100 90 / 100 K E E P P R O M O T E
- 19. 20 4 4 Config ChatOps IT Autom Deploy Test Observe Self-Healing Production: $ keptn new problem <Services, Root Cause> P R O D Evaluate Decide Act Notify 4 Escalate 4 4
- 20. 21 Advantages of the Keptn approach • Uniquely combine delivery and operations automation • Separation of the what (shipyard) from the how (uniform) • Change a process or exchange a tool in minutes • GitOps and cloud-native best practices out-of-the-box • Easy extensibility via event-based model • Declarative approach vs. copy & paste pipelines
- 21. Confidential 22 MTTI = Mean Time to Innovation MTTR Mean Time to Remediate 4.8 days 4 hours ~ 10min 12.5 days 2 days ~ 1 hour We are building keptn to re-shape this reality GROW this number!
- 22. Demo: Should be done by now
- 23. 24Confidential • https://github.com/keptn/community • @keptnproject • [email protected] • keptn.slack.com • Biweekly communitymeetings • Zoom https://dynatrace.zoom.us/j/578828410 • Notes https://tinyurl.com/keptn-meeting-notes Jointhecommunity
- 24. What is Andreas Grabner, Dynatrace @grabnerandi @keptnProject https://keptn.sh https://github.com/keptn
Editor's Notes
- #4: We did a survey with most of our attendees at PERFORM 2019 in Las Vegas – asking them questions around their cloud native projects. Please take the URL and do the survey as well! I looked at two metrics that tell me how mature an organization is: MTTI: how long does it take to get a newly built and already tested feature from pre-prod into production? 1 hour was the benchmark that our CTO gave us internally! MTTR: how long does it take to remediate any problems that may come up? This should be in the range of minutes, not hours or days! The shocking truth of this survey was that only 5% of our customers are reaping the benefits of new technology. The majority is in the bottom left half where they would have assumed that new technology gets them to the top right „magic quadrant“
- #5: Many teams we spoken with build their own Deployment Pipelines: Combination of OpenSource & Commercial Tools for Deployment Automation! Testing Pipelines: Combination of OpenSource & Commerical Tools for Test Execution Quality Gates: Most often done manual. Some are investing in automated validation! Auto Remediation: Mostly done manual with a trend towards simply remediation actions
- #23: Numbers based on our survey – https://dynatrace.ai/acsurvey