You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the network migration, the new addresses could not be set in the GUI.
GUI --> "Resource update failed - Can not update ingress-public-ip AddressPool in the metallb namespace"
-->The chrome debug console gave output: 'resource not found'
After investigations, there is a drift between the APIVersions: Frontend Constants
apiVersion: 'metallb.io/v1alpha1',
kind: 'AddressPool',
But in metallb other APIVersions are used: MetalLB deployment
apiVersion: metallb.io/v1beta1
kind: IPAddressPool
So our deliveries will not work with the GUI. Only with kubeadmin and manual patches.
The text was updated successfully, but these errors were encountered:
This is a known issue, should be at least partially addressed by #827. But work on the UI stopped quite some time ago and we have currently no plans to resume it.
During the network migration, the new addresses could not be set in the GUI.
GUI --> "Resource update failed - Can not update ingress-public-ip AddressPool in the metallb namespace"
-->The chrome debug console gave output: 'resource not found'
After investigations, there is a drift between the APIVersions:
Frontend Constants
apiVersion: 'metallb.io/v1alpha1',
kind: 'AddressPool',
But in metallb other APIVersions are used:
MetalLB deployment
apiVersion: metallb.io/v1beta1
kind: IPAddressPool
So our deliveries will not work with the GUI. Only with kubeadmin and manual patches.
The text was updated successfully, but these errors were encountered: