Releases

Highlights of v0.0.3 release

This release is mainly focused around improving stability and refactorings, but there is one notable feature worth mentioning.

Resolution of host name for target Resource

As users are completely free to name Target Resource(Deployment or DeploymentConfig), Service and VirtualServices etc, we improved resolution strategy which previously relied on pattern matching.

By resolving Services that could possibly match the Target Resource, we look for all Virtual Services that specify that Service/Host.

Support full local cluster dns names

VirtualServices and DesinationRules can now be defined with both short form or full dns name using the Host field and istio-workspaces will still be able to find the connections.

Example:

ratings vs ratings.namespace.svc.cluster.local

 

New features

Bug fixes

Latest dependencies update

  • build(deps): to 0.14.0 (#356)

  • github.com/google/go-github to 29.0.3 (#364)

  • github.com/onsi/ginkgo to 1.12.0 (#360)

  • github.com/onsi/gomega to 1.9.0 (#362)

  • github.com/operator-framework/operator-sdk to 0.15.2 (#366)

  • github.com/spf13/cobra to 0.0.6 (#369)

  • github.com/spf13/viper to 1.6.2 (#352)

  • go.uber.org/goleak to 75e74d7 (#377)

  • gopkg.in/fsnotify.v1 to 1.4.9 (#384)

Project infrastructure

Testing

  • fix(tests): controls tp version env var (#392), by @bartoszmajsak

  • test(generator): use generator in int test scenario (#386), by @aslakknutsen

  • fix(e2e): add to the members array instead of replacing it (#380), by @aslakknutsen

  • fix(test): generate a suitable deployment resource for a pure k8s ins… (#376), by @aslakknutsen

  • fix: uses username defined by IKE_CLUSTER_USER instead of oc whoami (#355), by @bartoszmajsak

  • feat: introduces ENV_FILE var to overwrite variables used in tests (#354), by @bartoszmajsak == Highlights of v0.0.2 release

Below you will find an exhaustive list of all the improvements since last release, but those are the most important changes:

Support for multiple development strategies

In v0.0.1 we only supported preparation of a telepresence session. In this release we’ve expanded this to allow specifying a strategy per Ref in the Session object.

Currently, we support two strategies: telepresence for local development and prepared-image.

The new prepared-image strategy allow you to setup a route for a pre-built image. It is a perfect fit for a CI system.

When using ike cli, the develop command will use the telepresence strategy while create will use the prepared-image strategy. The create command is non blocking compared to develop. The create command comes with a companion command delete to clean up when e.g. PR is merged.

Installing operator locally

Now you also can deploy operator to your local namespace, so where your project lives. This way only your namespace is watched.

Simply invoke ike install-operator -l

To learn more head over to the official docs.

All changes in this release

New features

Bug fixes

Latest dependencies update

  • github.com/coreos/prometheus-operator to 0.30.0 (#114)

  • github.com/go-cmd/cmd to 1.1.0 (#311)

  • github.com/google/go-github to 28.1.1 (#262)

  • github.com/google/shlex to e7afc7f (#316)

  • github.com/onsi/ginkgo to 1.10.3 (#297)

  • github.com/onsi/gomega to 1.7.1 (#299)

  • github.com/operator-framework/operator-sdk to 0.13.0 (#320)

  • github.com/spf13/viper to 1.6.1 (#317)

  • go.uber.org/goleak to 7380c5a (#310)

  • sigs.k8s.io/controller-runtime to 0.3.0 (#287)

  • ubi8/ubi-minimal to 8.1 (#303)

Project infrastructure

Testing

Highlights of v0.0.1 release

Inspired by @bobbytables talk from OSCON 2018 we started hacking on open source tooling realizing the idea of safe development on production. Now, after long weeks in the making, we are extremely happy to announce the first release of istio-workspace project.

With this toolkit, we strive to enable developers to:

Develop their microservices locally, using the tools they love!

Connect to other services in the cluster and test their changes!

All of that without interfering with other developers and users!

All of it based on CNCF open source projects such as Istio and Telepresence.

How does it work?

  • ike develop wraps Telepresence and let you start local development while being connected to the real services in the cluster

    • in addition, it will restart the process when any files have been changed (see --watch flag)

  • istio-workspace operator takes care of configuring routes in Istio so that only you can hit your service under development

To learn more head over to the official docs.