Configure api_vip and ingress_vip after cluster installation
th3penguinwhisperer opened this issue · 4 comments
Description
I have installed a cluster using openshift-installer IPI method on libvirt. I was thinking about using the keepalived operator and creating a second ingresscontroller to have the ingresscontroller on a VIP.
However it seems that this actually is already the case for vsphere and some others.
I don't see an option for libvirt (was perhaps thinking about switching to ovirt but that would not be a trivial change).
How can I change the MCO so that a VIP is deployed and my ingress controller uses it (if possible without reinstalling the cluster)?
Steps to reproduce the issue:
- Install openshift through libvirt
Describe the results you received:
Ingress controller does not listen on a VIP.
Describe the results you expected:
Ingress controller having it's own VIP.
Additional information you deem important (e.g. issue happens only occasionally):
Output of oc adm release info --commits | grep machine-config-operator:
machine-config-operator https://github.com/openshift/machine-config-operator 8530c27d3d9b6155923d348058bc025a6a98ec3c
Additional environment details (platform, options, etc.):
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.