Apigee Hybrid 1.2 Installation and Deployment Issues

Google Cloud Apigee
1

Hi I am trying to setup hybrid1.2 on GKE Cluster (with 2 nodes as I am on GCP free tier trial account).

I have followed the steps mentioned in docs at - https://cloud.google.com/apigee/docs/hybrid/v1.2/install-apply-hybrid

I didn’t get any issues and pods are up and running. I created a proxy to test but it’s not able to hit the url and fetch the response. In Apigee UI the proxy has been deployed successfully. When i try to hit using the gateway ip directly

35.xx.240.xx/sampleproxy i get 404 not found.

I already had a domain outside of Google Domain. I also tried to setup Cloud DNS as given in link https://cloud.google.com/apigee/docs/hybrid/v1.2/lets-encrypt

I obtained two static ip addresses as given at link below and have mapped it to my run time istio and mart

https://cloud.google.com/apigee/docs/hybrid/v1.2/static-ip

Below are the entries in overrides.yaml file.

ingress:
  enableAccesslog: true
  runtime:
    loadBalancerIP: x.xx.103.112
  mart:
    loadBalancerIP: x.xx.233.202

However, this also doesn’t work after making the entries for

$APIGEECTL_HOME/apigeectl init -f my-overrides.yaml -c istio

virtualhosts:
  - name: default
    hostAliases: ["apitest.xxxx.co.in"]

..

mart:
  hostAlias: "mart.xxx.co.in"


envs:
    # Apigee environment name.
  - name: test
    # Service accounts for sync and UDCA.
    serviceAccountPaths:
      synchronizer: ./service-accounts/sync-sa.json
      
      udca: ./service-accounts/udca-sa.json

If someone knows what I am doing wrong please help.

thanks,

Aakash

2

Any particular reason why you decided to install 1.2 instead of 1.3, which is the latest Hybrid version?

Because you’re using https, you cannot hit gateway IP directly and expect it to work correctly.

I didn’t get any issues and pods are up and running.

The running pods still do not mean that there are no underlying problems with access to the control plane. You might have errors in the pod’s logs.

The fact that the proxy reports installed in the Edge UI is a good news.

Can you, please try to call proxy using cluster IP via instructions in this page:

https://github.com/yuriylesyuk/ahr/wiki/API-Ingress-Troubleshooting

This will let yo separate a Hybrid runtime problem from the Istio gateway configuration problem.

The you can use steps from this page to make sure that your certificate is configured correctly.

https://github.com/yuriylesyuk/ahr/wiki/Hybrid-Ingress-Self-signed-Cert-Walkthrough

There is more information on ingress troubleshooting at this Hybrid 1.3 page

https://github.com/yuriylesyuk/ahr/wiki/Hybrid-Ingress-Walkthrough-1.3

including useful diagram. But you need to make some mental adjustments, as apigee routing is defined slightly differently between 1.2 and 1.3.

3

thanks i will try this.. recommended way during one of the training was to try first on 1.2 before moving to 1.3 so this is the reason of using an older version.