Have you ever found yourself in a situation where all your service mesh services are running in Kubernetes, and now you need to expose them to the outside world securely and reliably? Ingress management is essential for your configuration and operations when exposing services outside of a cluster. You need to take care of the authentication, observability, encryption and integration with other third-party vendors alongside other policies.
Disaster Recovery (DR) is crucial to every organization. Business continuity is important whether you live in an area prone to natural disasters or need to prepare for unseen events like a data center outage. But how do you ensure that the changes behind the scenes don’t impact the end user? Red Hat Ansible Automation Platform (AAP) is the automation tool of choice for many enterprises.
Event Hooks is a new Kong Enterprise feature launched in the Kong Gateway 2.5 Release. This feature sends you notifications when certain events happen on your Kong Gateway deployment. Kong Gateway listens for events, like routes, services, consumers, certificates, plugins, workspaces and RBAC roles created, updated or removed. You can also create or extend Kong Plugins and add the Event Hooks functionality for custom use cases.
In part 1 of this series on Kubernetes, we discussed how companies like VMware offer the necessary tools to launch, monitor, create and destroy virtual machines. In this post, we review how – much like virtual machines – containers need to be created, monitored, destroyed and relaunched to account for the health of the physical or virtual machines on which they run.
In the last blog post, we discussed the need for both speed and quality for your API delivery and how APIOps can help achieve both. In this part of our blog post series, we’ll walk through what the API lifecycle looks like when following APIOps. We’re still following the best practice we’ve established in the industry over the years, but what you’re going to see is that the processes we follow at each step of the API lifecycle – and between each step – have changed.
In part 1 of this series, we started a journey from the planet-spanning infrastructure layer to what happens inside a single Kong worker, similar to an office building in complexity. In this second part, we’ll dive a bit deeper—we’ll see who the occupants of that office building are and the kind of life they live.
Today, we’re thrilled to announce the general availability of Kong Ingress Controller 2.0 (KIC) – the most robust, scalable, and extensible version of our Kubernetes Ingress Controller to date. This is a major milestone both for the KIC product as well as for the Kong community as a whole. In addition to KIC 2.0’s new features, it also sets the foundation for us to more rapidly improve the user experience and add more capabilities.
Today, Application Programming Interfaces (APIs) and microservices are the de-facto standard for building and connecting modern applications. APIs are no longer just a delivery mechanism but have become the product itself. API lifecycle management refers to the comprehensive, step-by-step process of planning, developing, implementing, testing, and versioning an API.
These days, a lot of companies are moving towards cloud native applications and declarative configurations. This is also true for the traditional API gateways (e.g., MuleSoft, Axway, etc). Customers are looking for new technologies which fit better in their cloud environments and also are faster and cheaper. The main challenge here is how to migrate the existing APIs to the new platform.
In this episode of Kongcast, I had the pleasure of speaking with Viktor Farcic, developer advocate at Upbound, about why empowering developers to manage the full application lifecycle helps app development teams increase efficiency.
In this three-part blog series, we examine the critical role Kubernetes plays in shaping the future of infrastructure, including the rise of containers and Kubernetes. The first in the series covers Next-Generation Application Development. The second covers the Next Frontier: Container Orchestration. And the third covers How Kubernetes Gets Work Done.
If you could clone yourself, you could get your work done a lot faster, right? And that would free up time for you to pursue new projects and advance your career. It’s an idea that Kong Vice President of Products Reza Shafii discussed recently as part of Destination: Automation, a free digital event that explored ways organizations can embrace automation to make applications and underlying technology stacks more efficient, secure and resilient.
Continuous integration and continuous deployment—known colloquially as CI/CD—are essential strategies for building modern software applications. The goal of these processes is to foster a culture of continuous updates. CI is the process by which an external machine (not your local development environment) fetches your app and dependencies and then runs a test suite to ensure everything in your application builds and runs correctly.
Today, we are proud to announce the general availability (GA) of Kong Gateway 2.6! Kong Gateway 2.6 brings some of the most requested features by users and customers to date. Be sure to upgrade or try out a fresh install today! Kong Gateway 2.6 compatible releases will be available with Konnect, our SaaS platform, shortly! Read on for more details of the included functionality.
The inner workings of an API gateway request can be difficult to understand because of its scale. To provide some orientation, we will use the real world as a reference, from planet-spanning infrastructure to a person eating a chocolate bar (processing a server response in a plugin). This series will divide the abstraction space of how Kong Gateway processes requests into four different layers.
In the last blog, we discussed the challenges in managing APIs at scale in a Kubernetes environment. We also discussed how deploying a Kubernetes Ingress Controller or an API gateway can help you address those challenges. In this blog, we will briefly touch upon some of the similarities and differences between an API gateway and Kubernetes Ingress. We will also discuss a unique approach offered by Kong for the end-to-end lifecycle API management (APIM) in Kubernetes.
As APIs and microservices evolve, the architecture used to secure these resources must also mature. Utilizing a token-based architecture to protect APIs is a robust, secure and scalable approach, and it is also much safer than API keys or basic authentication. However, token-based architecture comes in varying maturity levels, as outlined by the API Security Maturity Model.
As Kong continues to expand its global footprint, we recently added Kore Labs, experts in FinTech digital product lifecycle management solutions, to the Kong customer community in the UK. Kore built its cloud-enabled solution on top of Kong in order to revamp its architecture to scale and provide customized solutions for its clients.
One of the things that’s quite interesting about service mesh is that it has not been a very well-defined category for a very long time. Service mesh is not a means to an end. By looking at its adoption, we’ve been seeing a refocus on the end use case that service mesh allows us to enable. Some are around observability while others are around security and trust – being able to provide that identity to all of our services.
In our first episode of Kongcast, I had the pleasure of speaking with Liz Fong-Jones, principal developer advocate at Honeycomb, about the concept of error budgets for service level objectives (SLOs) and how to accelerate software delivery with observability. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.
Hello, Kong Nation 👋! Constructed from the combined efforts of the open source community and the core engineers at Kong, Inc., today we are very proud to release the Kong Gateway (OSS) version 2.6. Please read on for more release information.
