What's Changed
In prior versions, anyone who needed to submit a pipeline execution had to get set up to access the Kubernetes cluster where the jobs would run. As of this release, users only need to get set up to access a Sematic server, and the server will handle all communication with Kubernetes. This improves user experience as well as security. It does mean that anyone running cloud execution may need to change their deployment so that the server can access Kubernetes. We've updated [the deployment docs](https://docs.sematic.dev/diving-deeper/deploy) with instructions and created a Helm chart to ease deployment. As a summary of this release:
* BREAKING CHANGE: For cloud execution, users submitting pipelines for execution no longer need Kubernetes access. Users who have deployed the Sematic server using docker will need to either (a) switch to deploying the server on Kubernetes or (b) use their Sematic deployment only for metadata tracking instead of metadata tracking + cloud execution.
* Remove job environment variables from resolution API response
* Lower the probability of evictions of resolution jobs and improve handling of that situation
**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.13.0...v0.14.0