Wanaku

Appearance

Wanaku 0.2.0 Released: Production Hardening and Enhanced Security ​

We're excited to announce Wanaku 0.2.0, a release focused on improving stability, security, and developer experience. This release takes steps toward making Wanaku more reliable for real-world deployments.

What's New in 0.2.0 ​

Improved Stability ​

Wanaku 0.2.0 includes improvements in error handling and operational reliability:

  • Better Error Messages — Raw Java exception class names have been replaced with user-friendly MCP error messages, giving you actionable descriptions that help you understand what went wrong.

  • Proper HTTP Status Codes — Fixed cases where the API returned generic 500 errors instead of appropriate 404 responses for missing resources (toolset repos, forward refreshes). This makes debugging integration issues much easier.

  • CLI Exit Codes — Admin CLI commands now correctly propagate non-zero exit codes on failure, ensuring that errors are properly detected in automated workflows.

  • OIDC Auth Improvements — Fixed CLI auth token handling, probe logging, and added PKCE support for more secure OIDC authentication flows.

Kubernetes Operator Enhancements ​

The Wanaku Kubernetes operator received several critical fixes:

  • Camel Integration Capability Labels — Fixed incorrect app labels in WanakuCapability resources for the Camel Integration Capability, ensuring proper resource tracking and selection.

  • Environment Variable Support — Camel integration capability routes now correctly honor environment variables, making it easier to configure routes for different deployment environments.

  • Log Error Filtering — JVM -XX: flags are now excluded from the operator's log error detection, preventing false positives when JVM tuning flags appear in logs.

  • Test Environment Support — Adjusted OpenShift service account permissions for better development and testing workflows.

New Service Templates ​

Wanaku 0.2.0 adds two new service templates for vectorized search:

  • Qdrant — A new service template for Qdrant-based vectorized search, enabling AI agents to query vector databases through MCP.

  • Pinecone — A Camel-Pinecone service template for vectorized search, providing another option for vector database integration.

CLI Improvements ​

  • --insecure Flag — The CLI now supports --insecure to trust all server certificates, simplifying development and testing workflows with self-signed certificates.

  • --plain Mode — A true plain output mode that bypasses JLine table rendering, making CLI output easier to parse in scripts and automated pipelines.

  • --unmask Option — Added --unmask to wanaku auth token --get for revealing the full token value when needed.

  • WANAKU_HOME Support — The LocalRunner now honors the WANAKU_HOME environment variable, allowing you to customize the Wanaku installation directory.

Namespace and Validation Improvements ​

Namespace management is now more robust and user-friendly:

  • Namespace Name Validation — Namespace names are now validated to reject non-alphanumeric characters (except dashes), preventing configuration errors that could break routing.

  • CLI Alias for Namespaces — Added --namespace-name as a PicoCLI alias for --namespace, making CLI commands more intuitive.

  • Null Path Guards — Fixed edge cases where the system attempted to create namespaces with null paths, which led to confusing error messages.

  • Validation Error Details — The API now surfaces detailed validation error messages instead of the generic MCP -32603 error code, making it clear what needs to be fixed.

  • Namespace List Filtering — The default namespace is now correctly excluded from label-filtered namespace lists when appropriate.

Security and Authentication ​

Security received significant attention in this release:

  • Custom Credentials File Path — The WANAKU_CREDENTIALS environment variable now allows you to customize the credentials file location, supporting stricter security policies and containerized deployments.

  • Production Security Guide — New comprehensive documentation on security best practices for production deployments, covering authentication, authorization, network policies, and secrets management.

  • Java Truststore Documentation — Detailed guidance on configuring Java truststore for HTTPS server connections, essential for enterprise deployments with custom CA certificates.

  • Local Mode Security Warning — Wanaku now warns when running in local mode with disabled authentication, making it clear when you're running in an insecure configuration.

Developer Experience ​

We've made it easier to build, test, and contribute to Wanaku:

  • Static Analysis — Integrated PMD and SpotBugs static analysis tools, catching potential bugs and code quality issues earlier in the development process.

  • Comprehensive Testing Guide — New documentation covering testing capabilities, test plans, and best practices for contributors.

  • Enhanced Operator Documentation — The operator documentation now includes additional status fields and troubleshooting tips based on real-world deployment experience.

Dependency Updates ​

Wanaku 0.2.0 includes updated dependencies for security and compatibility:

  • LangChain4j: 1.13.0 → 1.17.2
  • Quarkus MCP Server: 1.12.1 → 1.13.1
  • Quarkus Helm: 1.4.0 → 1.4.1
  • LangChain4j MCP: 1.13.0-beta23 → 1.16.1-beta26
  • JaCoCo Maven Plugin: 0.8.14 → 0.8.15
  • JNA: 5.19.0 → 5.19.1
  • Forage: upgraded to 1.5.0

Note: Quarkus platform and Apache Camel remain at 3.33.2 and 4.18.1 respectively.

Get Started ​

Install Wanaku with the installer script:

bash
curl -sSL https://wanaku.ai/get-wanaku.sh | bash

On Windows or if you prefer JBang:

bash
jbang app install wanaku@wanaku-ai/wanaku

Upgrade Notes ​

If you're upgrading from 0.1.x:

  1. Namespace Names — Review your namespace configurations. Names with special characters (other than alphanumeric and dashes) will now be rejected during validation.

  2. Operator Labels — If you're using label selectors on WanakuCapability resources for the Camel Integration Capability, verify they match the corrected labels.

  3. API Error Handling — If you have custom error handling that relied on specific HTTP status codes, test against the new responses. We now return 404 for missing resources instead of 500.

  4. OIDC Configuration — If you use OIDC authentication, token handling and PKCE support have been improved. No configuration changes are needed.

Wanaku 0.2.0 is part of a coordinated release across the Wanaku ecosystem:

  • Wanaku Capabilities Java SDK 0.2.2 — Updated SDK with compatibility improvements
  • Camel Integration Capability 0.2.0 — Synchronized release with environment variable support
  • Wanaku Demos 0.2.0 — Updated demos demonstrating new features

Documentation ​

Check the documentation to learn more, explore the demos, and report issues on GitHub.

Thank you to everyone who contributed to this release through code, documentation, testing, and feedback. Wanaku is better because of this community.