search

netscaler / netscaler-k8s-ingress-controller

NetScaler Ingress Controller for Kubernetes:
https://developer-docs.citrix.com/projects/citrix-k8s-ingress-controller/en/latest/
308 stars 91 forks source link

Way to predict the hash of created lbvservers? #632

Open pbptaker opened 7 months ago

pbptaker commented 7 months ago

We try to replace an ansible backed adc config using this product. We have several lb vservers where we use a backup-vserver as failover. If I want to specify this particular failover vserver we currently use the following annotation (which is working):

service.citrix.com/lbvserver: >- {"backupvserver":"prefix-servicename_port_lbv_b3x6qzolfuhy3557f6doopsdfdddz52ce6","connfailover":"stateful"}

This particular string b3x6qzolfuhy3557f6doopsdfdddz52ce6 is not known before. So in fact we have to apply the config twice. Once to learn the name of the backupverver, and once to add this name to the original vserver.

I tried to somehow predict this hash. Tried a base64 from the k8s-servicename (wrong).

I would like to know how this hash is being created. Using this I could prefill the backup server name. Thank you

ankits123 commented 7 months ago

@pbptaker just would like to know how many and how often the backup vserver is created . I suppose if there is only one back up vserver then it would be better create it manually(just like default secret) and refer it in any ingress. We will discuss this internally and get back. Please let us know on the above suggestion.

CC : @dheerajng

pbptaker commented 6 months ago

Hi ankits123

Thanks. Well we have about 25 vservers on which we have a backup-verver each. Doing things manually when we can do it automatically is not really an ideal solution in our opinion.

br

pbptaker