KubeCon + CloudNativeCon | Open Source Summit China 2019

We're missing opportunities to improve and optimize the software integration process. This lack of focus can decrease code quality, mask incompatibility between components, and frustrate users that seek reliable release cadence.

In this talk, two creative engineers will tell the story of how their team built ‘Release Engineering as a Service’ in order to tackle slow release cycles and endless bug reports.

The aim of the talk is to help open source contributors understand how small changes to their integration process can have an enormous impact on how fast their favorite features get delivered.

Maryam and Ramya will discuss:
- What is a release engineering team in the context of Kubernetes?
- How should we use CI/CD to integrate software consistently?
- How can we improve feedback cycles using automation, parallelization, and reutilization?

With the advancement in cloud service capabilities such as databases, cognitive services, and messaging queues, application architecture is extending to include not only code but also managed cloud services. In this talk we will examine the unique challenges in deploying and managing cloud integrated applications.

Topics will include:

- How to deploy and manage code and cloud services as a single unit
- Managing connection strings and keys between application and cloud services
- Comparison of emerging application deployment technology such as the Kubernetes Service Catalog, Terraform, and Cloud Native Application Bundles (CNAB)

The goal of this talk is to not only consider how cloud integrated applications change deployment and management practices, but to also take a hands on look at the emerging technology that facilitates these deployments.

900 character max
One of the excuses of developers for not writing tests is that they don't know how or that it is too much work. Real-world end-to-end (E2E) testing on Kubernetes was indeed difficult outside of core Kubernetes itself, because of limitations and dependencies of the Kubernetes E2E framework. Not anymore! Starting with 1.13, the framework can be used by outside projects. Several projects have already started to use the framework (Kubernetes Node Feature Discovery, Intel CSI storage drivers).

The talk will present the recent changes in the E2E framework (like splitting out cloud provider dependencies, clarifying parameter handling, enhancing configuration and external file support) and explain how to use it, using a real CSI driver as example.

Member from the Jenkins Cloud Native SIG will introduce Serverless Jenkins in the Cloud Native era and the technologies behind it (including Kubernetes, Prow, Tekton, etc.)

In this talk we will discuss how to use the Knative Pipeline project to configure and run CI/CD pipelines for your Kubernetes applications. You’ll be able to manage and observe CI/CD objects with kubectl the same way that you would interact with Kubernetes resources. We will dive into the major features Knative Pipeline supports and how to use them. This talk will include
- How to build pipelines.
- How to run one-off tasks.
- How to leverage the K8s ecosystem while running Pipelines for diagnosis and observability.
- Demonstrate a couple of use cases like an application developer pushing source code -> building images -> deploying application on their cluster without any external CI/CD resource.

This talk proposal is also submitted to Kubecon Europe 2019.

Many companies and organizations have adopted CI/CD processes in order to help deliver applications running on Kubernetes quickly, transparently, and with automated tests. While this is a desirable goal, it gets more complex when developing a management layer on top of k8s, especially when both images and helm charts are involved. In developing IBM Cloud Private, we have implemented a CI/CD process that automates promotion through a series of quality gates where we 1) Ensure that all charts (43) and images (135) are in sync across three supported architectures 2) Deploy instances of ICP clusters with different topologies, management services, and infrastructure 3) Run automated and manual functional and security regression tests against those clusters. Since implementation, have we have been able to iterate more quickly by discovering issues earlier in the development process.