cisco.ios VS awx-operator

cisco.ios has been released with bugfixes and features (changelog).

cisco.ios 4.4.0

A few updates on what the Networking team is working on: * we are developing some content related to interfaces and ospf * we are working on extending the capabilities of nxos_bgp_global to support the creation of neighbour templates; earlier we could use the module to just apply one that is already created * we are planning to release a filter plugin (ace_popper) which acts on a set of acls facts gathered from a network appliance, and removes ace entries on the basis of some matching criteria

Depedencies on other collections (defined in galaxy.yml) are resolved and installed by ansible-galaxy - unless you're doing an offline installation, then you need to do this manually. Missing collection dependencies are notified about at the time of installation.

I read here https://github.com/ansible-collections/cisco.ios/issues/698 that it seems to be by decide to not be able to remove single vlan from a trunk (if i have understand it correct) so i guess you need to do something like this?

There have been a few networking releases this week: * ansible.netcommon 3.1.0 has been released with new features (changelog) * cisco.ios 3.3.0 has been released with new features (changelog) * cisco.iosxr 3.3.0 has been released with new features (changelog)

Taking a look at the github requirements page:

We're happy to announce that AWX Version 23.0.0 is now available! We're happy to announce that AWX Operator version 2.5.2 is now available!

So what did I do wrong here ?! I followed the guide step by step (https://github.com/ansible/awx-operator) but still failed.

AH. I checked and found this open issue: https://github.com/ansible/awx-operator/issues/1391

Please see the releases pages for more details: AWX, Operator.

awx has an operator - https://github.com/ansible/awx-operator

I'm now attempting a POC to use k8s, despite having limited experience with it. I've successfully deployed AWX using the https://github.com/ansible/awx-operator on k8s, which includes Postgres. However, I'm unsure how to configure AWX with the plays that we publish in our CI/CD pipeline.

You can look at the operator source code https://github.com/ansible/awx-operator to see exactly what it does.

I have setup AWX Operator from https://github.com/ansible/awx-operator and everything works ok. But there's an annoying warning when running modules from the community.vmware collection.

We're happy to announce that AWX version 21.10.2 is now available! We're happy to announce that AWX Operator version 1.1.3 is now available! This AWX version downgrades a dependency which was causing tracebacks to appear often in the logs of some deployments.