The Latest in Containerization
Camptocamp is partnering its containerization skills and knowledge with Isovalent’s unrivaled new bleeding edge technology to support and empower customers' Kubernetes platforms.
Camptocamp and Isovalent
Cilium and the various solutions offered by Isovalent are part of a broader context, the microservices and containerization revolution. This paradigm shift involves many changes that are not only technical but also cultural. It is about rethinking how services are developed and deployed in a more agile way without compromising on stability and security.
To succeed in this transformation, companies need to be accompanied by specialists who can help them better approach this revolution by adopting the right tools and best practices from the start.
Camptocamp has this experience and many specialists who can show you the way.
Isovalent offers the latest technological advances in automation and containerization through its Tetragon and Cilium applications, which significantly reduce complexity and costs compared to traditional solutions.
Isovalent builds Open Source software and enterprise solutions that solve for networking, security, and observability needs in modern cloud-native infrastructure.
Cilium leverages a new Linux kernel technology, eBPF, enabling high-performance, cloud-native networking as well as observability and security. This significantly accelerates the investigation of application and platform level issues.
The cutting edge technology Cilium has already been adopted by leading global companies such as Adobe, AWS, Capital One, Datadog, GitLab, Google, and many more. For more information about the companies that have successfully implemented Cilium, visit the Cilium Adopters page.
When do you need Cilium/Tetragon?
- Your production Kubernetes platforms are slowed down by networking, observability and security challenges
Addressing security & compliance requirements
Providing advanced connectivity
Ensuring identity-aware observability for platform and application teams
Facing challenges with legacy approaches (networking, load balancing, multi-cluster connectivity)
But before taking full advantage of Cilium, a company should consider the following:
From a Service Mesh perspective
Are you struggling to keep a complex service mesh infrastructure running?
Sidecars are complex and difficult to handle because they require modification of pods.
They add a second layer of control to the platform, which means increased complexity and additional maintenance. As an alternative to the sidecar model, Isovalent Cilium Service Mesh offers a transparent service mesh with high efficiency and low complexity, with the help of eBPF.
How do you get deep insight into the applications and their traffic?
Cilium gives application teams self-service access to tools that provide comprehensive data streams about the status of connectivity between their services.
Data is essential to solving the classic "accusation" between application and operations teams. Cilium also securely gives application tenants access only to the connectivity data associated with their Kubernetes namespaces.
How do you transparently ensure encryption across all protocols?
To quickly solve a connectivity problem, it is essential to have as much historical context as possible. Cilium enables later queries as well as analysis of data and flows. Cilium also tags flow data with additional metadata, such as details about policies applied when a flow was allowed or denied. That greatly simplifies troubleshooting.
From a Cluster Mesh perspective
Do you feel your cross cluster pod-to-pod communication is efficient enough?
Without a simple out-of-the box mechanism for cross cluster communications, the majority of companies end up with many isolated clusters, which increase operational overhead, costs and resources. Cilium’s observability dashboard solves this issue.
Does your current environment have a built-in cross cluster control plane?
No, unlike in most Kubernetes networking environments, where built-in control planes have to go through gateways or proxies in order to span clusters, which increases overhead and delay, Cilium’s high availability control plane and service proxy simplify recovery, making it faster and cheaper.
Do services have to leave the cluster on your current solution in case of lost identity?
Yes. Thanks to the out-of-the-box observability dashboard, allowing a broader visibility around communication, services’ behavior and also to the networking infrastructure named Hubble, Cilium is a highly efficient solution.
Overview of Cilium/Tetragon’s main features
eBPF powered networking and observability
eBPF super charged service mesh
Decreased operational complexity
Decreased resource usage
Higher performance with eBPF approach
Avoid sidecar start-up/shut-down race conditions
Supports UDP, no traffic re-route and is already a part of CNI
Multi cluster connectivity
Management complexity is low, as it is easy to install and operate with no code to instrument
IP forwarding is without proxies or gateways
Kubernetes fundamental component of design is preserved and can be used for networking policies
Already implemented encryption at platform layer requires no further application changes
No overhead in configuring the same service across multiple availability zones with single or multi cloud setup. Simplifies recovery in case of partial or total meltdown
Network is fully observable without additional code changes
Deep visibility into the networking infrastructure with the observability dashboard.
Are you currently using or interested in Cilium with Red Hat OpenShift? Read more specific use cases of Cilium and Red Hat :
As a Container Network Interface (CNI), Cilium is recognized by Red Hat as one of OpenShift Operators
Isovalent explains “How to supercharge OpenShift with eBPF & Cilium” specifically to deliver more value on both the developer and operating sides.
Get in contact with us
Interested in working in an inspiring environment and joining our motivated and multicultural teams?