internet/awx-operator
3
0
Fork 0
mirror of https://github.com/ansible/awx-operator.git synced 2026-05-08 22:33:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #800 from ggiinnoo/readme-dummy-proof

Browse Source 
Added namespace warning | added apply command for missing namespace
This commit is contained in:
Shane McDonald
2022-02-23 09:30:19 -05:00
committed by GitHub
parent 58f30fb96c c81b78aad6
commit fbc2d3475c
1 changed files with 24 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
README.md
View File

@@ -106,23 +106,22 @@ Now you need to deploy AWX Operator into your cluster. Clone this repo and `git
``` ```
$ export NAMESPACE=my-namespace $ export NAMESPACE=my-namespace
$ make deploy $ make deploy
cd config/manager && /home/user/awx-operator/bin/kustomize edit set image controller=quay.io/ansible/awx-operator:0.14.0 /home/user/awx-operator/bin/kustomize build config/default | kubectl apply -f -
/home/user/awx-operator/bin/kustomize build config/default | kubectl apply -f - namespace/my-namespace created
namespace/my-namespace created customresourcedefinition.apiextensions.k8s.io/awxbackups.awx.ansible.com created
customresourcedefinition.apiextensions.k8s.io/awxbackups.awx.ansible.com created customresourcedefinition.apiextensions.k8s.io/awxrestores.awx.ansible.com created
customresourcedefinition.apiextensions.k8s.io/awxrestores.awx.ansible.com created customresourcedefinition.apiextensions.k8s.io/awxs.awx.ansible.com created
customresourcedefinition.apiextensions.k8s.io/awxs.awx.ansible.com created serviceaccount/awx-operator-controller-manager created
serviceaccount/awx-operator-controller-manager created role.rbac.authorization.k8s.io/awx-operator-leader-election-role created
role.rbac.authorization.k8s.io/awx-operator-leader-election-role created role.rbac.authorization.k8s.io/awx-operator-manager-role created
role.rbac.authorization.k8s.io/awx-operator-manager-role created clusterrole.rbac.authorization.k8s.io/awx-operator-metrics-reader created
clusterrole.rbac.authorization.k8s.io/awx-operator-metrics-reader created clusterrole.rbac.authorization.k8s.io/awx-operator-proxy-role created
clusterrole.rbac.authorization.k8s.io/awx-operator-proxy-role created rolebinding.rbac.authorization.k8s.io/awx-operator-leader-election-rolebinding created
rolebinding.rbac.authorization.k8s.io/awx-operator-leader-election-rolebinding created rolebinding.rbac.authorization.k8s.io/awx-operator-manager-rolebinding created
rolebinding.rbac.authorization.k8s.io/awx-operator-manager-rolebinding created clusterrolebinding.rbac.authorization.k8s.io/awx-operator-proxy-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/awx-operator-proxy-rolebinding created configmap/awx-operator-manager-config created
configmap/awx-operator-manager-config created service/awx-operator-controller-manager-metrics-service created
service/awx-operator-controller-manager-metrics-service created deployment.apps/awx-operator-controller-manager created
deployment.apps/awx-operator-controller-manager created
``` ```
Wait a bit and you should have the `awx-operator` running: Wait a bit and you should have the `awx-operator` running:
@@ -139,6 +138,8 @@ So we don't have to keep repeating `-n $NAMESPACE`, let's set the current namesp
$ kubectl config set-context --current --namespace=$NAMESPACE $ kubectl config set-context --current --namespace=$NAMESPACE
``` ```
It is important to know that when you do not set the default namespace to $NAMESPACE that the `awx-operator-controller-manager` might get confused.
Next, create a file named `awx-demo.yml` with the suggested content below. The `metadata.name` you provide, will be the name of the resulting AWX deployment. Next, create a file named `awx-demo.yml` with the suggested content below. The `metadata.name` you provide, will be the name of the resulting AWX deployment.
**Note:** If you deploy more than one AWX instance to the same namespace, be sure to use unique names. **Note:** If you deploy more than one AWX instance to the same namespace, be sure to use unique names.
@@ -159,6 +160,12 @@ Finally, use `kubectl` to create the awx instance in your cluster:
$ kubectl apply -f awx-demo.yml $ kubectl apply -f awx-demo.yml
awx.awx.ansible.com/awx-demo created awx.awx.ansible.com/awx-demo created
``` ```
Or, when you haven't set a default namespace
```
$ kubectl apply -f awx-demo.yml --namespace=$NAMESPACE
awx.awx.ansible.com/awx-demo created
```
After a few minutes, the new AWX instance will be deployed. You can look at the operator pod logs in order to know where the installation process is at: After a few minutes, the new AWX instance will be deployed. You can look at the operator pod logs in order to know where the installation process is at: