Skip to main content

Kubernetes (for GCP and OVH users)

Ingress​

After evaluating different ingress solutions within the Kubernetes ecosystem, our choice is Apache APISIX. Here are the reasons behind our decision:

  • Built on Nginx: Apache APISIX is built on top of the Nginx web server, leveraging its robustness and performance.

  • Open-Source Foundation: Supported by the Apache foundation, Apache APISIX aligns with our commitment to open collaboration and innovation.

  • Extensible with Plugins: Apache APISIX comes with a variety of plugins, allowing us to extend its functionality according to our specific requirements.

  • Powerful Visual Interface: Apache APISIX provides a user-friendly visual interface, simplifying the management and monitoring of our ingress configurations.

This selection aligns with our goals for scalability, reliability, and ease of management within our Kubernetes infrastructure.

How to handle changes via interface vs changes via infrastructure templates?
The infrastructures deployed by Webcapsule rely on infrastructure as code templates. Consequently, during a redeployment, these templates may overwrite manual modifications made via the interface. While this situation occurs infrequently in practice, we recommend the following steps to avoid it:

  1. Initially, test the modifications that you wish to incorporate via the visual interface of Apache APISIX.
  2. Subsequently, add these modifications to the infrastructure templates to ensure that both the template and the interface are in sync.

Cert Manager​

We utilize Cert Manager for managing HTTPS certificates within our infrastructure. Cert Manager is a Kubernetes-native certificate manager that automates the issuance and renewal of TLS certificates, ensuring secure communication. Cert Manager streamline the process of obtaining and managing certificates, enhancing the security and reliability of our web applications.