This repository was archived by the owner on Jan 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 65
ingress not showing IP address #223
Copy link
Copy link
Open
Description
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 31mWhen 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)
Client version: 0.4.0
Tried with 2 kubernetes versions:
old version
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.12-gke.14", GitCommit:"021f778af7f1bd160d8fba226510f7ef9c9742f7", GitTreeState:"clean", BuildDate:"2019-03-30T19:30:57Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}
new version
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.7-gke.10", GitCommit:"8d9b8641e72cf7c96efa61421e87f96387242ba1", GitTreeState:"clean", BuildDate:"2019-04-12T22:59:24Z", GoVersion:"go1.10.8b4", Compiler:"gc", Platform:"linux/amd64"}
Workaround for kubemci + ManagedCertificate
- Create regular ingress first, and wait for certificate to validate and become active
- Delete ingress and replace with
kubemcione
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels