The Management Console serves as the central hub for orchestrating and managing platform infrastructure across the environment. From deployment scaling and service management to security configuration and operational updates, the console provides administrators with the tools required to manage complex environments efficiently.
Recent enhancements to the configuration workflow have made the editing experience faster, more intuitive, and more flexible. With improvements such as tab-based navigation, selective deployments, integrated pod management, and automated certificate handling, administrators can now apply changes with greater precision while minimizing operational disruption.
This guide explains how to navigate the updated configuration experience and effectively manage deployment changes within the Management Console.
Non-Linear Configuration Navigation
Traditional deployment workflows often relied on a strict step-by-step process, forcing administrators to move sequentially through multiple screens before making updates. The Management Console now introduces a more agile and flexible editing experience through tab-based navigation.
Direct Access to Configuration Sections
Administrators can move directly between configuration categories such as:
- Infrastructure
- Services
- Security
- Deployment Settings
without needing to follow a linear “Next” button workflow.
This allows teams to quickly jump to the exact configuration area that requires modification, significantly improving efficiency during operational updates.
State Preservation Across Tabs
As administrators move between configuration sections, the console preserves all entered values and pending changes.
This enables teams to:
- Review multiple configuration areas simultaneously
- Make cross-sectional updates more efficiently
- Validate changes before committing updates
without the risk of losing previously entered information.
Faster Configuration Iteration
The non-linear workflow is especially useful when making targeted updates such as:
- Adjusting scaling parameters
- Updating environment variables
- Modifying service configurations
- Reviewing deployment-specific settings
By removing unnecessary navigation steps, administrators can perform configuration tasks more quickly and with less operational overhead.
Managing Scaling & Pod Lifecycle
Configuration changes within Kubernetes-based environments often require service refreshes or pod restarts before updates become active. The Management Console now includes integrated operational controls to simplify these workflows.
Manual Scaling Controls
Administrators can directly adjust deployment replica counts from within the console.
This allows teams to:
- Scale services up or down
- Manage resource allocation dynamically
- Refresh workloads during maintenance operations
- Handle temporary traffic or processing spikes
without relying on external Kubernetes command-line tools.
Direct Pod Management
If configuration changes are not automatically reflected across running services, administrators can now view and delete specific pods directly from the interface.
When a pod is deleted:
- Kubernetes automatically schedules a replacement pod
- The new pod pulls the latest configuration values
- Updated settings become active without requiring a full deployment restart
This provides a fast and controlled method for applying configuration updates across services.
Support for Restricted Environments
These controls are particularly valuable in restricted or read-only operational environments where administrators may not have direct access to Kubernetes management tools such as kubectl.
By exposing operational capabilities directly through the Management Console, teams can continue managing deployments securely without requiring elevated cluster permissions.
Targeted Force Deployments
Not every configuration update requires a full platform redeployment. To reduce downtime and improve deployment efficiency, the Management Console supports selective force deployment options.
App Pods Only
This option should be used when changes affect only the frontend or user-facing application layer.
Examples include:
- UI configuration updates
- Frontend environment variable changes
- Client-facing service adjustments
Backend Pods Only
This option targets backend processing services and internal APIs.
Typical use cases include:
- Processing logic updates
- Backend service configuration changes
- Internal API or data pipeline modifications
Full Deployment
A full deployment should be used when infrastructure-wide changes impact the complete platform stack.
Examples include:
- Global infrastructure modifications
- Shared dependency updates
- Platform-wide configuration changes
By deploying only the required components, administrators can significantly reduce system-wide downtime and improve operational responsiveness.
Security & Certificate Configuration
Managing SSL/TLS certificates and trusted Certificate Authorities (CAs) is often a complex operational responsibility. The Management Console simplifies this process through an integrated certificate management workflow.
Uploading Certificates
Administrators can navigate to the Security Configuration section and paste the contents of a .crt certificate directly into the console.
This removes the need for manual file distribution or command-line certificate management.
Automated Certificate Conversion
Once submitted, the console automatically converts the certificate into Java KeyStore (.jks) format.
This eliminates manual conversion steps and reduces the likelihood of formatting or compatibility errors.
Automated ConfigMap & Environment Updates
The platform automatically:
- Generates the
syntasa-ca-bundleConfigMap - Configures the required environment variables
- Synchronizes certificate settings across related services and pods
This ensures that all platform components consistently recognize and trust the updated certificates.
Environment-Wide Synchronization
After saving the configuration, the platform propagates the updated certificate settings throughout the environment, enabling secure communication across all services without requiring manual intervention.
Performance & Reliability Improvements
Several under-the-hood optimizations have been introduced to improve the responsiveness and reliability of configuration workflows within the Management Console.
Faster Configuration Loading
Configuration pages have been optimized to eliminate delays previously experienced during page initialization.
Administrators can now:
- Access deployment settings more quickly
- Navigate between configuration sections seamlessly
- Apply updates without interface lag or “hang” states
This creates a significantly smoother operational experience.
Enhanced Error Handling
The console now provides more descriptive and actionable error feedback during configuration updates.
Instead of generic system failures, administrators receive detailed guidance for issues such as:
- Duplicate usernames
- Invalid secret names
- Configuration validation failures
- Deployment-related conflicts
These improvements simplify troubleshooting and reduce the time required to resolve operational issues.
Conclusion
The enhanced configuration workflow within the Management Console provides administrators with greater flexibility, operational precision, and control over platform infrastructure.
With capabilities such as non-linear navigation, integrated pod lifecycle management, selective deployments, and automated certificate handling, administrators can efficiently manage environment updates while minimizing downtime and operational complexity.
These enhancements transform the Management Console into a more responsive and operationally mature administration platform, enabling teams to focus on delivering stable, secure, and high-performing environments.