Closed janlauber closed 2 years ago
@janlauber By any chance do you have more than 1 Citrix ingress controller running in the same cluster? Also, have you configured serviceclass
value while bringing up the Ingress controller?
hey @apoorvakamath
no there is just 1 Citrix ingress controller running in this cluster.
also as you see in my helm chart deployment configuration, there is no serviceClass
configured.
So I got it working without the IPAM Service. It works while adding some annotations to the service manifest:
# example
apiVersion: v1
kind: Service
metadata:
name: apache
annotations:
service.citrix.com/class: 'citrix'
service.citrix.com/frontend-ip: '10.0.26.72'
service.citrix.com/service-type-0: 'HTTP'
labels:
name: apache
spec:
externalTrafficPolicy: Local
type: LoadBalancer
ports:
- name: http
port: 8080
targetPort: http
selector:
app: apache
ah and also I added the serviceClass citrix
to the helm deployment of the citrix-ingress-controller
Dear Citrix team
Describe the bug When I configured the Citrix ingress controller as written in the documentation, there is no way my services will get the VIP configured in the IPAM controller.
To Reproduce Deployed Helm Charts Manifests:
Testdeployment with service (from your docs):
Expected behavior The service loadBalancerIP address should get configured in the service and show up when looking at it with:
and not like this:
Logs In the logs of the ingress controller is the following output printed:
Thank you very much for your support!