How to Migrate Apigee hybrid from apigeectl (1.10.4) to helm-based (1.11.1)

Google Cloud Apigee Knowledge Hub
,
1

Hello All,

In this video I go through the process of migrating a Apigee Hybrid 1.10.4 installed with apigeectl on a gke cluster to a helm based Apigee Hybrid on 1.11.1

I follow the google cloud public docs for this here and here .
I start out using the migration script to migrate from apigeectl to helm and then use the helm upgrade commands to upgrade the Apigee Hybrid component pods from 1.10.4 to 1.11.1.
Note that the --force argument is required for the pods to be updated to the new image (1.11.1) and I perform this from 22:35 in the video.
Apigee Community (for Q&A): https://community.apigee.com

6 Likes
2

This is awesome, thanks for sharing!

3

Thanks for sharing Ayo! This is really cool.

4

Hi Ayos,
we have tried to update helm but we are getting below error,

Issue: Issue in performing helm migration and installing helm charts as part of Apigee Hybrid Upgrade to 1.11.1.

Current Error:

Error: template: apigee-org/templates/organization.yaml:462:31: executing “apigee-org/templates/organization.yaml” at <.Values.apigeeIngressGateway.tolerations>: can’t evaluate field tolerations in type interface {}

  1. Previously, we able to identify that one of the fields from the “ingressGateways” components in not properly indented, to be specific is the “tolerations” field, and requested the Cx to try run the commands again using the newly provided organization.yaml file.

Result: It didn’t help the issue, still the Cx is facing the error.

  1. Update the following entries into the override file and try to run the command.

tolerations:

  • key: “key1”
    operator: “Equal”
    value: “value1”
    effect: “NoExecute”
    tolerationSeconds: 3600

Result: But this also not helped to resolve the current issue.

Appreciate your help

5

Hi,

so we have identified the issue affecting the ingressGateways and ApigeeingressGateways and have updated our config property reference doc with this.

To apply common configuration across all instances of the Apigee ingressGateway see this link.

You can also configure each individual instance of Apigee ingress gateway you may have using this link where you would see properties you want to manage the individual instances separately as "ingressGateways.name

You can apply the changes to the ingressGateways properties with the apigee-org chart and that should fix the issue.