Skip to main content
Version: 0.9

Older releases

Release v0.5.0#

This release of Kore delivers the following major features:

  • Azure subscription automation
    • Kore can now generate and manage Azure Subscriptions on demand for teams, as per AWS and GCP.
    • Uses new common cloud account infrastructure meaning we now have common account factory logic and handling across all three supported providers.
  • Azure Costs
    • Brings feature parity with AWS and GCP for basic resource-level actual cost data being available through Kore.
    • Supports cost imports at a billing account, invoice section or subscription level.
    • Also included a significant improvement of the setup/visibility for cost configuration for all clouds.
  • Crossplane MVP - Kore's new approach to managing cloud services for teams.
    • Kore can now deliver Crossplane, configured and ready to use, into EKS clusters on AWS.
    • Delivers tightly-scoped IAM permissions into Crossplane allowing it to perform just the actions required to deliver the resources needed.
    • Two initial cloud services supported - S3 and RDS (PostgreSQL).
  • Enable Least Privilege
    • For AWS, Kore now supports least-privilege throughout the product, with defined, well-scoped, IAM roles that are, if using AWS Account automation, themselves automatically delivered by Kore.
    • Uses new common cloud account infrastructure so we can apply the same principles to other clouds as appropriate.
  • Custom managed CIDR ranges
    • Allows administrators to define allowable ranges of IP addresses to use for clusters.
    • Teams can use automatic allocation or request smaller/larger ranges within a set of allowable sizes controlled by the admin.
    • Pre-requisite for us to enable peering of networks between clusters, teams, and shared management accounts.
  • AWS private cluster endpoints and networks
    • Allows, in combination with custom CIDR ranges, fully private EKS clusters.
    • Allows Kore-delivered clusters, accounts and VPCs to be peered with management account VPCs.
  • Managed TLS
    • Deploys cert manager to provide HTTPS certificates for users' applications.
  • Consistent and generic handling of cloud organisations and accounts
    • Common logic and code for account automation on all supported cloud providers.
    • Common logic and code for delivering sessions with access to the cloud provider in a permission-scoped way.
    • Will support the replacement of cloud credentials with workload identity.
    • Supports the delivery of least privilege.
    • Reduces security/secret footprint by having a single common place to deal with the secrets and permissions.
    • Extensible to support additional cloud providers using the same codebase and business logic.

Upgrading from v0.4.0#

Before the upgrade#

  • Kore now uses Kubernetes secrets for sensitive data and will need to have these migrated:
    • Use the kubectl context for the kore management cluster.
    • Download and run the interactive script migrations/ from the kore-tools repository.

After the upgrade#

  • Kore Managed AWS Accounts are migrated when v0.5.0 starts; should existing clusters show CloudAccounts as failed, Kore can be restarted to fix:
    • Use the kubectl context for the kore management cluster.
    • kubectl -n kore rollout restart deployment kore-apiserver
  • Kore Costs now has a new configuration experience and implementation. To upgrade:
    • Run kore -t kore-admin get services and note any entries with kind 'kore-costs' or 'kore-costs-engine'.
    • For each of those services, run kore -t kore-admin delete service <name>
    • Reconfigure estimated and actual costs through the UI

Release v0.4.0-beta9#

This release of Kore adds the following key features:

  • Changed from Kores internal configmap to v1.Configmap
  • Bug fixes to the UI services section using to use rather than spec.displayName

Release v0.4.0-beta8#

This release of Kore adds the following key features:

  • Added Azure Pod Identity for external-dns
  • Bug fix, ensure we wait for the cluster to have a success status, before we install domain components
  • Install aad-pod-identity into AKS clusters
  • Team context UI changes

Release v0.4.0-beta7#

This release of Kore adds the following key features:

  • Fixing bug for UI incorrectly handled kore-costs credentials
  • Added AKS Network Policies - allowing the team to override the settings
  • Fixed the kore login bug causing segfault
  • Enable & Disable Users in Kore CLI commands - allowing kore-admins to enable and disable users in kore
  • Kore Robot Token Status Fields - shifting the tokens into the spec rather than status fields
  • Check swagger using --swagger-only so we get faster feedback of failures
  • Added Audit searching and filtering to the UI
  • Automatically publish Helm charts into the Kore Service Catalog
  • Kore Chart - External Database - adding the ability to reference an external database for kore
  • Team and Cluster Identifier fixes the issues around annotations and kore apply
  • Create custom Azure virtual network for AKS clusters
  • Added the /serverinfo endpoint for api details
  • Added network policies to the Kore chart
  • Provided and option to enable EKS controlplane logging
  • Fix Docker Kore Image User Permissions in the CI kore CLI container image
  • Added support for Azure domains
  • Fixed the issue around EKS nodegroup naming

Release v0.4.0-beta6#

This release of Kore adds the following key features:

  • Fixed issues in the GORM database client
  • Displays cluster selections when accessing the kore kubeconfig
  • Fixes character bug caused by long names kubernetes resources

Release v0.4.0-beta5#

This release of Kore adds the following key features:

  • Provides the ability to configure builds on the UI
  • Differentiating between GitHub and gitlab access tokens in container builds
  • Bumping the kore-costs to v0.0.4
  • Adding a fix for lingering ELBs on EKS deletion
  • Rename ServiceCredentials API resource to ServiceAccess, add automatic migration
  • Container build and push feature

Release v0.4.0-beta4#

This release of Kore adds the following key features:

  • Adding a shortname to the namespaceclaim (based on feedback)
  • Allow Kore admins to manage their own team membership/roles
  • Switched kore local to version to 1.17.11
  • Updating the default version of kubernetes for AKE to 1.17

Release v0.4.0-beta3#

This release of Kore adds the following key features:

  • Added service provider for AWS Elasticsearch
  • Added service deployment for cluster installations
  • Added priority class for EKS autoscaler
  • Fixed bug allowing for deletion of clusters with kore DNS zones

Release v0.4.0-beta2#

This release of Kore adds the following key features:

  • Deloying managed domains for EKS clusters

Release v0.4.0-beta1#

This release of Kore adds the following key features:

Release v0.3.0#


This release of Kore adds the following key features:

Smaller additions#


Release v0.2.4#


Bugfix fixing kubeconfig path for kore cli on windows Kubeconfig Paths

Release v0.2.3#


Bugfix release to enable Namespaces not appearing on cluster page

Release v0.2.2#


Bugfix release to enable GSuite token refresh to continue to work for Kore CLI after first login

Release v0.2.1#


Bugfix release to enable GSuite token refresh to work for Kore CLI

Release v0.2.0#


This release of Kore adds the following key features:

  • Security Overview of plans and clusters.
  • Cloud Services (including S3 and managed binding of services into cluster namespaces via Kore-provisioned secrets).
  • GCP Account Management - auto-creation of projects in a configurable way as teams request clusters.
  • GCP GKE Improvements - node pools, auto-scale/sizing re-configuration, release channels and versions are now fully supported.
  • Enhanced management of cluster plans/parameters to allow cluster users and node groups/pools to be managed easily through the UI.



Pre Release v0.2-0-rc2#




Release v0.1.0#


The first beta release of Kore delivers the following key themes:

  • Added GCP Projects for teams (CLI & UI).
  • Single account EKS support.
  • Clusters by Plans only. Ability for operators to control the shape of the plans which teams consume.
  • A formalized release process for Kore.
  • The addition of a team audit trail of operations, view-able from CLI and UI.
  • A new CLI - kore.


  • GCP Projects for teams (CLI & UI)

    - GCP Projects [PR #327](
    • GCP Organization Credentials Verification PR #457
    • GCP IAM Permissions Check PR #368
  • EKS Support

    • Basic EKS Cluster Support #348
    • Add EKS Cluster Build support in the UI #402
  • Plans and Policies

    • limit cluster creation to be only available via a plan #343
    • As a kore admin be able to get, create, update plans in the UI #442
    • Be able to edit an existing cluster configuration once it's built #567
    • Create plan policies associated with teams and plans #536
    • View cluster plans #420
    • Cluster Deployment from Plans #346
  • Audit

  • Stable Kore Releases

    • A release process for kore #345
    • Testing: Create basic infrastructure in which we can produce API-level tests #334
  • Kore CLI

    • Add 'local' command to kore cli #590
    • Tab Completion of Resource #640
    • Stop building korectl #636
    • Korectl Bash Autocompletion #424
  • Other Additions

    • UI: See detailed status of a cluster and its underlying objects #494
    • UI: Allow deletion of a cluster in failed state #493
    • have a way of knowing how and where to authenticate to when i have a cluster #341
    • Know the API endpoint for kore via the UI #443
    • remove alpha from kore local documentation #687
    • make the version displayed at the bottom of every page discretely #686
    • Create & Delete Admin PR #483
    • Korectl Cluster Kubeconfig #444
    • GKE Kubernetes Version PR #462
    • as an owner of a team i want to be able to delete my team #430
    • Apply From Stdin #408
    • invite an admin user to kore #360
    • promote a user to be an admin of kore #359


  • Rename API endpoint ekss/ to eks/ to match other resources #675
  • As a kore administrator I expect to be able to deploy kore using helm with a URL #624


  • Store Client hiding errors #671
  • Kubernetes Deletion Bug #655
  • Team Deletion Bug #654
  • Always check on the team API endpoints whether a team exists PR #651
  • Handle validation errors in kore PR #637
  • EKS resource type doesn't work in the kore CLI #607
  • Create/delete admin is broken in the kore CLI #606
  • Handle trailing slashes for kore profile configure command #638
  • Oauth Redirect URL Bug Fix PR #490
  • Helm Chart HMAC #476
  • Fix Max Attempts on Resource Waits PR #452
  • Deleting GKE before Cluster Fix PR #435
  • Controller Runtime Client GVK PR #434
  • Fix namespace claim wait PR #431
  • GKE Bootstrap Fix PR #454
  • Team Removal with Clusters Bug PR #426
  • Namespace required when setting Allocation via API #417
  • Fix Cloud Provider failing state PR #407
  • fix invalid gke status when no credentials PR #405
  • Fix invalid status for GKE nodes #404
  • Make relevant audit visible to the correct personas #299
  • korectl cls auth doesn't give any context help #296
  • korectl cls auth on it's own gives 404 #295
  • Use the refresh token to refresh expired credentials PR #325
  • When creating a team with an invalid name, it returns 500 #367


  • Examples use different teams and invalid plans which make them hard to use #633
  • Kubernetes Images PR #463
  • Default Option Value PR #428
  • Add kubernetes resource config, clean up custom path override logic PR #414
  • Makefile Images Stage Fix PR #409
  • Kore Admin Delete Check PR #397
  • Enable simple kore UI releases with kore #389
  • Auto Generated Resources PR #388
  • CLI Cleanup & Resource Waits PR #386
  • Fix deepcopy-gen PR #383
  • JSONPath Dependency PR #382
  • WhoAmI Command Rendering Fix PR #381
  • Team Name Regex PR #375
  • Long Description Format PR #374
  • Profile Delete Command PR #373
  • Potential Segmentation Fault PR #370
  • UI Endpoint PR #353
  • Enable APIs PR #349
  • Logrus Caller Report #330

Release v0.0.23#


This release targets being able to use Kore to create, manage and destroy EKS Kubernetes clusters in AWS, with all dependent resources managed (VPC, Subnets, node groups, etc). As this is the first formal release of Kore, it only shows the major features added since the previous pre-release alpha.


Improved & Changed#


Last updated on Aug 5, 2021