When creating an ingress using kubemci the ingress is created but the resource is not showing an IP address:
NAME HOSTS ADDRESS PORTS AGE
global XXXXXX 80 31m
When the ingress is installed withoutkubemci (regular ingress) everything works ok, which suggests that the problem is not with the global ip or ssl certificates annotations.
The loadbalancer works, so it seems just a cosmetic problem, however this can affect controllers that need to fetch the IP for the controller, like the ManagedCertificate controller that does not seem to work with kubemci (**workaround)
When creating an ingress using
kubemci
the ingress is created but the resource is not showing an IP address:When the ingress is installed without
kubemci
(regular ingress) everything works ok, which suggests that the problem is not with the global ip or ssl certificates annotations.The loadbalancer works, so it seems just a cosmetic problem, however this can affect controllers that need to fetch the IP for the controller, like the ManagedCertificate controller that does not seem to work with
kubemci
(**workaround)Tried with 2 kubernetes versions:
old version
new version
Workaround for
kubemci
+ManagedCertificate
kubemci
one