Siebel Cloud Manager (SCM) uses an ingress controller to manage how external users and systems access Siebel services running in a Kubernetes cluster. With the Siebel CRM 26.3 Release Update, SCM will be transitioning its default ingress controller from NGINX to Traefik.
Click here to find out more about Siebel Cloud Manager and its key benefits.
What’s driving this change?
The Kubernetes community has announced that the NGINX ingress reaches end of life (EOL) in March 2026 and will no longer receive:
- Security patches for new vulnerabilities (CVE fixes)
- Bug fixes and reliability improvements
- Guaranteed compatibility with future Kubernetes versions
To protect your business from the risks of unsupported software, SCM is stepping in to provide a modern, supported alternative – Traefik, a cloud-native ingress controller and reverse proxy that manages inbound application traffic in Kubernetes. By moving to Traefik, SCM will keep your deployment secure, reliable, and future-ready, while reducing exposure to unsupported software risk.
Secure traffic and TLS management using Traefik
In enterprise architectures, a Load Balancer (for example, OCI Load Balancer) sits in front of the Kubernetes cluster to provide a stable endpoint and distribute traffic before it reaches the ingress controller. With SCM 26.3 and above, the expected flow is as follows:
Traefik manages certificates and TLS configuration at the ingress layer, while the Load Balancer continues to provide external entry capabilities.
Benefits of modern ingress with Traefik
Traefik is a cloud-native ingress designed to reduce operational complexity and improve reliability. It offers the following benefits:
- Automatic SSL management: Simplifies certificate handling at the ingress layer and supports streamlined, automated encryption management.
- Dynamic discovery: Continuously monitors the Kubernetes environment and updates routing rules in real time, reducing manual configuration when services change.
- Modular architecture: Uses Custom Resource Definitions (CRDs) and reusable “Middleware” to manage complex traffic behaviours such as redirects, rate limiting, and custom headers more consistently.
- High performance and scalability: Supports rapid routing updates and improved resource efficiency to help environments scale as demand grows.
Easily transition to Traefik
SCM supports seamless transition to Traefik based on your deployment scenario:
| Scenario | Support and action |
| New deployments (SCM 26.3+) | Fully automated. Traefik is included by default. |
| Existing deployments (SCM 24.x–26.2) | Guided migration. SCM provides a dedicated workflow in migration.sh (Option 8) to help you transition from NGINX to Traefik. |
Built-in safety net: After migration, SCM temporarily retains your existing NGINX settings so you can validate traffic handling by Traefik before the final switchover. This reduces the risk while supporting a controlled transition.
Migrating to Traefik reduces the security and operational risk of relying on an unsupported ingress controller and ensures tour Siebel CRM deployments on Kubernetes are secure, compliant, and aligned with modern traffic‑management best practices.
Aligning with the future
Looking forward, the Kubernetes ecosystem is converging on the Gateway API as the standard for cluster traffic management. By moving to Traefik now, SCM helps aligns your Siebel CRM deployments with a future-ready architecture—enabling you to stay current and maintain a supported path toward next-generation cloud-native connectivity.
For guidance on adopting Traefik as your ingress controller, see the SCM documentation.