# Kubernetes - Ingress - Multiple IDP?

**URL:** <https://discuss.pomerium.com/t/kubernetes-ingress-multiple-idp/155>\
**Category:** Support\
**Tags:** idp, k8s\
**Created:** [September 15, 2022, 6:05pm UTC](https://discuss.pomerium.com/t/kubernetes-ingress-multiple-idp/155 "2022-09-15T18:05:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![denis](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@denis](https://discuss.pomerium.com/u/denis)\
**Post date:** [September 17, 2022, 3:50am UTC](https://discuss.pomerium.com/t/kubernetes-ingress-multiple-idp/155/3 "2022-09-17T03:50:07Z")

</div>

You need deploy two instances of Pomerium into your cluster.

The following has to be changed compared to vanilla installation. Assuming you name your installations `one` and i.e. `two`:

1. Namespace: `pomerium` =\> `pomerium-one`
2. Global settings: `global` =\> `global-one`
3. Databases MUST be distinct.
4. Controller name: `pomerium.io/ingress-controller` =\> `pomerium.io/ingress-controller-one`
5. `IngressClass`: `pomerium` =\> `pomerium-one`
6. Authenticate URLs should be distinct - i.e. `https://authenticate-one.corp.com`

You may use `kustomize` that is part of `kubectl` to create a variation of the installation: create a folder `pomerium-one` with the following two files:

**`kustomization.yaml`**

```auto
namespace: pomerium-one
bases:
  - https://raw.githubusercontent.com/pomerium/ingress-controller/main/deployment.yaml
patchesStrategicMerge:
  - deployment.yaml
patches:
  - target:
      kind: IngressClass
      name: pomerium
    patch: |-
      - op: replace
        path: /metadata/name
        value: pomerium-one
      - op: replace
        path: /spec/controller
        value: pomerium.io/ingress-controller-one

```

and **`deployment.yaml`** :

```auto
apiVersion: apps/v1
kind: Deployment
metadata:
  name: pomerium
  namespace: pomerium
spec:
  template:
    spec:
      containers:
        - name: pomerium
          args:
            - all-in-one
            - --pomerium-config=pomerium-one
            - --update-status-from-service=$(POMERIUM_NAMESPACE)/pomerium-proxy
            - --metrics-bind-address=$(POD_IP):9090
            - --name=pomerium.io/ingress-controller-one

```

From that directory, run `kubectl apply -k .` and it should deploy an installation for `pomerium-one`. Now repeat the same for `pomerium-two`, and create secrets and appropriate global configurations.

Now you may start assigning `spec.ingressClass` `pomerium-one` and `pomerium-two` to the `Ingress` objects to make them use different Pomerium installations (and identity providers).

---

_[View the full topic](https://discuss.pomerium.com/t/kubernetes-ingress-multiple-idp/155)._