Can the ingress support helm upgrade from different repo to the same API gateway?

[szelee]

Hi,

This is a great controller that automate the apigateway integration with microservices. I am using CI/CD with helm upgrade to deploy. At the moment, I am exploring the options to use only 1 api gateway with different paths for different repository that we have.

I have tested it but getting the following error:

##[error]Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: namespace: default, name: apigw-dev, existing_kind: networking.k8s.io/v1beta1, Kind=Ingress, new_kind: networking.k8s.io/v1beta1, Kind=Ingress

Just wondering if it's possible to update the existing api gateway by just adding more path? Look forward to hearing from you.

Regards, Szelee

[Magizhchi]

This PR should address updating the existing APIGW - https://github.com/awslabs/amazon-apigateway-ingress-controller/pull/15

[kuwarprashant11]

When do you think PR #15 will be available test?