We have some exciting new features in the latest release of Octant, such as Container Exec and the Workload Viewer, together with several quality of life improvements and bug fixes. We are also changing the cadence of our monthly community meeting to weekly, and giving you a quick and easy way to access bleeding edge changes.
Octant now supports the ability to execute single and interactive commands against containers. This allows you the equivalent of
kubectl exec directly inside of Octant.
Once an executed process has completed, Octant will hold the output in a terminal window until you dismiss it or stop Octant. This is useful behavior when running one-off, non-interactive commands, and allows you to refer back to the output as needed for debugging and informational purposes.
You can now get an at-a-glance view of the health of all your workloads in a namespace using Octant. A workload card will quickly show you if all of your pods are healthy, and the amount of memory and CPU allocated. Clicking on a workload will take you to the resource viewer for that workload.
This is the early stages of the workload viewer, and as the workload feature continues to progress it will eventually become the default view for Octant.
This release also includes bug fixes around CRDs, Plugins, and more. You can find the complete details in our release notes.
We will now be holding community meetings weekly on Wednesdays at 1PM ET / 11AM PT. Be sure to join the project-octant Google group to get a calendar invite. We also announce each meeting one hour before start time in the Octant Slack channel.
As a reminder for those who like to be on the bleeding edge, we have nightly builds available. These are built directly from master each night and allow folks to get faster access to updates and features in-between official releases.
The nature of Octant as a project requires input from the community - from code contributions and documentation to sharing your usage in the field, there are many ways to get involved. Feel free to ask questions via the distribution list, Slack, or try out the latest release on GitHub!