Cloud Collective

Let's talk about serverless CI/CD services provided by the Cloud Providers.
Scenario 1: You are working in a startup and need to implement extensible and secure CI/CD pipelines but don't want to invest time and money on the self-hosted one. You are already using a Cloud Service Provider (AWS, Azure, or GCP) or using GitHub for version control. How can you utilize managed CI/CD services provided by them?

Scenario 2: You have been running Jenkins or other self-hosted CI server for a while. Now, you want to explore if the Cloud Managed CI services have matured enough to relieve you of the pains of managing a build cluster yourselves.

In this webinar, we will review what are those options. How to configure

Topics:
1. What are these managed CI/CD services from AWS, Azure, GCP, and GitHub?
2. How to configure each one of them?
3. Comparison of all 4 among each other.
4. Pros and Cons of each vs. a self-hosted one

Speaker:
Varun Nandu: Software Engineer, Egen

Zoom Webinar link will be added within 2 days of the event.

Let's understand the role of service mesh in Kubernetes world and find out what is Istio, it's features, and whether you actually need it?

Scenario 1: You have been using Kubernetes for the last few years and now your distributed platform has become complex. You now have 100s of microservices communicating over http and tcp. You are now looking into abstracting traffic management, service-service security (mTLS, authN, authZ) and telemetry out of the services to a separate layer aka Service Mesh.

Scenario 2: You have heard about Service Mesh for a while and want to understand features, complexities, configurations before jumping on to it completely.

Kubernetes is a complex platform. It offers basic levels of service discovery and with few simple integrations you can achieve basic telemetry, resource monitoring, ingress gateways, TLS cert management etc. But when you start running a large number of services (> 50), you want a mature in-cluster component that can do all these for you in a more scalable way. That's where a service mesh comes into picture. But remember: running a service mesh within Kubernetes will feel like running a platform within a platform. Setup and operations are complex. Let's discuss.

This is first of the two part series. This is a beginner level session.
Topics:
1. What is a Service Mesh?
2. Do I need a Service Mesh if I am already using Kubernetes?
3. What is Istio and where does it help?
4. Take aways.
5. Q&A

Speaker:
Praveen Salitra: Director of Technology, Egen
Praveen is a Cloud Architect and the Director of Technology at Egen. Over the last 10 years, he has been involved “hands-on” on multiple projects developing distributed platforms, microservices, APIs, data pipelines, user facing apps, and infrastructure automation. He has led technical teams in Industrial IoT, Healthcare, and Retail solutions for various startups and enterprises. He has trained more than 8000 engineers on modern technical stack, including JavaScript frameworks, Java, AWS, Azure, Docker, and Kubernetes. In the last few years, he has started public speaking and advising companies on the Cloud-Native architectures. https://praveen.salitra.io

Zoom Webinar link will be shared within 2 days prior to the event.

In this second part of the series, we learn how to install and configure Istio and explore it's features with a hands-on demo.

Scenario 1: You have been using Kubernetes for the last few years and now your distributed platform has become complex. You now have 100s of microservices communicating over http and tcp. You are now looking into abstracting traffic management, service-service security (mTLS, authN, authZ) and telemetry out of the services to a separate layer aka Service Mesh.

Scenario 2: You have heard about Service Mesh for a while and want to understand features, complexities, configurations before jumping on to it completely.

Kubernetes is a complex platform. It offers basic levels of service discovery and with few simple integrations you can achieve basic telemetry, resource monitoring, ingress gateways, TLS cert management etc. But when you start running a large number of services (> 50), you want a mature in-cluster component that can do all these for you in a more scalable way. That's where a service mesh comes into picture. But remember: running a service mesh within Kubernetes will feel like running a platform within a platform. Setup and operations are complex. Let's discuss.

This is second of the two part series. This is an advance level session.
Topics:
1. How to install and configure Istio?
2. A hands-on demo.
4. Take aways.
5. Q&A

Speaker:
Praveen Salitra: Director of Technology, Egen
Praveen is a Cloud Architect and the Director of Technology at Egen. Over the last 10 years, he has been involved “hands-on” on multiple projects developing distributed platforms, microservices, APIs, data pipelines, user facing apps, and infrastructure automation. He has led technical teams in Industrial IoT, Healthcare, and Retail solutions for various startups and enterprises. He has trained more than 8000 engineers on modern technical stack, including JavaScript frameworks, Java, AWS, Azure, Docker, and Kubernetes. In the last few years, he has started public speaking and advising companies on the Cloud-Native architectures. https://praveen.salitra.io

Zoom Webinar link will be shared within 2 days prior to the event.