6.1 and Minor Releases
6.1.0 Release Notes
Released on kinops October 17, 2024
No Customer-Managed Release. 6.1.2 will be the next available version.
Incompatibility with previous versions
The design of Integrator introduced changes to the form's JSON structure. As a result, forms created or edited in a v6.1+ environment are incompatible with earlier versions. This means forms exported from a v6.1 space cannot be imported into earlier versions, even if they do not use the new integration strategy.
Integrator
6.1.0 includes the initial release of our next-generation integration framework, colloquially known as "Integrator." See additional documentation here (https://docs.kineticdata.com/docs/integrator)
Miscellaneous Updates
- We've introduced several security updates across the Platform
- Fix healthz and default-backend Image Names in Dispatch Job.
- Remove out-of-compliance decryption modules from Coordinator.
- Resolve Indexer logging issues and update Dockerfile and chart.
- Remove Discussions-related Webhook events from Core.
- Convert the 'iv' and 'salt' to use SecureRandom in Kinetic Core.
Bug Fixes
- Corrected an issue where, after cloning a workflow to another form, the redirect page would incorrectly point to the workflow in the origin form instead of the destination form.
- Corrected an issue where viewing a submission with null attachment values breaks the space console.
- Corrected an issue where defining a model with a very long, space-free qualification query caused the Name and Result Type columns to be squashed.
6.1.2 Release Notes
Release on kinops January 23, 2025
Customer-managed release date pending
Version 6.1.1 was not officially released for customer-managed implementations.
These release notes include all changes introduced since version 6.1.0.
Integrator
Enhancements to HTTP Connections
- Secrets Handling: Introduced the ability to define secret values for authentication configurations that require sensitive information. This is particularly useful for cases like HTTP Bearer Token authentication, where credentials can be passed through headers, URL parameters, or request bodies. These secrets are handled securely and injected into connection configurations.
- Connections Health Checks: Builders can now specify a health check GET endpoint (e.g.,
/app/api/v1/version
) to validate the health of a connection. This enhancement supports all HTTP connection types, including Basic Authentication, providing a method to validate credentials and configurations before defining and testing operations.
Improvements to HTTP Operations
- Operation Documentation: Added a description field to HTTP operations, allowing Builders to document the purpose, parameters, and expected values.
- Troubleshooting Inputs: Updated the handling of empty URL parameters to ensure they are omitted, addressing limitations in APIs (including our own).
- Double-Slash Scenario: Enhanced operation execution to automatically eliminate double slashes in the URL (e.g., when the base URL ends with
/
and the operation path starts with/
). - Timeout Implementation:Added a timeout to HTTP operations to abort and fail requests if no messages are received within a defined period.
- Error Indicators: Introduced an exclamation icon on operation tabs to indicate errors more clearly.
Additional Features and Updates
- Database Optimization:Updated certain database columns to use the JSONB datatype for better performance and flexibility.
- Connection Testing Results: Refactored the results returned when testing connections for greater clarity
- Wildcard Certificates: Added support for wildcard certificates in connection configurations.
- Performance Telemetry: Incorporated additional performance telemetry for Integrator to enhance monitoring and diagnostics.
- OAS Specifications: Normalized OpenAPI Specifications (OAS) and leveraged references where applicable for consistency and maintainability.
- Integration Tests: Implemented integration tests for validating connection certificate configurations.
Miscellaneous Updates
Security
- Implemented multiple security enhancements across the Platform to improve data protection and prevent vulnerabilities.
User Interface Enhancements
- Removed links to the legacy form builder from the Platform Console.
- Updated the confirmation modal for deleting workflows to include the workflow name.
- Updated the Coordinator to automatically apply appropriate settings, ensuring newly created spaces are fully functional without requiring a platform template.
System Improvements
- Completely removed Discussions from Core.
- Added a form in the system console to assist with migrating a space from another Kubernetes cluster into the current cluster.
- Updated the Coordinator to automatically apply appropriate settings, ensuring newly created spaces are fully functional without requiring a platform template.
Bug Fixes
Remote Agent 6.1 now officially supports Tomcat 9, but there is an issue with upgrade to 9.0.96.
When upgrading your local Tomcat to 9.0.96, you may be required to delete your Tomcat work directory (e.g.
$TOMCAT_HOME/catalina/work
) forkinetic-agent
if you run into JSP errors.From the Tomcat release notes:
In 9.0.96, a change was made to the way pooled JSP tags were released, resulting in a binary incompatiblity between some JSP files compiled with earlier versions of Apache Tomcat 9. This incompatibility will be corrected in 9.0.97, so JSPs compiled before 9.0.96 should again run without recompilation in 9.0.97 and later.
Integrator
- Fixed an issue where connections to the Kinetic platform returned a 401 error after deploying a new Integrator container.
- Resolved an issue with the Integrator container readiness check that caused repeated pod restarts.
- Fixed an issue where saving an Integrator connection with HTTP auth returned a 500 error.
- Addressed a bug where the Integrator code editor page copied content from the wrong tab.
- Fixed an issue where the outputs tab in an Integrator operation did not display errors due to payload shape changes.
- Corrected a startup error in Integrator related to static assets.
- Resolved an issue where too many simultaneous Integrator executions caused Hackney processes to mishandle GenServer calls.
- Updated the space console UI to display the correct Kapp integration URL and revised related help text.
Space Console
- Fixed a crash in the space console caused by improperly formatted error responses during integration operation or connection testing.
Workflow Builder
- Fixed an issue where cloning a node caused an unexpected application error.
- Resolved a bug where dropdown types in workflow builder nodes were rendered as text boxes.
- Corrected an issue where using outputs from an Integrator operation wrapped results in quotation marks.
System Console
- Corrected a typo in an error message related to certificates.
- Resolved an issue where ingress certificate rotation incorrectly displayed a restart-required message.
- Updated the system console to reflect Integrator changes consistently.
Other
- Fixed failing tests caused by the JSTL upgrade.
- Resolved a security context issue with the NFS Subdir External Provisioner that blocked dynamic volume creation.
- Fixed an issue where spaces with legacy Discussion policies could not be saved.
- Resolved a bug where Task could not be enabled in spaces initially created without Task.
- Fixed an error when creating a Kapp with categories that include attributes.
- Addressed an issue where form fields based on integrations were not populating on subsequent views.
- Corrected an issue where validating the Database Adapter broke subsequent executions.
6.1.3 Release Notes
Release on kinops March 20th, 2025
Release for customer-managed environments pending.
Integrator Naming
Integrator is an internal name we've used for our new integration framework. While this name has appeared in some published documents, it is not visible within the platform itself (unless you're looking under the hood). Integrator is just one of several ways to integrate with external systems and the platform itself. Moving forward, we will no longer refer to "Integrator" in documentation. Instead, we'll use the more generic term integrations to cover changes or enhancements across ALL integration capabilities.
Integration Updates
- Automatically update output results when editing output mappings (if valid JavaScript) after running an operation.
- Add support for PATCH methods in HTTP operations.
- Replace common error messages with user-friendly text.
- Support processing response cookies in HTTP authentication and operations.
- Allow creating connections and operations with a specified ID.
- Adjust HTTP Bearer Token authentication to treat any 2xx response as successful.
- Refactor integration connection types to be dynamic (no hardcoding).
- Refactor ExecuteController to remove support for inline connection definitions.
- Enable Ndots customization for Integrator deployments.
- Add support for running integration tests that rely on Keycloak in GitHub Actions.
Navigation Updates
- Activity is now renamed Insights
- We've streamlined the navigation experience by relocating items previously found under Global Workflow directly into the Space console.
- Space > Insights > Activity is where to find Runs, Errors, Triggers as well as space-level Webhook Jobs.
- Space > Build > Workflow is where to manage all Trees and Routines as well as space-level Workflows and WebAPIs.
- The Kapp navigation has been updated similarly. Kapp name > Insights > Activity is where to find all Kapp-level Webhook jobs. Kapp name > Build > Workflow is where to manage Kapp-level Workflows and WebAPIs.
- As a result of these changes, the dropdown option Global Workflow has been removed.
Miscellaneous Updates
Workflow Builder
- Added the ability to navigate directly from a workflow error to the related loop iteration in the Run Explorer.
- Moved the Close button inside the workflow builder node tab when only one tab is open for improved usability.
Bug Fixes
Space Console
- Fixed an issue in Space Console submission views where the display of a sort-column caused confusion.
- Resolved an issue that allowed the creation of usernames with invalid characters.
Workflow Builder
- Fixed an issue where long operation names on workflow nodes were truncated to an ellipsis with no visible portion of the name.
- Resolved a problem where result bindings were omitting nodes if their names contained special characters.
- Corrected an issue where Usage information on a node didn’t update unless the entire page was reloaded.
System Console
- Resolved a routing bug with new migrate UI in the System console.
Integrations
- Handled trapped exists in ConnectionServer to prevent unexpected failures.
- Resolved an issue where certain valid error responses were not properly matched or summarized in the front-end.
- Fixed a bug where loading a connection with an invalid OAS configuration caused a json.encoder error.
Installer
- Enabled proxying of image pulls through the Replicated Proxy for online installs.
- Fixed BYOC (Bring Your Own Certificate) customizations incorrectly appearing in the k0s config form in Replicated.
- Fixed an issue where the k0s Embedded Installer displayed BYOC customizations unintentionally.
- Reduced the replica count of in-cluster resources when running with a Replicated development license.
- Fixed an issue where the kinetic-system-initialization job failed to start on fresh installs due to a
wget
problem.
Other
- Resolved an issue with authentication entry points and success handling affecting SPA (Single Page Application) display types.
- Fixed a bug where dropdown fields powered by integrations didn’t render values correctly when viewing an existing submission.
- Improved the Approval Link flow to ensure users are properly redirected after login if they weren’t already authenticated.
- Removed legacy System Console code, artifacts, and rendering support.
- Upgraded the Ingress NGINX Controller for improved stability and support.