By: Mahendran Mookkiah Account Admin 15 Sep 2020 at 3:23 p.m. CDT

4 Responses
Mahendran Mookkiah gravatar
## Background Gluu 3.1.6 deployed in Kubernetes by following the instruction from [here](https://github.com/GluuFederation/gluu-docker/tree/3.1.6/examples/kubernetes/gke) ## Expected documentation I expected Gluu to provide upgrade instruction on every release for Kubernetes/container based deployments. I found the instruction in one release but not in another. Example I don't find the [4.1 equivalent instruction ](https://gluu.org/docs/gluu-server/4.1/upgrade/#kubernetes-upgrading-instructions)in other versions (Ex: 4.0 and 4.2) ## Actual documentation We see upgrade from 3.1.x to 4.1 instruction only [available for VM based deployment](https://gluu.org/docs/gluu-server/4.1/upgrade/#upgrade-31x-to-40) Side Note: The link to the file 101-ox.ldif on [this](https://gluu.org/docs/gluu-server/4.1/upgrade/#kubernetes-upgrading-instructions) page is broken.Side Note: The link to the file 101-ox.ldif on [this](http://) page is broken. Please help documenting the steps to upgrade every version from previous release. I am happy to contribute documenting if instruction and container native update script is provided.

By Aliaksandr Samuseu staff 15 Sep 2020 at 4:24 p.m. CDT

Aliaksandr Samuseu gravatar
Hi, Mahendran. I've asked the dev team to share their thoughts.

By Mohammad Abudayyeh staff 16 Sep 2020 at 2:09 a.m. CDT

Mohammad Abudayyeh gravatar
Hey Mahendran, The reason why there is no clear path is because its not officially supported. We need to discuss an upgrade path for you. All our upgrade paths start from 4.0 and onwards. Perhaps a new `4.2.1` installation after our release this week and than a move of ldifs. Let me discuss with my team and we will get back to you. https://github.com/GluuFederation/cloud-native-edition https://gluu.org/docs/gluu-server/4.2/installation-guide/install-kubernetes/ Thanks, Mohammad

By Michael Schwartz staff 16 Sep 2020 at 10 a.m. CDT

Michael Schwartz gravatar
In 3.x.x, Docker Edition was a licensed offering. So use of that software without a support contract transgressed the license. Another result was that because Ceva did not have any contract with Gluu, we did not have any record of a production deployment of 3.x using GKE. Doing a 3.x to 4.x migration is never an in-place upgrade--not in VM's or K8. It always involves export/import. To do this migration, we need to update our quote. Upgrade projects are a "project". It will require planning, testing and a cutover. This is outside of support.

By Mohammad Abudayyeh staff 20 Sep 2020 at 11:57 p.m. CDT

Mohammad Abudayyeh gravatar
Hey Mahendran, This ticket can be re-opened. Please consider updating your support status. Best, Mohammad