Hi Alexandru. That is a side-effect of updating the helm charts used to deploy the nginx ingress controller. It should not cause any problems as this service is not intended to be used directly by other applications. The test should be updated to check for the new service names. Regards, Isac. On Tue, Mar 30, 2021 at 6:08 AM Dimofte, Alexandru < alexandru.dimofte@intel.com> wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
Hello guys,
One of our tests is checking the kube services and after the upgrade of nginx-ingress-controller I found that some services names were changed:
E AssertionError: One or more services are missing from the list
E assert ['ic-nginx-in...', 'kube-dns'] == ['ic-nginx-ing...', 'kube-dns']
E At index 0 diff: *'ic-nginx-ingress-controller'* != *'ic-nginx-ingress-ingress-nginx-controller'*
E Full diff:
E - [*'ic-nginx-ingress-controller'*, *'ic-nginx-ingress-default-backend'*, 'kube-dns']
E + [*'ic-nginx-ingress-ingress-nginx-controller'*,
E + *'ic-nginx-ingress-ingress-nginx-controller-admission'*,
E + 'kube-dns']
Is this an expected behavior, a known issue?
Should we open a bug or we actually need to update our test?
Thanks!
Kind regards,
Alex Dimofte
[image: Logo Description automatically generated]
Dimofte Alexandru
Software Engineer
STARLINGX TEAM
Skype no: +40 336403734
Personal Mobile: +40 743167456
alexandru.dimofte@intel.com
Intel Romania
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
