Skip to content

Latest commit

 

History

History
110 lines (78 loc) · 5.85 KB

releasenotes_V0.6.2.md

File metadata and controls

110 lines (78 loc) · 5.85 KB

Release Notes 0.6.2

This release provides improvements in working with the Keptn Bridge and API as well as troubleshooting support by creating a support-archive through the Keptn CLI.

🚀 Improved automation support with API extensions and deep linking into Keptn Bridge:

  • Keptn API: Internally used endpoints for retrieving Keptn status information are now accessible through the public API, e.g.:

    • GET /v1/project - Returns all projects managed by Keptn.
    • GET /v1/project/{projectName} - Returns meta-information about a project.
    • GET /v1/project/{projectName}/stage - Returns stages from a project.
    • GET /v1/project/{projectName}/stage/{stageName}/service - Returns services from a stage.

  • Keptn Bridge: To provide a convenient and secure way of working with the Keptn Bridge, the Keptn CLI command: keptn configure bridge --action=expose has been introduced. This command allows exposure of the Bridge via Istio or Nginx ingress. In addition, basic authentication with username and password can be activated. For improved automation support, deep links into the Keptn Bridge are provided that point to certain UI components.

🦑 Argo CD for deployment: With this release, Keptn can be used in combination with Argo CD / Argo Rollout as explained by a tutorial. While Argo CD is used for deploying an Argo Rollout, Keptn is leveraged for testing, evaluating, and promoting this rollout.

🌟 Easier bug reporting with support-archives: The CLI now offers the command: keptn generate support-archive that fetches all log files from a Keptn deployment and puts them into an archive. This archive can then be used for troubleshooting without connection to the Kubernetes cluster.

Last but not least, this release addresses limitations and issues in regard to create a Keptn project with a not-initialized Git repo.

Keptn Specification

Implemented Keptn spec version: 0.1.3

New Features

Platform Support / Installer

  • Allow specifying a domain when installing Keptn (e.g., keptn install --domain=127.0.0.1.nip.io) #1482
  • Allow to re-use existing nginx-ingress installation #1712

Keptn Core

  • configuration-service:
    • Improve troubleshooting for git related problems #1637

CLI Enhancements

  • Create a support-archive for troubleshooting #1549
  • Provide a CLI command for exposing Keptn Bridge #1560

API

  • Introduce an API-gateway that proxies requests to configuration-service #1510
  • Query a list of projects #1559
  • Provide an endpoint for exposing Keptn's Bridge via Istio or nginx ingress #1153

Bridge

  • Use icons for event types #1352
  • Deep links into Bridge components #1316
  • Format SLOs as floats #1681

Fixed Issues

  • API:
    • Do not overwrite source property of cloud events #1643
  • Configuration-service & Shipyard-service:
    • Catch a not initialized Git repo by creating an initial commit #1545
    • Fixed error handling (issue with quality-gates multi-stage setups) #1695
  • Installer:
    • Check for ImagePullBackOff errors for the installer job #1521
    • Do not overwrite an existing Keptn installation #1376
  • Bridge:
    • Provide proper deep-link functionality for "Problem detected" events #1557
    • Bridge preselects wrong evaluation event in heatmap view #1518
    • Heatmap shows undefined color for test results of type fail #1580
  • Lighthouse:
    • Evaluating "<=5%" was interpreted as "<=5" (missing percent sign) #1498
  • Helm:
    • Helm Service should not require an outbound Internet connection #1532

Refactoring

  • Added multiple unit tests to improve code coverage
  • Refactor api-service and configuration-service #1510
  • Refactor go-utils #1492
  • Change APIVersion from apps/v1beta1 to apps/v1 #1529

Development Workflow

  • Improve Travis-CI workflow
  • Added GitHub actions for linting
  • Updated contribution guide

Good to know / known limitations

  • Cluster-internal non-http traffic does not use VirtualServices for Blue/Green deployments #1715
  • For old limitations, please see Release 0.6.1.
  • After executing keptn configure domain, an already exposed Keptn Bridge is no longer accessible #1752
  • The installation option --gateway=NodePort currently uses the internal node IP and, hence, a NodePort installation only works if the node can be directly accessed #1708