Skip to content

Releases: rancher/eks-operator

v0.1.0-rc7

07 Jul 17:01
Compare
Choose a tag to compare
v0.1.0-rc7 Pre-release
Pre-release

Fixed bug:
Prevents nil pointer exception by no longer attempting to record error on deletion

v0.1.0-rc6

03 Jul 20:48
Compare
Choose a tag to compare
v0.1.0-rc6 Pre-release
Pre-release

Changes:
errors now recorded in status
added generated fields to status

v0.1.0-rc5

27 Jun 00:33
Compare
Choose a tag to compare
v0.1.0-rc5 Pre-release
Pre-release

Bug fixes:
fixed bug where status would update to active before checking node groups

v0.1.0-rc4

26 Jun 20:59
Compare
Choose a tag to compare
v0.1.0-rc4 Pre-release
Pre-release

Bug fixes:

  • Fix node instance role deletion by giving each created role a unique name

v0.1.0-rc3

25 Jun 04:18
Compare
Choose a tag to compare
v0.1.0-rc3 Pre-release
Pre-release

Bugs fixed:
*cluster not deleting because another cluster is referencing the same node instance role

Other changes:
*controller generated values now set in status to avoid being overwritten

v0.1.0-rc2

16 Jun 22:26
Compare
Choose a tag to compare
v0.1.0-rc2 Pre-release
Pre-release

Can provision EKS clusters with the following configurable properties:

  • region
  • public access
  • public access CIDR sources
  • private access
  • using secrets containing AWS access key and secret key, "amazonec2credentialConfig-accessKey" and "amazonec2credentialConfig-secretKey" respectively
  • using instance profiles
  • can set VPC/subnets/security-groups/service-role or they will be created for you
  • node groups

Node group properties:

  • max size
  • min size
  • desired size
  • disk size
  • ssh key
  • gpu
  • instance type
  • labels
  • can set Kubernetes version after creation to prevent automatic update when updating cluster

v0.1.0-rc1

16 Jun 21:34
Compare
Choose a tag to compare
v0.1.0-rc1 Pre-release
Pre-release

Can provision EKS clusters with the following configurable properties:

  • region
  • public access
  • public access CIDR sources
  • private access
  • using secrets containing AWS access key and secret key, "amazonec2credentialConfig-accessKey" and "amazonec2credentialConfig-secretKey" respectively
  • using instance profiles
  • can set VPC/subnets/security-groups/service-role or they will be created for you
  • node groups

Node group properties:

  • max size
  • min size
  • desired size
  • disk size
  • ssh key
  • gpu
  • instance type
  • labels
  • can set Kubernetes version after creation to prevent automatic update when updating cluster