Skip to content

Changelog for 1.13.1 #270

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: release-1.13.1
Choose a base branch
from
Open

Changelog for 1.13.1 #270

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,4 +110,24 @@ All notable changes to this project will be documented in this file. The format
### Changed
- AKO library has been upgraded. User have to update CRD definitions and AKO to 1.11.1 before upgrading AMKO to 1.11.1.

## AMKO-1.12.1

### Added:
- AMKO now claims support for Kubernetes 1.28, 1.29 and OCP 4.14

### Changed:
- PKI Profile used in GSLB Site Persistence can be added via `GlobalDeploymentPolicy` and `GSLBHostRule`

## AMKO-1.13.1

### Added:
- AMKO now claims support for Kubernetes 1.31 and OCP 4.17
- AMKO now support multitenancy at namespace level. This feature allows AMKO to map each namespace in Kubernetes/OpenShift cluster uniquely to a tenant in Avi.
- AMKO now supports OpenShift Routes with `spec.subdomain` field using the [`defaultDomain`](https://github.com/vmware/global-load-balancing-services-for-kubernetes/blob/release-1.13.1/docs/crds/gdp.md?plain=1#L128) field in GDP object.
- AMKO now has ability to support only control plane health monitoring.

### Bugs fixed:
- Fixed an issue where AMKO was not adding a new GS poolmember if GSLBHostrule was defined with publicIP
- Improved logic to remove stale health monitors created by AMKO


10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,16 +20,16 @@ AMKO is aware of the following object types:
For Kubernetes clusters:
| **Components** | **Version** |
| -------------- | ----------- |
| Kubernetes | 1.23-1.27 |
| Kubernetes | 1.27-1.31 |
| AKO | 1.13.1 |
| AVI Controller | 21.1.6 - 30.1.1 |
| AVI Controller | 22.1.3 - 31.1.1 |

For openshift clusters:
| **Components** | **Version** |
| -------------- | ----------- |
| Openshift | 4.10-4.13 |
| Openshift | 4.14-4.17 |
| AKO | 1.13.1 |
| AVI Controller | 21.1.6 - 30.1.1 |
| AVI Controller | 22.1.3 - 31.1.1 |

#### Pre-requisites
To kick-start AMKO, we need:
Expand Down Expand Up @@ -159,7 +159,7 @@ kubectl apply -f <output_dir>/amko/crds/
helm list -n avi-system

NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
amko-1598451370 avi-system 1 2023-06-19 10:00:31.609195757 +0000 UTC deployed amko-1.10.1 1.10.1
amko-1598451370 avi-system 1 2024-06-19 10:00:31.609195757 +0000 UTC deployed amko-1.12.1 1.12.1
```

*Step4*
Expand Down
Loading