Unable to recognize "bpm-ingress.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"
Article ID: KB0071734
Updated On:
| Products | Versions |
|---|---|
| TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) | 5.0.0, 5.1.0, 5.2.0, 5.2.1, 5.2.2 |
Description
This error occurs while BPM Enterprise (BPME) is being configured on a Kubernetes cluster. While deploying bpm-ingress.yaml, below error is seen:-
# kubectl apply -f bpm-ingress.yaml
error: unable to recognize "bpm-ingress.yaml": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"
BPME provides the below sample yaml configurations in bpm-ingress.yaml file -
*****bpm-ingress.yaml ******* apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: "bpm-ingress" namespace: bpm ..........
Environment
All supported Kubernetes environments
Resolution
The sample configuration files are only provided as a guide and can be modified as needed.
For this error, check the available APIs from Kubernetes and correct them -
Example:-
The below command returns the API version for Network policies as "networking.k8s.io/v1".
Replace the Network policy API with the networking.k8s.io/v1 in the bpm-ingress.yaml file -
For this error, check the available APIs from Kubernetes and correct them -
Example:-
The below command returns the API version for Network policies as "networking.k8s.io/v1".
# kubectl api-resources
NAME SHORTNAMES APIVERSION NAMESPACED KIND
bindings v1 true Binding
componentstatuses cs v1 false ComponentStatus
…..
prioritylevelconfigurations flowcontrol.apiserver.k8s.io/v1beta2 false PriorityLevelConfiguration
ingressclasses networking.k8s.io/v1 false IngressClass
ingresses ing networking.k8s.io/v1 true Ingress
networkpolicies netpol networking.k8s.io/v1 true NetworkPolicy
runtimeclasses node.k8s.io/v1 false RuntimeClass
Replace the Network policy API with the networking.k8s.io/v1 in the bpm-ingress.yaml file -
*****bpm-ingress.yaml ******* apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: "bpm-ingress" namespace: bpm ..........
Issue/Introduction
This article documents an error that may be seen while configuring BPM Enterprise 5.x on a Kubernetes cluster.
Additional Information
Internal reference id - ABE-2435
Feedback
Yes
No
Powered by
