Openstack ingress must comply with the common Ingress resource api version that is now being used by the nginx-ingress-controller app: "networking.k8s.io/v1" for the Ingress resources.
Update was based on Kubernetes release docs:
networking.k8s.io/v1beta1 == 1.14 to 1.18
networking.k8s.io/v1 = 1.19+
Severity:
Critical: WRO (armada or fluxcd) will not be applied on WRCP 22.06+ since nginx-controller is already using the new apiVersion by default.
Steps to Reproduce:
Install stx master +
Upload stx-openstack
Apply the stx-openstack app
Expected Behavior:
Application should be successfully applied.
Actual Behavior:
Application failed to apply due to a apiVersion mismatch between openstack and platform Ingress resources.
Reproducibility:
Reproducible
System Configuration:
N/A
Timestamp/Logs:
Logs for a failed apply of a test FluxCD stx-openstack app:
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl get helmrelease -n openstack
NAME READY STATUS AGE
garbd False dependency 'openstack/ingress' is not ready 3m28s
ingress False install retries exhausted 3m28s
mariadb False dependency 'openstack/ingress' is not ready 3m28s
memcached False dependency 'openstack/mariadb' is not ready 3m28s
nginx-ports-control True Release reconciliation succeeded 3m28s
openstack-psp-rolebinding True Release reconciliation succeeded 3m28s
rabbitmq False dependency 'openstack/memcached' is not ready 3m28s
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl -n openstack describe helmrelease ingress
Name: ingress
Namespace: openstack
Labels: chart_group=openstack-ingress
Annotations: <none>
API Version: helm.toolkit.fluxcd.io/v2beta1
Kind: HelmRelease
(...)
Status:
Conditions:
Last Transition Time: 2022-06-27T16:43:43Z
Message: install retries exhausted
Reason: InstallFailed
Status: False
Type: Ready
Last Transition Time: 2022-06-27T16:43:43Z
Message: Helm install failed: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"
Brief Description:
Openstack ingress must comply with the common Ingress resource api version that is now being used by the nginx-ingress- controller app: "networking. k8s.io/ v1" for the Ingress resources.
Update was based on Kubernetes release docs:
networking. k8s.io/ v1beta1 == 1.14 to 1.18 k8s.io/ v1 = 1.19+
networking.
Severity:
Critical: WRO (armada or fluxcd) will not be applied on WRCP 22.06+ since nginx-controller is already using the new apiVersion by default.
Steps to Reproduce:
Install stx master +
Upload stx-openstack
Apply the stx-openstack app
Expected Behavior:
Application should be successfully applied.
Actual Behavior:
Application failed to apply due to a apiVersion mismatch between openstack and platform Ingress resources.
Reproducibility:
Reproducible
System Configuration:
N/A
Timestamp/Logs:
Logs for a failed apply of a test FluxCD stx-openstack app:
[sysadmin@ controller- 0 ~(keystone_admin)]$ kubectl get helmrelease -n openstack psp-rolebinding True Release reconciliation succeeded 3m28s memcached' is not ready 3m28s
NAME READY STATUS AGE
garbd False dependency 'openstack/ingress' is not ready 3m28s
ingress False install retries exhausted 3m28s
mariadb False dependency 'openstack/ingress' is not ready 3m28s
memcached False dependency 'openstack/mariadb' is not ready 3m28s
nginx-ports-control True Release reconciliation succeeded 3m28s
openstack-
rabbitmq False dependency 'openstack/
[sysadmin@ controller- 0 ~(keystone_admin)]$ kubectl -n openstack describe helmrelease ingress openstack- ingress fluxcd. io/v2beta1 27T16:43: 43Z 27T16:43: 43Z k8s.io/ v1beta1"
Name: ingress
Namespace: openstack
Labels: chart_group=
Annotations: <none>
API Version: helm.toolkit.
Kind: HelmRelease
(...)
Status:
Conditions:
Last Transition Time: 2022-06-
Message: install retries exhausted
Reason: InstallFailed
Status: False
Type: Ready
Last Transition Time: 2022-06-
Message: Helm install failed: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Ingress" in version "networking.
Test Activity:
Developer Testing
Workaround:
None