Skip to main content

· One min read

What's Changed

Features

  • 34c38370 resoto Remove SQLAlchemy dependency (#1270)

Fixes

  • 06b4bdc6 docker Optimize swap space
  • 2d06999c docker Remove Jupyterlite venv cherry-picked from main
  • 59dc535b docker Refactor to use resotopython:1.0.2 (#1280)
  • 4aa83140 docker Rebase on resotopython base image and update to Node 16 actions (#1276)
  • 31e30eb9 plugins/digitalocean Bump boto

Chores

  • 02bf0f2c docker Backport workflow_dispatch logic to single image
  • 2173083c ci Update/tag respective stable version docs on tag (#1279)
  • 4c3d3bf5 resoto Bump 2.4.7
  • 6a88d496 resoto Bump 2.4.6
  • cf9db945 ci Update API docs CI (#1267)

· One min read

What's Changed

Features

  • 8d462c68 resoto update the secret name
  • 38532da1 resoto update the workflow to always publish from a branch
  • e380b5c1 resoto update the dependencies in resoto-bundle

Fixes

  • fb669cb0 resotocore Fix api test setup (#1192)
  • 04a0dbd5 plugins/digitalocean Fix the snapshots regions collection (#1194)

Chores

  • f74ed976 resoto bump 2.4.2
  • 7bd2252e ci Correct file path & link for release notes (#1211)
  • d1d0d668 ci Update path to helm chart yaml (#1210)
  • 461547be ci Update CI for versioned docs (#1164)
  • 459f8dde ci Fix release notes generator when no PR, bump helm-charts versions (#1148)
  • 655b4ff1 ci Handle reversed component/group in release notes generator (#1078)

· 7 min read

What's Changed

Features

Fixes

Chores

· 3 min read

Hello everyone, here's an update for July!

In June, we released Resoto 2.3.2. The key update that we shipped is a feature that a lot of users have asked for—support for Kubernetes! 😎

Configuration UI

Last month we introduced our new config system, with the ability to edit your Resoto configuration on the fly via Resoto Shell. Not everyone is comfortable working with the shell though, and so we added a new web-based UI.

Kubernetes Support

So far, Resoto has worked out-of-the-box for the "native" cloud providers AWS, GCP, and DigitalOcean. But our users have been telling us that they're not just running "bare metal" on these clouds. No surprise—most of them use Kubernetes for orchestration. You can now point Resoto to your kubeconfig file, with which Resoto will collect all available contexts.

note

Resoto's unified data model still applies. Common Resoto types like resource, instance, and volume are still relevant with Kubernetes. We went "deep" on Kubernetes from day one, meaning we support the entire set of 100+ Kubernetes properties. Full-text search, piping commands, and performing jobs (like tag and cleanup) also work for Kubernetes.

We think you will be delighted to use Resoto with Kubernetes. For more details, check out Matthias' blog post.

Nested Properties

To add Kubernetes support, we first had to build new capabilities into our data model. Nested properties is one such capability.

The first version of Resoto supported simple structures—think "a resource with a property." This simple structure unfortunately doesn't work well with the nested structures commonplace in Kubernetes. For example, one Kubernetes pod can contain multiple containers. Within each of those containers, you then have a long list of possible properties (from the 100+ mentioned above). Each of those nested properties can be accessed and used for filtering or information retrieval.

Resoto now supports arbitrary complex models with nested properties. We also made sure autocomplete in Resoto Shell works with complex models. You can (literally) navigate through nested properties as you type.

Multi-Cloud Graph Edges

Another fundamental capability we launched with Kubernetes support is support for graph edges between different clouds.

Data collection and definition of resource dependencies within Resoto happens with cloud-specific collectors. Since collectors are cloud-specific, so far Resoto has only supported dependencies within a cloud, not between clouds.

Kubernetes resources are abstracted away from the underlying cloud provider. The Kubernetes collector knows nothing about AWS or EC2 instances, while the AWS collector only knows AWS services like EC2 and EKS. With multi-cloud edge support, Resoto can now track relationships between the two, creating the complete call graph for a view of the entire stack from ingress, via pod, deployment, k8s node, or compute instance down to the hardware.

This new feature provides insights across multi-cloud infrastructure. Since we see a lot of multi-cloud deployments in the enterprise, we will continue to extend our collectors to provide additional insights into relationships across clouds.

Read more about nested properties and multi-cloud graph edges in the release notes.

· One min read

What's Changed

Fixes

· One min read

Join the Some Engineering team tomorrow for our fourth Community Hour event!

Event Details

📅 Thursday, July 7, 2022 4:00 PM UTCRSVP on Discord

We will be showcasing new Resoto features, giving an overview of Resoto's command-line interface (CLI), and answering questions.

Join this event if you…

  • are curious about what Resoto has to offer
  • have questions about Resoto
  • want to meet the Some Engineering team

This event is taking place LIVE on the Some Engineering Discord server and will not be recorded.