Hello everyone,
In the process of migrating apigee installation from apigeectl to helm charts in apigee 1.11.0 (since apigeectl will not be supported in apigee 1.12), i found out that the documentation https://cloud.google.com/apigee/docs/hybrid/v1.11/helm-migration#configuration-properties-changes suggests to Create an additional apigeeIngressGateway stanza in the overrides file. I don’t see the point for this, since i am using ingressGateways in the old apigeectl installation instead (to configure each individual instance of the Apigee ingress gateway)
Does anyone have an idea about this and would it have any consequences if i did not perform this change.
Best regards.
Hello,
I didn’t do any change to the ingressGateways stanza and I upgraded to 1.12 from 1.11, everything is working fine.
1 Like
Hi @bilal_bouaziz , my understanding was that some of the configuration settings (pod resource requests come to mind) for ingressGateways are now separated out from the way they are done in earlier versions, and requires some rework of your overrides values. If you’re taking defaults on everything for ingressGateway, you might not have a problem skipping it.
1.12 doc
https://cloud.google.com/apigee/docs/hybrid/v1.12/config-prop-ref#apigeeingressgateway
https://cloud.google.com/apigee/docs/hybrid/v1.12/config-prop-ref#ingressgateways
vs 1.10 doc
https://cloud.google.com/apigee/docs/hybrid/v1.10/config-prop-ref.html#ingressgateways
3 Likes
Thank you for your response. we performed the migration and upgrade on a non prod environment without adding the stanza and everything went well.
2 Likes