request help: How to start multiple unrelated ingress-apisix-composite-deployment to load traffic from different sources about apisix-ingress-controller

[bren-ai]

I modified the configuration after installation. The exported deployment, config, and clusterrolebinding are the configurations currently in use after I modified them.

This is my configuration: demo.tgz
Reference documentation: https://apisix.apache.org/zh/blog/2023/10/18/ingress-apisix/#%E5%AE%89%E8%A3%85-apisix-ingress-controller
@Vacant2333 @Revolyssup Thank you very much for the answer

[Revolyssup]

@bren-ai Make sure that you set the watching namespace parameter for each deployment of ingress controller different so that they don't interfere with each other. Here it looks like both controllers are trying to modify the same resource.

[Vacant2333]

@bren-ai Make sure that you set the watching namespace parameter for each deployment of ingress controller different so that they don't interfere with each other. Here it looks like both controllers are trying to modify the same resource.

can we provide a docs for multiple install?

[Vacant2333]

I modified the configuration after installation. The exported deployment, config, and clusterrolebinding are the configurations currently in use after I modified them.

This is my configuration: demo.tgz Reference documentation: https://apisix.apache.org/zh/blog/2023/10/18/ingress-apisix/#%E5%AE%89%E8%A3%85-apisix-ingress-controller @Vacant2333 @Revolyssup Thank you very much for the answer

good! i think we can close the issue now?

[bren-ai]

I want to know how to achieve my goal, How to start multiple unrelated ingress-apisix-composite-deployment to load traffic from different sources

[acuteaura]

This is our values override for running a second controller via the Helm chart. We do this to have an internal-only load balancer, but maybe expanded on what you want to achieve could help us understand what you're actually trying to do here.

ingress-controller:
  config:
    ingressPublishService: apisix/apisix-internal-gateway
    kubernetes:
      ingressClass: apisix-internal
      electionId: ingress-apisix-internal-leader
    apisix:
      serviceName: apisix-internal-admin
      serviceNamespace: apisix
gateway:
  annotations:
    service.beta.kubernetes.io/azure-load-balancer-internal: "true"

Note that you also have to use the ingress name in all your CRDs to not have them processed by both controllers.

[bren-ai]

Thanks for the answer. The purpose is only to safely isolate the traffic entrance, which is divided into public and private traffic entrances. @acuteaura

[kedare]

Is there a way to have multiple independant instances sharing the same objects ?
For example I have 2 instances of the apisix helm chart (each with their own etcd and apisix-ingress-controler), 1 for private routes (via internal ALB) and another for public routes (via public LB).

I have some services that need to expose both public and private routes, how can I achieve this ?

I get the same issue so far, facing the the object has been modified; please apply your changes to the latest version and try again error.

For example should I add something to this for it to work ? (it only needs to be in the public one in this example)

apiVersion: apisix.apache.org/v2
kind: ApisixPluginConfig
metadata:
  name: ecgator-plugins
spec:
  plugins:
    - name: proxy-rewrite
      enable: true
      config:
        uri: /upload

[acuteaura]

Write two objects (with whatever templating/generator you use) and set spec.ingressClassName