Octant Community Meeting

This doc is meant to serve as the "one doc to rule them all" for Octant community meetings.

• Octant community meetings are held every second Wednesday of the month at 1PM ET / 10AM PT (Convert to your timezone)
• Join the community meeting using this Zoom link
• Find previous recordings on YouTube
• Previous meeting notes are moved to GitHub Discussions
• Need help or have an issue to discuss with the team? Add your item to Discussion Topics for the next meeting's agenda.

The Octant team can be reached at:

• #Octant channel in the Kubernetes slack workspace
  • If you aren't already a member on the Kubernetes Slack workspace, please first request an invitation to gain access.
• Twitter: @projectoctant

November 10th, 2021

Status updates

Discussion topics

Q&A

October 13th, 2021 - YouTube Stream

Status updates

• KubeCon!
• Getting field tests of Octant in hardened RBAC
  • Waiting from feedback from an end user to be able to cut back 0.25

Q&A

September 29th, 2021 - YouTube Stream

Status updates

• Release 0.25 status update
  • Module Federation 2622
  • RBAC restricted usage 2923
  • Octant custom protocol progress 2899

Discussion topics

• Community meeting cadence
  • Bi-weekly?
• Octant turnkey image
• Go 1.17

September 22th, 2021 - YouTube Stream

Attendees - Add your name + affiliation (optional)

Status updates

• 0.25 project theme: RBAC restricted usage of Octant as well as providing tighter integration in to the local desktop
• Module federation: why and how (Milan)

Discussion points

Q&A

• What's the role of a custom protocol for the desktop app? (David)

September 15th, 2021 - YouTube Stream

Attendees - Add your name + affiliation (optional)

• David Espejo, VMware
• Milan Klanjsek, VMware
• Kara Yimoyines, VMware

Status updates

• 0.24 has been released!

  • What's new?
    • Added container image manifest for pods #156
    • Added automatic reloading of Go plugins #178
    • Brew formula update WIP

• New video tutorial added

Discussion points

• Retro: Improving the plugin experience. What are we missing to achieve 1.0?
  • The desire to have a RESTConfig
    • Better handling of kubeconfigs, contexts and what is the current context
  • Having the ability to watch different resources from plugins
  • 1.0 is more about the Plugin API than the feature set

Q & A