Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the release doc with Sprint 235 updates #6798

Merged
merged 2 commits into from
May 9, 2023
Merged

Update the release doc with Sprint 235 updates #6798

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c194076
Update the release doc with Sprint 235 updates
valaparthvi May 8, 2023
4d8a72d
Review
valaparthvi May 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
55 changes: 44 additions & 11 deletions docs/website/blog/2023-05-04-odo-v3.10.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,35 +14,68 @@ odo `v3.10.0` is now out!
To install `odo`, follow [the installation guide](../docs/overview/installation).

## Notable Changes
Check this Playlist for an overview of the most notable changes in this release: https://www.youtube.com/playlist?list=PLGMB2PY4SNOqUm7C5VLarQq6jd8Ie0iHu
Check these playlists for an overview of the most notable changes in this release:
* https://www.youtube.com/playlist?list=PLGMB2PY4SNOqUm7C5VLarQq6jd8Ie0iHu
* https://www.youtube.com/playlist?list=PLGMB2PY4SNOqn0aLyfdSQERr657DtbxkA

### Features

#### `--address` to define a custom address for port forwarding during `odo dev`
To enhance the port forwarding feature provided by `odo dev`, you can now use a custom address for ports to listen by passing `--address` flag.
More details are available in [`odo dev` command reference doc](https://odo.dev/docs/command-reference/dev#using-custom-address-for-port-forwarding).
#### [`--port-forward` to define custom port mapping and `--address` to define a custom address for port forwarding during `odo dev`](https://github.com/redhat-developer/odo/issues/6479)
To enhance the port forwarding feature provided by `odo dev`, you can now use custom port mapping with flag `--port-forward` and a custom address for ports to listen by passing `--address` flag.
Read more about [custom port mapping](https://odo.dev/docs/command-reference/dev/#using-custom-port-mapping-for-port-forwarding) and [custom address](https://odo.dev/docs/command-reference/dev/#using-custom-address-for-port-forwarding) on `odo dev` command reference doc.

Custom Port Mapping for port forwarding:
<iframe width="560" height="315" src="https://www.youtube.com/embed/X0mgdcRvz3U?list=PLGMB2PY4SNOqn0aLyfdSQERr657DtbxkA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

Custom Address for port forwarding:
<iframe width="560" height="315" src="https://www.youtube.com/embed/4QJ42cLo6j0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

#### `odo dev` handles failing build commands in a better way.
Build command is ideally the first command that is run after the necessary resources are created in the `odo dev` workflow. Read [How odo works](https://odo.dev/docs/development/architecture/how-odo-works#how-odo-dev-works) for a better understanding of this.
#### [Automatically mounting volumes, configmaps, and secrets](https://github.com/redhat-developer/odo/issues/6549)
You can now automatically mount existing persistent volumes, configmaps and secrets to your `odo dev` deployment by applying an appropriate label to them.
```yaml
metadata:
labels:
devfile.io/auto-mount: "true"
```

In the previous versions, `odo dev` would run the build command in an infinite loop until it succeeded, which was unnecessary. In v3.10.0 however, `odo dev` stops after 1 unsuccessful attempt, and waits for the user to make changes to the project, providing with a slightly better user experience.
Read more about it in [Automounting Volumes](https://odo.dev/docs/user-guides/advanced/automounting-volumes).

<iframe width="560" height="315" src="https://www.youtube.com/embed/ukCXSbHo1c4?list=PLGMB2PY4SNOqn0aLyfdSQERr657DtbxkA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

<iframe width="560" height="315" src="https://www.youtube.com/embed/bBtil91_X-Q" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

#### Support variable substitution for `odo build-images`
#### [Support variable substitution for `odo build-images`](https://github.com/redhat-developer/odo/issues/6274)
`odo build-images` now supports the Devfile variable substitution in a similar way as `odo dev` and `odo deploy`.

Read more about it in the [`odo build-images` command reference doc](https://odo.dev/docs/command-reference/build-images#substituting-variables).

<iframe width="560" height="315" src="https://www.youtube.com/embed/lWZAaerNck4" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

#### [`odo dev` can run simultaneously on podman and cluster](https://github.com/redhat-developer/odo/issues/6494)
<iframe width="560" height="315" src="https://www.youtube.com/embed/1tAioAuyxJY?list=PLGMB2PY4SNOqn0aLyfdSQERr657DtbxkA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

### Bugs

#### [Allow to cancel `odo dev` execution at any phase](https://github.com/redhat-developer/odo/issues/6196)
In the previous versions, `odo dev` could not be cancelled until the build phase was complete. This has now been fixed to allow cancelling `odo dev` at any phase.
<iframe width="560" height="315" src="https://www.youtube.com/embed/mwQP3mD05eU?list=PLGMB2PY4SNOqn0aLyfdSQERr657DtbxkA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

#### [`odo dev` handles failing build commands in a better way.](https://github.com/redhat-developer/odo/issues/6196)
Build command is ideally the first command that is run after the necessary resources are created in the `odo dev` workflow. Read [How odo works](https://odo.dev/docs/development/architecture/how-odo-works#how-odo-dev-works) for a better understanding of this.

In the previous versions, `odo dev` would run the build command in an infinite loop until it succeeded, which was unnecessary. In v3.10.0 however, `odo dev` stops after 1 unsuccessful attempt, and waits for the user to make changes to the project, providing with a slightly better user experience.

<iframe width="560" height="315" src="https://www.youtube.com/embed/bBtil91_X-Q" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

#### [PodSecurity Admission: Display duplicate warnings only once](https://github.com/redhat-developer/odo/issues/6699)
Warnings related to PodSecurity Admission are now printed only once.

#### [Wait until expected ports are opened before starting port-forwarding](https://github.com/redhat-developer/odo/issues/6667)
`odo dev` now waits until the application ports are listening before printing the port forwarding information.

### Documentation
* [Blog: Helm integration with odo](https://odo.dev/blog/using-helm-with-odo)
* [`odo dev` behavior with .gitignore and .odoignore](https://odo.dev/docs/user-guides/advanced/pushing-specific-files)


* [Automounting Volumes](https://odo.dev/docs/user-guides/advanced/automounting-volumes)

## Detailed Changelog

Expand Down