Skip to content

Releases: redhat-developer/odo

Release of v2.0.6

03 Mar 07:18
2f7f4a0
Compare
Choose a tag to compare

Release of v2.0.6

v2.0.6 (2021-03-03)

Full Changelog

New features:

  • Application does not comes up, if pod restarted due to some external factor #4050
  • Added java-maven to the list of components to be tested #4427 (rnapoles-rh)

Code Refactoring:

  • Refactor occlient and kclient by unifying them into one #4093
  • Add better message for component create when devfile does not exists #4018
  • Clean up error wrapping #3911
  • Updates the library to the latest version #4446 (mik-dass)

Bugs:

  • Devfile deletion does not respect context #4437
  • odo push fails for certain url names #4392
  • "odo catalog list services" fails on minishift #4376
  • odo create fails to download files in assigned --context for odo create --starter #4370
  • Integration tests failing on PSI #4364
  • build command should be optional #4363
  • The added private registry will be covered during the integration tests #4343
  • "odo create" needs "--s2i" flag in the multi-component example in the documentation #4184
  • Debug does not work most of the time for python and python-django components #4156
  • Misleading url name issue when using the java-openliberty devfile #4060
  • New spring devfile does not work on default namespace #4027
  • odo create should not require cluster access to function #3811
  • Fixes the URL name cropping issue. #4452 (mik-dass)
  • Modifies odo create for devfile components to not require a cluster access. #4436 (mik-dass)
  • Fixes no default build command error. #4430 (mik-dass)
  • Make starter project download work with custom context directory #4425 (valaparthvi)
  • Adds an error to be ignored while listing services #4420 (dharmit)

Tests:

Documentation & Discussions:

  • Update ci-reference test doc #4289
  • CRC Getting Started - Command in step 4 of chapter 3.3.2 needs to be updated #4069
  • Document how to enable OLM on Kubernetes #4450 (dharmit)
  • Adding link to Connector extension on Open VSX #4434 (brianking)
  • Ci reference test docs #4329 (anandrkskd)

Closed issues:

  • Update import paths for github.com/devfile/api to github.com/devfile/api/v2 #4346
  • Add e2e scenario for java-maven devfile debug command #4162
  • Conditional verification coverage in unit test #4052
  • more tests for odo list #3995

Merged pull requests:

Installation of v2.0.6

To install odo, follow our installation guide at docs.openshift.com

After each release, binaries are synced to mirror.openshift.com

* This Changelog was automatically generated by github_changelog_generator

Release of v2.0.5

11 Feb 11:09
e8030b1
Compare
Choose a tag to compare

Release of v2.0.5

v2.0.5 (2021-02-11)

Full Changelog

New features:

  • Add language and tags to odo catalog list components (devfile) #4385
  • Watch mode doesn't support debug command #4357
  • Automate the process of updating odo.dev website #4255
  • Short alias in CLI #3875
  • Support non dockerfile build for "odo deploy" #3846
  • minor logging improvement suggestion #3830
  • Export tags and language for Devfile components #4391 (jeffmaury)
  • Adds debug-command flag to odo watch #4381 (mik-dass)
  • Adding ubi8/nodejs-14 image as supported #4304 (prietyc123)

Code Refactoring:

Bugs:

  • odo login overwrites the current active project/namespace #4387
  • odo push fails on psi minikube #4383
  • No starter project in "java-maven" component's devfile #4082
  • "odo nodejs create --port <>" creates component with invalid port #3879
  • On macOS odo on crc return "net/http: TLS handshake timeout" #3850
  • Disable preStart event using validations #4405 (kadel)
  • $ARTIFACTS_DIR is set by platform #4399 (anandrkskd)
  • adding project resource check before warning about default project usage #4396 (niconosenzo)
  • Keeping the current active project/namespace when re-logging in #4388 (mcouliba)
  • Fixes catalog list services for minishift #4377 (dharmit)
  • Fixes getPod() for kubernetes components #4374 (mik-dass)

Tests:

Documentation & Discussions:

Closed issues:

  • Verify automation process to run windows tests on PSI #4379
  • Confusing message about default project. #4309
  • Add ubi/nodejs-14 image as Supported #4303
  • Enable 4.7 cluster on periodic jobs #4280
  • jUnit reports misleading test success status #4279
  • odo Interop onboarding process for ocp testing #4223
  • Cleanup odo cluster configure scripts #4199
  • Odo should use apply command for preStart(and postStop when its implemented) #4187
  • Run PR tests on internal PSI resources #4056
  • odo push unable to create namespace on the fly #3921
  • Flags that are not common for both s2i and devfile components should have this information in description #3828
  • We should validate config params for devfile #3791

Merged pull requests:

Installation of v2.0.5

To install odo, follow our installation guide at docs.openshift.com

After each release, binaries are synced to mirror.openshift.com

* This Changelog was automatically generated by github_changelog_generator

Release of v2.0.4

20 Jan 08:11
5544b25
Compare
Choose a tag to compare

Release of v2.0.4

v2.0.4 (2021-01-20)

Full Changelog

Closed issues:

  • Cleanup odo cluster configure scripts #4199

v2.0.4 (2021-01-20)

Full Changelog

New features:

  • View, set and unset "Ephemeral" using "odo preference" commands #4327
  • Upload ginkgo --debug log output to CI artifacts #3807
  • Implement project for devfile #3798
  • Run integration/e2e test validation part of odo release #3796
  • odo should provide more contextual information as to what it's doing #3709
  • Add centos7 nodejs latest as supported #4349 (prietyc123)
  • Execute make target consecutively even on failure #4324 (prietyc123)

Code Refactoring:

  • Refactor json output match through out the test script #3823
  • Follow same initialization pattern as other clients #4323 (dharmit)
  • Changed block comment to reflect what the code actually does. #4312 (niconosenzo)
  • Refactors URL for localConfigProvider. #4311 (mik-dass)
  • Update CI reference doc #4265 (amitkrout)

Bugs:

  • Broken link in Releases page #4308
  • devfile validation fails if folder name is not valid #4305
  • Ignore Che devfile v1 #4276
  • Project devfile deleted #4262
  • odo service list fails with one service #4221
  • Latest images on 3.11 cluster reflects as unsupported on init repo #4220
  • describe and create commands test for existing component in context folder is inconsistent #4210
  • Operator Hub documentation should explain the need for installing Service Binding Operator #4195
  • odo installation on windows is broken #4062
  • odo 'hangs' after using a cluster that's no longer accessible #4046
  • "odo service create" doesn't output service name when no parameters are provided #4013
  • Fixes panic while collecting events from the pod. #4358 (mik-dass)
  • Output service name when creating Operator backed service #4336 (dharmit)
  • override an env file if found without a devfile on odo create #4332 (girishramnani)
  • Don't fail the command if listing a CR's instances fails #4300 (dharmit)
  • Handling absolute and relative source path file uri #4247 (prietyc123)

Tests:

  • Recurring CI failures while trying to verify support for nodejs images #4347
  • Test compilation fails on "vet" check with ginkgo #4277
  • odo log -f tests are flaky #3809
  • Revert centos nodejs tags to older version #4348 (prietyc123)
  • Separates test into its own spec #4345 (dharmit)
  • Some fix for configure script of s390x. #4317 (zhengxiaomei123)

Documentation & Discussions:

  • Update documentation to use Service Binding Operator on operatorhub.io #4299
  • Update docs to install SBO from OperatorHub.io #4306 (dharmit)
  • #4062 Update installing odo on Windows section to fix filename and ad… #4176 (rnapoles-rh)

Closed issues:

  • Build error when trying to build a node.js native addon #4365
  • Expand E2E test case coverage - Creating multicomponent applications with odo #4356
  • Docker rate limit issue being hit on clusters without docker pull secret in PSI #4278
  • Allow users to toggle between ephemeral and persistent volumes for devfiles #3775
  • Add linked component/service information in odo describe for devfile component and operator services #3734
  • Support creating multiple URLs with the same TargetPort #3710

Merged pull requests:

Installation of v2.0.4

To install odo, follow our installation guide at docs.openshift.com

After each release, binaries are synced to mirror.openshift.com

* This Changelog was automatically generated by github_changelog_generator

Release of v2.0.3

09 Dec 06:24
9ae7540
Compare
Choose a tag to compare

v2.0.3 (2020-12-09)

Full Changelog

New features:

  • Make "odo link" compatible with the breaking changes introduced by Service Binding Operator #3973

Code Refactoring:

  • Use the generators from devfile/library #4209
  • Removes ExecCMDInContainer() and ExtractProjectToComponent() from the occlient. #4291 (mik-dass)
  • remove packages imported twice #4275 (girishramnani)
  • Makes odo work with v0.3.0 of Service Binding Operator #4274 (dharmit)
  • Refactors service catalog and discovery client code #4272 (mik-dass)
  • Use the generators from devfile/library #4263 (maysunfaisal)
  • Refactors and moves buildConfigs, imageStreams and some other resources #4261 (mik-dass)
  • Refactors, cleans and moves some resources to the new files. #4250 (mik-dass)
  • remove duplicate list and refactor #4177 (girishramnani)

Bugs:

  • No 2.0.2 binary on mirrors #4269
  • odo delete --app --project does not work for devfile components #4259
  • odo requires the 'master' branch #4257
  • odo env view -o json outputs raw text #4243
  • E2e images test script fails while image verification on windows platform #4235
  • env variables in exec commands are not properly exported #4232
  • odo list showing a duplicate entry of devfile component #4144
  • 'odo app list' prints only applications where at least one s2i component exists #4136
  • debug port-forward does not work on 4.6 cluster #4036
  • add json output for odo env view #4254 (girishramnani)
  • windows path seperator fix #4234 (anandrkskd)

Tests:

  • Modifies WaitForDeploymentRollout() to collect events. #4283 (mik-dass)

Documentation & Discussions:

  • We need clarity around installing and using Operators with odo both on OCP & k8s environments #4130
  • Spring Boot example reports "running on IBM Cloud" #4095
  • Add a note to the Operators docs. [skip ci] #4282 (boczkowska)
  • Update the prow help command link #4268 (prietyc123)
  • Add Open Liberty to devfile doc #4119 (awisniew90)

Closed issues:

  • test-cmd-devfile-status test suite fails on Power #4241
  • Enable 4.6 cluster for odo pr test #4138

Merged pull requests:

Installation of v2.0.3

To install odo, follow our installation guide at docs.openshift.com

After each release, binaries are synced to mirror.openshift.com

* This Changelog was automatically generated by github_changelog_generator

v2.0.2

25 Nov 06:12
585fd6d
Compare
Choose a tag to compare

Release of v2.0.2

v2.0.2 (2020-11-25)

Full Changelog

New features:

  • Provide the way to get list of starter projects with id/display name/description for specific component type #4129
  • odo catalog list components should truncate long descriptions #4044
  • Re-enable support for the sparseCheckoutDir field in devfiles #3933
  • Update configure-installer-tests-cluster-ppc64le to support nodejs12 e2e test #4229 (sarveshtamba)
  • Update configure-installer-tests-cluster-s390x to support nodejs12 e2e test #4215 (zhengxiaomei123)
  • Adding the latest java image ubi8/openjdk-11 in odo supported list #4206 (prietyc123)
  • Trunicate longer devfile description #4150 (mohammedzee1000)
  • Writing unit tests using Gomock #4110 (prietyc123)
  • Adding ubi8/nodejs-12 images as supported #4070 (prietyc123)

Code Refactoring:

  • Cleanup & Refactor kClient generators code before migrating to devfile library #4131
  • Switch to use the parser from devfile/parser in odo repo #4117
  • Add a PreValidate function to generic CLI Run #3604
  • Move functions to separate files in context package #4231 (adisky)
  • Refactors pvc code in occlient and kclient #4226 (mik-dass)
  • Moves route related code from occlient.go to a new file #4213 (mik-dass)
  • Moves project related code from occlient.go to a new file #4211 (mik-dass)
  • Use example from the repo instead of downloading it #4207 (dharmit)
  • List only installed Operators; some refactor #4202 (dharmit)
  • Switch to use parser library #4188 (yangcao77)
  • Updates build version to 2.0.1 #4166 (cdrage)
  • Refactor & cleanup kclient generators code before migrating to devfile/parser #4134 (maysunfaisal)

Bugs:

  • nodejs (devfile) and nodejs/12 (s2i) components are not accessible after push, but java-quarkus (devfile) works fine #4245
  • Parallel test execution fails due to racing with duplicate entry in KUBECONFIG #4190
  • odo list fails with SISSEGV when application has no odo managed components #4183
  • odo should only list the successfully installed Operators #4155
  • odo url describe reported as not supported subcommand in v2.0.0 #4126
  • odo catalog list services -o json throws error when no services are available #4024
  • odo create --s2i flag shows Warning message on 4.6 cluster #4016
  • odo describe --context option is ignored when current directory is a devfile based component #3902
  • The odo test command doesn't give enough feedback, by default; odo test exit status #3899
  • Devfile component names are not present in 'odo catalog list components' output #3827
  • Ignore Configmap mounted in DeploymentConfig #4193 (mcouliba)
  • resolve the panic on odo list when the project contains non-odo DCs #4189 (girishramnani)
  • Update required s2i imagestreams for nodejs and java on IBM Power #4181 (sarveshtamba)
  • Update required s2i imagestreams for nodejs and java on IBM Z. #4180 (zhengxiaomei123)

Tests:

Documentation & Discussions:

  • Document how to setup Operators on a minikube cluster #4103
  • Create a roadmap for the project and add it to readme #4083
  • Remove container image from personal repo in RH openshift document #3833
  • Allow using odo inside a firewall #3824
  • Update release notes #4178 (girishramnani)
  • Changes headings for deploying your first devfile #4167 (cdrage)
  • Fix blog post #4164 (cdrage)
  • Publish blog post #4161 (cdrage)
  • fix: typos [skip-ci] #4158 (metacosm)
  • Add 2.0.1 changelog blog post #4154 (cdrage)
  • Document Operator installation on minikube #4140 (dharmit)

Closed issues:

  • Run pr jobs e2e and integration tests on macOS and windows #4227
  • odo could not be started/used on OS X #4198
  • xUnit/jUnit test report generation #4137
  • Decide a mocking framework for interface #4097

Merged pull requests:

Installation of v2.0.2

To install odo, follow our installation guide at [docs.openshift.com](https://docs.openshift.com/container-platform/latest/cli_reference/openshift_developer_cli/installing-od...

Read more

v2.0.1

26 Oct 16:03
a9fff7d
Compare
Choose a tag to compare

What's new

Secure starter project support

With this release, you can now deploy a component directly from a secure registry.

$ odo create nodejs --registry <secure registry name> --starter --starter-token <starter project token>

App comands

A series of new commands have been added to app.

You can now list, describe and delete an app with the following commands:

$ odo app list
$ odo app describe <app-name>
$ odo app delete <app-name>

PROJECT_SOURCE env variables

PROJECT_SOURCE now works as an environment variable when specifying a workingDir inside a devfile.yaml.

 $ export PROJECT_SOURCE=/tmp/foobar/
- exec:
    commandLine: mvn -Dmaven.repo.local=/home/user/.m2/repository spring-boot:run
    workingDir: ${PROJECT_SOURCE}

Installing odo

Installing odo on Linux

Binary installation

# curl -L https://mirror.openshift.com/pub/openshift-v4/clients/odo/latest/odo-linux-amd64 -o /usr/local/bin/odo
# chmod +x /usr/local/bin/odo

Installing odo on macOS

Binary installation

# curl -L https://mirror.openshift.com/pub/openshift-v4/clients/odo/latest/odo-darwin-amd64 -o /usr/local/bin/odo
# chmod +x /usr/local/bin/odo

Installing odo on Windows

Binary installation

  1. Download the latest odo.exe file.

  2. Add the location of your odo.exe to your GOPATH/bin directory.

Setting the PATH variable for Windows 10

Edit Environment Variables using search:

  1. Click Search and type env or environment.

  2. Select Edit environment variables for your account.

  3. Select Path from the Variable section and click Edit.

  4. Click New and type C:\go-bin into the field or click Browse and select the directory, and click OK.

Setting the PATH variable for Windows 7/8

The following example demonstrates how to set up a path variable. Your binaries can be located in any location, but this example uses C:\go-bin as the location.

  1. Create a folder at C:\go-bin.

  2. Right click Start and click Control Panel.

  3. Select System and Security and then click System.

  4. From the menu on the left, select the Advanced systems settings and click the Environment Variables button at the bottom.

  5. Select Path from the Variable section and click Edit.

  6. Click New and type C:\go-bin into the field or click Browse and select the directory, and click OK.

Full changelog

New features:

  • odo url delete should work without arguments #4106
  • When using a devfile with multiple starter projects, odo should ask the user which one to use #3812
  • Add support for overriding composite commands #3759
  • Release 2.0.1 of odo #4152 (cdrage)
  • feat: Allow composite commands to be overridden #4043 (johnmcollier)
  • Update build version to 2.0.0 #4022 (cdrage)
  • Adds app commands for devfile components #4007 (mik-dass)
  • Update integration testcases and e2e testcases for ppc64le support #4000 (sarveshtamba)
  • Save PROJECT_SOURCE for containers mounting source #3979 (maysunfaisal)
  • Secure starter project support #3743 (GeekArthur)

Code Refactoring:

Bugs:

  • Nit: odo url list shows :// before it is pushed #4109
  • odo storage create should create without a path #4101
  • odo push fails for s2i components #4071
  • odo devfile push command tests failed with error "Failed to create the component: error while waiting for deployment rollout: watch channel was closed"" #4058
  • odo create: --s2i flag is broken #4048
  • Overriding parent devfile's commands no longer works #4038
  • Unable to mount bootstrap volume to deployment config sub path "ODO_S2I_DEPLOYMENT_DIR" on 4.6 cluster #4015
  • component volumeMount path validation error #4005
  • devfile volume component size bug #4004
  • odo rewrite should preserve "unknown" properties of 'metadata' (and other optional properties?) per devfile schema #3968
  • Beta release: Operator Hub does NOT work & tests are disabled (tracking issue) #3932
  • Switching from run to debug mode shows no build but build occurs #3929
  • odo allows devfile commands with duplicate ids #3886
  • Odo fails when devfile component container name is really long #3698
  • nit: dont show url as :// in odo url list #4111 (girishramnani)
  • Update vendor-update makefile target #4086 (johnmcollier)
  • read s2i paths from both Config and ContainerConfig #4068 (kadel)
  • Fixes message indicating no build when run mode is switched #4066 (mik-dass)
  • Update configure-installer-tests-cluster-ppc64le.sh script to import right imagestream for tests. #4065 (sarveshtamba)
  • Default vol mount path to vol name if absent #4045 (maysunfaisal)
  • make odo list's output for no components consistent #4029 (girishramnani)
  • Don't allow duplicate command IDs #4001 (johnmcollier)
  • 3968-add more optional metadata #3987 (yangcao77)
  • Update s2i image for the library change on s390x plaftorm. #3974 (zhengxiaomei123)
  • add container name validation during creation and push #3959 (yangcao77)
  • Fix deletion of files and folders created during watch #3890 (mik-dass)

Tests:

Documentation & Discussions:

  • Unexpected mention of 'crc' in 'kubernetes prerequisites' #4113
  • fix windows installation instructions #4077
  • Update debugging page on how to debug via application + IDEs #3971
  • installing odo documents changes for IBM Z platform #3913
  • Developer CLI odo doc needs update #3878
  • odo cli reference doc still pointing to old refere...
Read more

v2.0.0

22 Sep 18:46
6fbb9d9
Compare
Choose a tag to compare

What's new

Changes to the default deployment method

Devfile is a file format that is used as odo's new deployment engine. Starting from 2.0.0 onwards, Source-to-Image (S2I) is no longer the default deployment method. S2I is still supported and can now be accessed with the --s2i flag from the command-line.

Learn how to deploy your first devfile using devfiles from our Devfile tutorial.

Example on how to download a starter project and deploy a devfile:

$ odo create nodejs --starter
Validation
 ✓  Checking devfile existence [22411ns]
 ✓  Checking devfile compatibility [22492ns]
 ✓  Creating a devfile component from registry: DefaultDevfileRegistry [24341ns]
 ✓  Validating devfile component [74471ns]

Starter Project
 ✓  Downloading starter project nodejs-starter from https://github.com/odo-devfiles/nodejs-ex.git [479ms]

Please use `odo push` command to create the component with source deployed

$ odo push

Validation
 ✓  Validating the devfile [132092ns]

Creating Kubernetes resources for component nodejs
 ✓  Waiting for component to start [5s]

Applying URL changes
 ✓  URL http-3000: http://http-3000-nodejs-foobar.myproject.example.com/ created

Syncing to component nodejs
 ✓  Checking files for pushing [1ms]
 ✓  Syncing files to the component [868ms]

Executing devfile commands for component nodejs
 ✓  Executing install command "npm install" [4s]
 ✓  Executing run command "npm start" [2s]

Pushing devfile component nodejs
 ✓  Changes successfully pushed to component

Deploying a custom Kubernetes controller with odo

With the release of 2.0.0 deploying operators is now out of experimental mode.

Learn how to deploy your first Kubernetes custom controller from our Operator documentation.

Example on how to deploy your first Operator:

$ odo catalog list services
  Operators available in the cluster
  NAME                          CRDs
  etcdoperator.v0.9.4           EtcdCluster, EtcdBackup, EtcdRestore

$ odo service create etcdoperator.v0.9.4/EtcdCluster

odo debug is no longer in technical preview

The odo debug command is no longer in technical preview.

Learn how to debug your component via the CLI or VSCode.

Installing odo

Installing odo on Linux

Binary installation

# curl -L https://mirror.openshift.com/pub/openshift-v4/clients/odo/latest/odo-linux-amd64 -o /usr/local/bin/odo
# chmod +x /usr/local/bin/odo

Installing odo on macOS

Binary installation

# curl -L https://mirror.openshift.com/pub/openshift-v4/clients/odo/latest/odo-darwin-amd64 -o /usr/local/bin/odo
# chmod +x /usr/local/bin/odo

Installing odo on Windows

Binary installation

  1. Download the latest odo.exe file.

  2. Add the location of your odo.exe to your GOPATH/bin directory.

Setting the PATH variable for Windows 10

Edit Environment Variables using search:

  1. Click Search and type env or environment.

  2. Select Edit environment variables for your account.

  3. Select Path from the Variable section and click Edit.

  4. Click New and type C:\go-bin into the field or click Browse and select the directory, and click OK.

Setting the PATH variable for Windows 7/8

The following example demonstrates how to set up a path variable. Your binaries can be located in any location, but this example uses C:\go-bin as the location.

  1. Create a folder at C:\go-bin.

  2. Right click Start and click Control Panel.

  3. Select System and Security and then click System.

  4. From the menu on the left, select the Advanced systems settings and click the Environment Variables button at the bottom.

  5. Select Path from the Variable section and click Edit.

  6. Click New and type C:\go-bin into the field or click Browse and select the directory, and click OK.

Full changelog

New features:

  • implement odo describe for devfile #3644
  • Release 2.0.0 #4021 (cdrage)
  • Move Operator Hub out of experimental mode #3938 (dharmit)
  • Implement clonePath, update source code sync location #3907 (adisky)

Code Refactoring:

  • "odo link" help message should not check for ClusterServiceVersion support #4008
  • API version and schema version tests should be migrated to devfileV2 #3794
  • Do not check for CSV when initializing odo link command #4010 (dharmit)
  • Update odo debug --help screen #3963 (cdrage)
  • Clarify description of the force-build flag in help text for odo push #3958 (johnmcollier)
  • Switch to use project instead of namespace in env #3951 (GeekArthur)
  • Remove the namespace flag from odo #3949 (johnmcollier)
  • Migrate devfile cmd validation to validate pkg #3912 (maysunfaisal)
  • Remove command group type init #3898 (adisky)

Bugs:

  • "odo link -h" shows same message for 3.x & 4.x clusters #3992
  • make goget-tools fails due to go mod dependency #3983
  • Handle edge case when index file is commented in .gitignore #3961
  • Java component build execution requires pom.xml #3943
  • default registry not initialized when user already has a preference.yaml file #3940
  • odo url create shouldn't require a port if only one port exists in the devfile #3923
  • odo push with alternate --run-command should push complete file set upon new pod creation #3918
  • converting s2i items to devfile items does not set the Endpoint's name properly #3910
  • Unexpected EOF during watch stream event decoding, watch channel was closed. #3905
  • odo debug serial tests script panic out #3897
  • Default URL does not propagate to .odo/env/env.yaml and you cannot delete it. #3893
  • Breaking component create without exposing port #3882
  • odo registry list causes panic if preference has not been setup #3842
  • odo watch goes into infinite push loop if ignore flag is used #3819
  • 'odo create' should properly validate devfiles #3778
  • context flag does not work with devfile url create #3767
  • odo log is unusable for multi container components #3711
  • "odo registry add" adds registry for invalid url in devfileV2 #3451
  • Prints help message based on backend cluster #3993 (dharmit)
  • s2i component fix: use Config instead of ContainerConfig for port detection #3957 (kadel)
  • 3923- url creation with optional port flag #3950 (yangcao77)
  • Add mandatory file ignores when using --ignore flag #3942 (maysunfaisal)
  • Fix default registry support #3941 (GeekArthur)
  • Update s2i image from library for ppc64le #3939 (sarveshtamba)
  • update s2i to devfile conversion as per new url design #3930 (adisky)
  • Add test-case for validating devfiles on component create #3908 (johnmcollier)
  • Improve URL format validation #3900 (GeekArthur)
  • implement odo describe for devfile #3843 (metacosm)

Tests:

  • Test failures while running test-cmd-push test suite on ppc64le #3539
  • Test failures while running test-cmd-storage test suite o...
Read more

v2.0.0-beta-1

10 Sep 19:18
Compare
Choose a tag to compare

Release of v2.0.0-beta-1

This is the v2.0.0-beta-1 release of odo!

Similar to our alpha release, we switch the default deployment mechanism from Source-To-Image to Devfile.

In order to start using Devfile, follow our deploying a devfile using odo guide.

Breaking changes:

  • Operator Hub service deployment does not work in this release. We are actively working on getting this fixed for the next beta release. See issue: #3932
  • -o json output may not work for some Devfile functionalities. See: #3521

Please open a GitHub issue if you encounter any other commands that do not work!

Installing v2.0.0-beta-1 of odo

v2.0.0-beta-1 of odo uses devfile as its default deployment mechanism.

Installing odo on Linux

Binary installation

# curl -L https://github.com/openshift/odo/releases/download/v2.0.0-beta-1/odo-linux-amd64 -o /usr/local/bin/odo
# chmod +x /usr/local/bin/odo

Installing odo on macOS

Binary installation

# curl -L https://github.com/openshift/odo/releases/download/v2.0.0-beta-1/odo-darwin-amd64 -o /usr/local/bin/odo
# chmod +x /usr/local/bin/odo

Installing odo on Windows

Binary installation

  1. Download the latest odo.exe file.

  2. Add the location of your odo.exe to your GOPATH/bin directory.

Setting the PATH variable for Windows 10

Edit Environment Variables using search:

  1. Click Search and type env or environment.

  2. Select Edit environment variables for your account.

  3. Select Path from the Variable section and click Edit.

  4. Click New and type C:\go-bin into the field or click Browse and select the directory, and click OK.

Setting the PATH variable for Windows 7/8

The following example demonstrates how to set up a path variable. Your binaries can be located in any location, but this example uses C:\go-bin as the location.

  1. Create a folder at C:\go-bin.

  2. Right click Start and click Control Panel.

  3. Select System and Security and then click System.

  4. From the menu on the left, select the Advanced systems settings and click the Environment Variables button at the bottom.

  5. Select Path from the Variable section and click Edit.

  6. Click New and type C:\go-bin into the field or click Browse and select the directory, and click OK.

Release of v1.2.6

27 Aug 13:11
89b5ab6
Compare
Choose a tag to compare

Release of v1.2.6

v1.2.6 (2020-09-01)

Full Changelog

New features:

  • Applying secret to namespace for authenticated registry for ppc64le #3849 (sarveshtamba)

Bugs:

  • component is left in broken state after redeployment of the pod #3838
  • Fix #3838: Component is left in broken state after redeployment of the pod #3859 (jgwest)

Merged pull requests:

v1.2.6 (2020-08-31)

Full Changelog

New features:

  • odo documents changes for IBM P/Z platform #3725
  • Update test guidelines and link it to the pr template #3687
  • Remove --devfile parameter from non odo create commands. #3661
  • "odo unlink" to unlink a devfile component from an Operator backed service #3563
  • Implement hotReloadCapable flags from devfile v2 spec #3548
  • Migrate odo product under new openshift developer tools and services product #3276
  • Replace unstable mongodb-enterprise operator subscription with percona-server-mongodb-operator #3820 (prietyc123)
  • Applying secret to namespace for authenticated registry for s390x #3802 (zhengxiaomei123)
  • Adds list command of storage for devfile v2 #3788 (mik-dass)
  • Adding plugin handler test makefile target #3787 (prietyc123)
  • Docker test container for travis login #3732 (amitkrout)
  • Adds storage create and delete commands for devfiles. #3626 (mik-dass)

Code Refactoring:

Bugs:

  • zip starter projects should not require URLs ending with .zip #3853
  • odo doesn't properly re-sync all files if a new deployment is created on 'odo push' #3847
  • odo watch redeploys component during first push #3841
  • logging error/irregularities #3829
  • Devfile Mode: 'odo app list' doesn't display app name #3789
  • Devfile run command not started if odo push is run after odo push --debug #3784
  • ingress url does hit for component nodejs in devfile registry #3771
  • Devfile mode: 'odo push' skips the build command #3769
  • Starting from odo v1.2.1 describe command does not include info about linked components #3766
  • 'make test-coverage' failed on s390x platform #3756
  • etcd operator tests fails on 4.4 cluster periodic job #3753
  • Help text gets printed twice for invalid odo commands #3750
  • ALPHA: unable to list components from default devfile registry #3747
  • Devfile mode: the run command process isn't killed, before starting the debug command process, if 'restart' attribute is set as false #3738
  • Unable to install bundler for Ruby image while "odo push" on 4.6 cluster #3683
  • Ask for images work on s390x arch #3670
  • odo v1.2.4 tar.gz binaries for macOS and windows have wrong format #3668
  • push doesn't delete volumes when removed from devfile #3641
  • odo log -f terminates earlier #3610
  • Watch command should better handle file synchronization when push command is invoked before/after the watch #3585
  • --ref/-r flag for odo create doesn't work #3498
  • odo url list fails for s2i components if experimental mode is enabled #3474
  • Sync operation within the Push command does not remove deleted/renamed files when -f flag is set #3460
  • odo watch does not tell me the err on devfile validation failure #3435
  • Devfile v2 issue: additional property exposure is not allowed #3426
  • On windows platform teardown steps fails to delete context because files are still in use #3371
  • "odo catalog list components --all" displays components without displaying name #3340
  • Fix #3841 - odo watch redeploys component during first push #3860 (jgwest)
  • fix: remove requirement for URL to end with .zip #3854 (metacosm)
  • Fixing rvm error and Docker file format for travis login #3813 (amitkrout)
  • remove showing help twice for incorrect commands #3805 (girishramnani)
  • Fix odo describe for component with linked services #3804 (dgolovin)
  • Fix describe to print out linked components list #3790 (dgolovin)
  • Fixes odo url list for s2i components #3728 (mik-dass)
  • Fixes GetRunningPodNameByComponent for the CLI runners #3666 (mik-dass)
  • Sync operation within the Push command does not remove deleted/renamed files #3619 (jgwest)

Tests:

  • UTs fails within env folder #3755
  • Update the parent devfile tests #3638
  • test-cmd-devfile-log teardown steps throws error while accessing projectDir on windows platform #3540
  • odp push throws error of watch channel was closed on ppc64le #3530
  • Updates test for printSupportedParameters to fix flake #3760 (mik-dass)
  • Updates the integration test for parent support. #3739 (mik-dass)
  • Fix odo log flake #3733 (adisky)

Documentation & Discussions:

  • Wrong command present in multicomponent-application documentation ( odo.dev ) #3707
  • How to create a valid URL when using kubernetes in the backend? #3463
  • Remove experimental mode from docs [#3855](https://github.com...
Read more

v2.0.0-alpha-2

13 Aug 15:39
ff06439
Compare
Choose a tag to compare

Release of v2.0.0-alpha-2

This is the v2.0.0-alpha-2 release of odo!

In this release we switch the default deployment mechanism from Source-To-Image to Devfile.

In order to start using Devfile, follow our deploying a devfile using odo guide.

Breaking changes:

  • As of right now, the following commands do not work:
    • odo catalog describe component <component-name>
    • odo catalog describe service <service-name>

Please open a GitHub issue if you encounter any other commands that do not work!

Installing v2.0.0-alpha-2 of odo

v2.0.0-alpha-2 of odo uses devfile as its default deployment mechanism.

Installing odo on Linux

Binary installation

# curl -L https://github.com/openshift/odo/releases/download/v2.0.0-alpha-2/odo-linux-amd64 -o /usr/local/bin/odo
# chmod +x /usr/local/bin/odo

Installing odo on macOS

Binary installation

# curl -L https://github.com/openshift/odo/releases/download/v2.0.0-alpha-2/odo-darwin-amd64 -o /usr/local/bin/odo
# chmod +x /usr/local/bin/odo

Installing odo on Windows

Binary installation

  1. Download the latest odo.exe file.

  2. Add the location of your odo.exe to your GOPATH/bin directory.

Setting the PATH variable for Windows 10

Edit Environment Variables using search:

  1. Click Search and type env or environment.

  2. Select Edit environment variables for your account.

  3. Select Path from the Variable section and click Edit.

  4. Click New and type C:\go-bin into the field or click Browse and select the directory, and click OK.

Setting the PATH variable for Windows 7/8

The following example demonstrates how to set up a path variable. Your binaries can be located in any location, but this example uses C:\go-bin as the location.

  1. Create a folder at C:\go-bin.

  2. Right click Start and click Control Panel.

  3. Select System and Security and then click System.

  4. From the menu on the left, select the Advanced systems settings and click the Environment Variables button at the bottom.

  5. Select Path from the Variable section and click Edit.

  6. Click New and type C:\go-bin into the field or click Browse and select the directory, and click OK.