v1.0.4

• Verify connection doesn't work: when verifying Kerberos Vault it was throwing an verification error, even though settings were correct
• Docker Hub image repository was changed we moved to uugai/factory.

1.0.1049084302

Changes

• Add encryption feature, now you can enable E2E encryption for all of your Kerberos Agents (RSA + AES).
• White labeling factory using your own stylesheet.

Release

• Docker Hub
• kerberos/factory:1.0.1049084302

1.0.851776620

Changes

• Merged API and Frontend projects (similar to Kerberos Agent), we no longer require two ingresses and two ports (see migration section).
• Update UI components, add mobile menu and sidebar fixes.
• Add health checks
• Ability to delete deployments, will now cleanup all resources previously (which was not the case, an error occurred when reusing the name).
• Ability to update resources for an individual resources (memory limit).
• Add verify camera RTSP connections.
• Add friendly name option

Migration

A single "simple" migration steps is required moving to this release. We have merged the API and Frontend into a single binary (similar to Kerberos Agent). Previously we had two applications served in the Kerberos Factory container 8082 and 80. Now both the API and Frontend are served through a single binary running on port 80.

Make sure to modify the K8S_PROXY environment variable from port http://localhost:8082 to http://localhost:80, as we now have all hosted on port 80, and port 8082 is no longer required.

- name: K8S_PROXY
  value: http://localhost:80

Release

• Docker Hub
• kerberos/factory:1.0.851776620

1.0.669719463

Changes

• Kerberos Agent is now running on port :80 instead of :8080. Therefore a change was made in Kerberos Factory to align this. For existing Kerberos Agents (created before this new version, please check the migration section).
• Sub stream functionality has been added to the latest Kerberos Agent, and therefore an additional fields was added to the edit camera modal.

Migration

Kerberos Agents created before this Kerberos Factory release are exposed using the old port :8080. Therefore the equivalent Kubernetes Service is also configured to expose :8080.

When upgrading Kerberos Factory to this release, you'll experience that Kerberos Agents can no longer be opened and the Kerberos Factory UI will crash due to it's not able to connect to the Kerberos Agent on port :8080 any longer. Please follow these steps to do an successful upgrade.

1. Upgrade Kerberos Factory to 1.0.669719463 and change base image for Kerberos Agents to 3ce9adc.
2. Newly created Kerberos Agents will work out-of-the-box, however old Kerberos Agents still run on the old service port :8080.
3. Locate the old Kerberos Agents, created with the previous release of Kerberos Factory, and modify the relevant service file: kubectl get svc -n kerberos-factory.
4. Run the edit command kubectl edit svc kerberosagent-<agent_name> -n kerberos-factory and change the ports from 8080 to 80. Update the new service file CTRL+O.
5. Open the Kerberos Factory UI, and press the Edit camera button. The edit modal should appear now.

Release

• Docker Hub
• kerberos/factory:1.0.669719463

1.0.463972855

Changes

• Allow rtsp-benchmark to send additional configurations/params.

Release

• Docker Hub
• kerberos/factory:1.0.463972855