Use v1 extensions because v1beta1 is being removed

[rooftopcellist]

To remain compatible with Kubernetes 1.22 and Openshift 4.9, we need to start using the extensions/v1 API as the extensions/v1beta1 is being removed.

All beta Ingress APIs (the extensions/v1beta1 and networking.k8s.io/v1beta1 API versions)

The beta CustomResourceDefinition API (apiextensions.k8s.io/v1beta1)

Context: https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/

[rooftopcellist]

When testing this out on OCP 4.9, I found another usage of an API that is not in 4.9: rbac.authorization.k8s.io/v1beta1. This was not listed in https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/#api-changes. I checked all API usage in our code against the newly recommended deprecation list: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22

[rooftopcellist]

I am now able to deploy the awx-operator, deploy awx with it, and run a job.

[chadams@chadams-work awx-operator]$ oc version
Client Version: 4.6.8
Server Version: 4.9.0-0.nightly-2021-08-23-224104
Kubernetes Version: v1.22.0-rc.0+5c2f7cd

[slaurencelle]

i try yours solution but still unable to have my awx pod beoing create, i am not using openshift nor okd or rancher.
Just using the opensource Kubernetes stack.

i am using this yaml file to deploy the awx pods

cat awx-deploy.yml

apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
name: awx-demo
spec:
service_type: nodeport
ingress_type: none
hostname: awx-demo.example.com

this is for testing if it work i will start personnalize my deployment file.

Any idea what is not working, again ?
regards,

Stephane