Skip to main content

odo v3.7.0 Released

· 5 min read
Armel Soro

odo v3.7.0 is now out!

To install odo, follow the installation guide.

Notable Changes​

Check this Playlist for an overview of the most notable changes in this release: odo v3.7.0 (Sprint 231)

Features​

odo logs on Podman​

To continue improving the feature parity between Kubernetes and Podman, odo logs is now supported on the latter.

Similarly to how odo dev requires specifying the target platform (using the --platform flag), odo logs also requires specifying the platform to display the logs of a component running on Podman, like so:

ODO_EXPERIMENTAL_MODE=t odo logs --platform podman

As a reminder, Podman support in odo is still experimental and requires you to opt in if you want to try it out.

More details on forwarded ports in the output of odo describe component​

odo describe component now additionally includes the following helpful information about forwarded ports:

  • the endpoint name, as defined in the Devfile
  • the endpoint exposure, as defined in the Devfile
  • whether the port is a debug endpoint or not. Note that this is based upon a naming convention: the endpoint name in the Devfile should be debug or be prefixed with debug- to be considered as a debug endpoint.
Example output:
Normal outputJSON output
$ odo describe component

[...]

Forwarded ports:
 •  127.0.0.1:20001 -> cont:3000
    Name: http-node
 •  127.0.0.1:20002 -> cont:5858
    Name: debug
    Exposure: none
    Debug: true
 •  127.0.0.1:20003 -> cont2:5005
    Name: debug-2
    Exposure: internal
    Debug: true

[...]
$ odo describe component -o json
{
  [...]
  "devForwardedPorts": [
    {
      "containerName": "cont",
      "portName": "http-node",
      "isDebug": false,
      "localAddress": "127.0.0.1",
      "localPort": 20001,
      "containerPort": 3000
    },
    {
      "containerName": "cont",
      "portName": "debug",
      "isDebug": true,
      "exposure": "none"
      "localAddress": "127.0.0.1",
      "localPort": 20002,
      "containerPort": 5858
    },
    {
      "containerName": "cont2",
      "portName": "debug-2",
      "isDebug": true,
      "exposure": "internal"
      "localAddress": "127.0.0.1",
      "localPort": 20003,
      "containerPort": 5005
    }
  ],
  [...]
}

Support for OpenShift Devfile components​

odo now supports OpenShift components that are defined in a Devfile.

Detailed Changelog​

As with every release, you can find the full list of changes and bug fixes on the GitHub release page.

Full Changelog

Features/Enhancements:

  • Support for image component on podman #6577 (valaparthvi)
  • Support dev.odo.push.path:* attributes on Podman #6576 (rm3l)
  • Implement odo logs on podman #6550 (feloy)
  • Add support for OpenShift Devfile components #6548 (rm3l)
  • Set platform and platformVersion in telemetry #6540 (feloy)
  • Show information about forwarded debug ports in odo describe component #6537 (rm3l)

Bugs:

  • Fix UX inconsistency when handling commands bound to events #6574 (rm3l)
  • odo logs: Do not panic when no access to cluster/podman #6561 (feloy)
  • Correct container-attributes data in release blog #6560 (valaparthvi)
  • Log error when podman client cannot be initialized #6538 (valaparthvi)
  • Display error message when odo dev fails on podman and clean resources #6522 (valaparthvi)

Documentation:

  • Fix the port value (20001) in the quickstart guides #6570 (rm3l)
  • Verification file for Google Search console [feloy] #6566 (feloy)
  • Dogfood odo for working on the website #6564 (rm3l)
  • Set the date for the v3 GA blog post #6563 (rm3l)
  • Add blog post demonstrating how odo can be used with Podman #6562 (rm3l)
  • docs: --HEAD flag for homebrew no longer needed #6554 (kadel)
  • Release PR for v3.6.0 #6529 (github-actions[bot])

Cleanup/Refactor:

  • test: use t.TempDir to create temporary test directory #6533 (Juneezee)

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

Contributing to odo​

If odo interests you, and you would like to contribute to it, we welcome you!

You can contribute to odo in a lot of different ways!

Take it for a spin 🚘 and report back bugs🐞 that you encountered, or features🌟 that you would like to see.

Help us with the documentation📜, or tell us how you used odo 🖍.

Review the PRs👀, or help us fix a failing test 🚩.

Work on the TODOs📝, or help us cleanup the code🚮.

Or, simply tune in📻 to our contributor calls and learn more about odo.

odo is your playground!

Read the developer reference guide on contributing to odo to know more.