# awx.ansible.com down?

**URL:** <https://forum.ansible.com/t/awx-ansible-com-down/36338>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [February 16, 2022, 4:29pm UTC](https://forum.ansible.com/t/awx-ansible-com-down/36338 "2022-02-16T16:29:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andy\_MacDonald](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@Andy\_MacDonald](https://forum.ansible.com/u/Andy_MacDonald)\
**Post date:** [February 16, 2022, 4:29pm UTC](https://forum.ansible.com/t/awx-ansible-com-down/36338/1 "2022-02-16T16:29:06Z")

</div>

error: unable to recognize “awx-demo.yml”: no matches for kind “AWX” in version "[awx.ansible.com/v1beta1](http://awx.ansible.com/v1beta1)

Trying to pull this into our AKS cluster and hitting this. Looks like [awx.ansible.com](http://awx.ansible.com) does not resolve.

% dig [awx.ansible.com](http://awx.ansible.com) @1.1.1.1

; \<\<\>\> DiG 9.10.6 \<\<\>\> [awx.ansible.com](http://awx.ansible.com) @1.1.1.1  
;; global options: +cmd  
;; Got answer:  
;; -\>\>HEADER\<\<- opcode: QUERY, status: NXDOMAIN, id: 23994  
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:  
; EDNS: version: 0, flags:; udp: 1232  
;; QUESTION SECTION:  
;[awx.ansible.com](http://awx.ansible.com). IN A

;; AUTHORITY SECTION:  
[ansible.com](http://ansible.com). 3600 IN SOA [andy.ns.cloudflare.com](http://andy.ns.cloudflare.com). [dns.cloudflare.com](http://dns.cloudflare.com). 2267590434 10000 2400 604800 3600

;; Query time: 23 msec  
;; SERVER: 1.1.1.1#53(1.1.1.1)  
;; WHEN: Wed Feb 16 11:28:43 EST 2022  
;; MSG SIZE rcvd: 103

Anyone know whats going on?

Thanks

---

<div class="post-metadata">

**Author:** ![kdelee](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kdelee/32/193_2.png) [@kdelee](https://forum.ansible.com/u/kdelee)\
**Post date:** [February 23, 2022, 9:17pm UTC](https://forum.ansible.com/t/awx-ansible-com-down/36338/2 "2022-02-23T21:17:09Z")

</div>

[awx.ansible.com](http://awx.ansible.com) is the reference to the Custom Resource Type in kubernetes, not a domain name.

When you install the operator to a namespace, you define these extensions of the kubernetes api

…copying from the awx-operator readme…

$ export NAMESPACE=my-namespace  
$ make deploy  
/home/user/awx-operator/bin/kustomize build config/default | kubectl apply -f -  
namespace/my-namespace created  
[customresourcedefinition.apiextensions.k8s.io/awxbackups.awx.ansible.com](http://customresourcedefinition.apiextensions.k8s.io/awxbackups.awx.ansible.com) created  
[customresourcedefinition.apiextensions.k8s.io/awxrestores.awx.ansible.com](http://customresourcedefinition.apiextensions.k8s.io/awxrestores.awx.ansible.com) created  
[customresourcedefinition.apiextensions.k8s.io/awxs.awx.ansible.com](http://customresourcedefinition.apiextensions.k8s.io/awxs.awx.ansible.com) created  
serviceaccount/awx-operator-controller-manager created  
[role.rbac.authorization.k8s.io/awx-operator-leader-election-role](http://role.rbac.authorization.k8s.io/awx-operator-leader-election-role) created  
[role.rbac.authorization.k8s.io/awx-operator-manager-role](http://role.rbac.authorization.k8s.io/awx-operator-manager-role) created  
[clusterrole.rbac.authorization.k8s.io/awx-operator-metrics-reader](http://clusterrole.rbac.authorization.k8s.io/awx-operator-metrics-reader) created  
[clusterrole.rbac.authorization.k8s.io/awx-operator-proxy-role](http://clusterrole.rbac.authorization.k8s.io/awx-operator-proxy-role) created  
[rolebinding.rbac.authorization.k8s.io/awx-operator-leader-election-rolebinding](http://rolebinding.rbac.authorization.k8s.io/awx-operator-leader-election-rolebinding) created  
[rolebinding.rbac.authorization.k8s.io/awx-operator-manager-rolebinding](http://rolebinding.rbac.authorization.k8s.io/awx-operator-manager-rolebinding) created  
[clusterrolebinding.rbac.authorization.k8s.io/awx-operator-proxy-rolebinding](http://clusterrolebinding.rbac.authorization.k8s.io/awx-operator-proxy-rolebinding) created  
configmap/awx-operator-manager-config created  
service/awx-operator-controller-manager-metrics-service created  
deployment.apps/awx-operator-controller-manager created

It looks to me like perhaps you are trying to create an AWX in a namespace that does not have the operator/does not ave the api extensions

Perhaps walking through the operator installation one more time and making sure you are using the same namespace for everything may help you get past your problem  
[https://github.com/ansible/awx-operator#awx-operator](https://github.com/ansible/awx-operator#awx-operator)