Restoring just gives 404 page not found?

Environment
k3s version v1.27.4+k3s1 (36645e73)
go version go1.20.6

OS: Ubuntu 20.04.6 LTS
AWX Operator: 2.5.1

Description
I read the tips/troubleshooting.md and found no logs or anything that seemed suspicious or relevant.
My issue is I am trying to restore from a backup created using the /2.5.1//backup/README.md and /2.5.1/restore/README.md walkthroughs
I have been able to successfully backup and restore on 0.30.0, but since having made a clean 2.5.1 install, and having decided now is the time for backup and restore testing, I have not been able to get it to work again.
Step to Reproduce

I set up my initial vm using the walkthrough in /2.5.1/README.md. I included /2.5.1/acme#readme since I have a cloudflare account.

my acme/issuer.yaml:
---
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: awx-issuer
spec:
  acme:
    # The email address to be registered with ACME CA
    email: <email>

    # The URL of the ACME API endpoint.
    # In Let's Encrypt, this is one of the following:
    #   Production: https://acme-v02.api.letsencrypt.org/directory
    #   Staging   : https://acme-staging-v02.api.letsencrypt.org/directory
    server: https://acme-v02.api.letsencrypt.org/directory

    privateKeySecretRef:
      name: awx-issuer-account-key

    solvers:
      - dns01:
          cloudflare:
            email: <email
            apiTokenSecretRef:
              name: cloudflare-api-token-secret
              key: api-token

my acme/kustomization.yaml:
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: awx

generatorOptions:
  disableNameSuffixHash: true

secretGenerator:
  - name: cloudflare-api-token-secret
    type: Opaque
    literals:
      - api-token=<cloudflareapitoken>

resources:
  - issuer.yaml

My base/awx.yaml:
---
apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
  name: awx
spec:
  admin_user: admin
  admin_password_secret: awx-admin-password

  ingress_type: ingress
  ingress_tls_secret: awx-secret-tls
  hostname: <awx.hostname.site>

  ingress_annotations: |
    cert-manager.io/issuer: awx-issuer
    traefik.ingress.kubernetes.io/router.middlewares: default-redirect@kubernetescrd

  postgres_configuration_secret: awx-postgres-configuration

  postgres_storage_class: awx-postgres-volume
  postgres_storage_requirements:
    requests:
      storage: 8Gi

  projects_persistence: true
  projects_existing_claim: awx-projects-claim

  web_replicas: 1
  task_replicas: 1

  postgres_init_container_resource_requirements: {}
  postgres_resource_requirements: {}
  web_resource_requirements: {}
  task_resource_requirements: {}
  ee_resource_requirements: {}
  init_container_resource_requirements: {}

  # Uncomment to reveal "censored" logs
  #no_log: false

My base/kustomization.yaml:
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: awx

generatorOptions:
  disableNameSuffixHash: true

secretGenerator:
  - name: awx-postgres-configuration
    type: Opaque
    literals:
      - host=awx-postgres-13
      - port=5432
      - database=awx
      - username=awx
      - password=<awx_pg_pw>
      - type=managed

  - name: awx-admin-password
    type: Opaque
    literals:
      - password=<awx_admin_pw>

resources:
  - pv.yaml
  - pvc.yaml
  - awx.yaml

I then created a backup/awxbackup.yaml:

---
apiVersion: awx.ansible.com/v1beta1
kind: AWXBackup
metadata:
  name: awx-backup-20230906210105
  namespace: awx
spec:
  deployment_name: awx
  backup_pvc: awx-backup-claim

  # Uncomment to reveal "censored" logs
  #no_log: "false"

and went through the steps to get the backup folder, tar.gz it and upload it to my storage.

I then setup a new VM for restoring. I performed all the steps as in 1. except the kubectl apply -k base´. I have an ansible playbook with all of this if that would help, as I am automating everything.

I then prepare for restore:

        - sudo mkdir -p /data/backup
        - sudo chmod 755 /data/backup
        - mv backup.tar.gz /data/backup/
        - tar -xzf /data/backup/backup.tar.gz -C /data/backup
        - kubectl apply -k restore
        - update restore/awxrestore.yaml with name of backup folder

---
apiVersion: awx.ansible.com/v1beta1
kind: AWXRestore
metadata:
  name: awxrestore-2023-09-06
  namespace: awx
spec:
  deployment_name: awx

  # Parameters to restore from AWXBackup object
  #backup_name: awxbackup-2021-06-06

  # Parameters to restore from existing files on PVC (without AWXBackup object)
  backup_pvc: awx-backup-claim
  backup_dir: /backups/tower-openshift-backup-2023-09-06-210119

  # Uncomment to reveal "censored" logs
  #no_log: false

I then apply restore with kubectl apply -f ~/awx-on-k3s/restore/awxrestore.yaml, and it runs successfully and ends without any failures. see image.

I update my cloudflare A record that points my awx.my.domain to the new VM, ensuring vm has port 80 and 443 open, and when I confirm in chrome that the domain I am reaching has the IP that my new vm has, I see 404 page not found. Chrome does not cry about missing cert, so that was sent successfully by traefik.

Logs
I got not error messages, and no logs show failures, EXCEPT kubectl -n awx logs -f deployment/awx-task -c awx-task:

again this did not seem relevant to me.
When I run kubectl -n awx get awx,all,ingress,secrets I get

I do not see any issues here whatsoever as well, and I did check the logs as requested in tips/troubleshooting.md
Hope you are able to help me figure out where I went wrong!

@toutas
Hi, thanks for filling the issue and providing extremely detailed information for your issue! These are super helpful for me to understand your situation.
Your procedures and investigation are adequate and do not appear to be major oversights.
So, to make further investigation, first, you should identify the components that are not working as expected. To do this, break down the components that make up the system and build on the successes of smaller tests.

Server side:

The pod awx-web can respond to HTTP request
The service awx-service can route your traffic to the pod
Cert Manager can issue new certificate
The ingress awx-ingress can route your HTTP request to the pod through the service and can use correct certificate

Cloudflare side:

The A record for your FQDN is correct

Client side:

Your FQDN can be resolved as new IP address (local DNS cache has been updated)

Overall:

Test AWX

1. The pod awx-web can respond to HTTP request
On your K3s host, test with curl over HTTP (not HTTPS).
# Determine the IP address of the `awx-web` pod
$ kubectl -n awx get pod -o wide
NAME                                               READY   STATUS    RESTARTS   AGE     IP           NODE                  NOMINATED NODE   READINESS GATES
...
awx-web-968db44d8-44tj7                            3/3     Running   0          6m41s   <IP_ADDRESS>   kuro-awx01.krkb.lab   <none>           <none>

# Send HTTP request to the port 8052 of the pod. Expected output is:
$ curl http://<IP_ADDRESS>:8052/api/
{"description":"AWX REST API","current_version":"/api/v2/","available_versions":{"v2":"/api/v2/"},"oauth2":"/api/o/","custom_logo":"","custom_login_info":"","login_redirect_override":""}

2. The service awx-service can route your traffic to the pod
On your K3s host, test with curl over HTTP (not HTTPS).
# Determine the IP address of the `awx-service` service
$ kubectl -n awx get service
NAME                                              TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
...
awx-service                                       ClusterIP   <IP_ADDRESS>   <none>        80/TCP     9m39s

# Send HTTP request to the port 80 of the service. Expected output is:
$ curl http://<IP_ADDRESS>:80/api/
{"description":"AWX REST API","current_version":"/api/v2/","available_versions":{"v2":"/api/v2/"},"oauth2":"/api/o/","custom_logo":"","custom_login_info":"","login_redirect_override":""}

3. Cert Manager can issue new certificate
On your K3s host, check the logs for issuer. Ensure that the logs show the success of issuing certificate.
# Determine the certificate that generated by Cert Manager
$ kubectl -n awx get certificate
NAME             READY   SECRET           AGE
awx-secret-tls   True    awx-secret-tls   23m

# Check Status and Events of the certificate
$ kubectl -n awx describe certificate awx-secret-tls
...
Spec:
  Dns Names:
    awx.example.com
  Issuer Ref:
    Group:      cert-manager.io
    Kind:       Issuer
    Name:       awx-issuer
  Secret Name:  awx-secret-tls
  Usages:
    digital signature
    key encipherment
Status:
  Conditions:
    Last Transition Time:  2023-09-07T13:08:46Z
    Message:               Certificate is up to date and has not expired
    ...
  Not After:               2023-12-06T12:08:41Z
  Not Before:              2023-09-07T12:08:42Z
  ...
Events:
  Type    Reason     Age   From                                       Message
  ----    ------     ----  ----                                       -------
  Normal  Issuing    24m   cert-manager-certificates-trigger          Issuing certificate as Secret does not exist
  Normal  Generated  24m   cert-manager-certificates-key-manager      Stored new private key in temporary Secret resource "awx-secret-tls-7qlk9"
  Normal  Requested  24m   cert-manager-certificates-request-manager  Created new CertificateRequest resource "awx-secret-tls-b4v7v"
  Normal  Issuing    23m   cert-manager-certificates-issuing          The certificate has been successfully issued

4. The ingress awx-ingress can route your HTTP request to the pod through the service and can use correct certificate
On your K3s host, test with curl over HTTP (not HTTPS).
# Determine the IP address of the `awx-ingress` ingress
$ kubectl -n awx get ingress
NAME          CLASS     HOSTS             ADDRESS         PORTS     AGE
awx-ingress   traefik   awx.example.com   <IP_ADDRESS>   80, 443   2m52s

# Send HTTP request with --resolve to imitate DNS name resolution. Expected output is:
$ curl --resolve awx.example.com:80:<IP_ADDRESS> http://awx.example.com/api/
{"description":"AWX REST API","current_version":"/api/v2/","available_versions":{"v2":"/api/v2/"},"oauth2":"/api/o/","custom_logo":"","custom_login_info":"","login_redirect_override":""}

# Send HTTP request with --resolve to imitate DNS name resolution. Expected output is:
$ curl -k --resolve awx.example.com:443:<IP_ADDRESS> https://awx.example.com/api/
{"description":"AWX REST API","current_version":"/api/v2/","available_versions":{"v2":"/api/v2/"},"oauth2":"/api/o/","custom_logo":"","custom_login_info":"","login_redirect_override":""}

# Ensure HTTPS connection is established with correct certificate (-v is appended).
$ curl -kv --resolve awx.example.com:443:<IP_ADDRESS> https://awx.example.com/api/
* Added awx.example.com:443:<IP_ADDRESS> to DNS cache
* Hostname awx.example.com was found in DNS cache
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to awx.example.com (<IP_ADDRESS>) port 443 (#0)
...
* Server certificate:
*  subject: CN=awx.example.com
*  start date: Sep  7 12:08:42 2023 GMT
*  expire date: Dec  6 12:08:41 2023 GMT
*  issuer: C=US; O=(STAGING) Let's Encrypt; CN=(STAGING) Artificial Apricot R3
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
...

5. The A record for your FQDN is correct
Please double check on Cloudflare.
6. Your FQDN can be resolved as new IP address (local DNS cache has been updated)
On your client, test your name resolution with dig or nslookup.
$ nslookup awx.example.com
...
Name:   awx.example.com
Address: <IP_ADDRESS>

7. Test AWX
On your client, test with curl.
# Test with explicitly specified IP address
$ curl -kv --resolve awx.example.com:443:<IP_ADDRESS> https://awx.example.com/api/

# Final test
$ curl -v https://awx.example.com/api/

Tips:
If you are getting 404s even though everything is fine on the server side and name resolution is fine on the client side, check for network reachability or firewall problems.
One possibility is that you have been routed to another server with the same IP address.
If you want to enable access logs for your traefik on your K3s, invoke folliwing and wait until the pod traefik-* is requreated and in Running state.
$ sudo tee /var/lib/rancher/k3s/server/manifests/traefik-config.yaml <<EOF
---
apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
  name: traefik
  namespace: kube-system
spec:
  valuesContent: |-
    logs:
      access:
        enabled: true
EOF

$ kubectl -n kube-system get pod
NAME                                     READY   STATUS      RESTARTS   AGE
...
traefik-899bbd849-q2czv                  1/1     Running     0          44s
...

$ kubectl -n kube-system logs -f traefik-899bbd849-q2czv
...
<IP_ADDRESS> - - [07/Sep/2023:13:52:01 +0000] "GET /api/ HTTP/1.1" 200 186 "-" "-" 31 "awx-awx-ingress-awx-example-com@kubernetes" "http://<IP_ADDRESS>:8052" 43ms

Hope this helps.

@kurokobo thank you for your quick response! I will go through these tomorrow local time, hopefully I will be able to figure out it out based on your info and post a solution for anyone else.
I will give an update afterwards.

@kurokobo I have been able to go through your list now, and it starts failing with the 404 page not found when I attempt
curl --resolve awx.my.doman:80:<IP_ADDRESS> http://awx.my.domain/api/ on the VM hosting k3s.
In steps 1-3 everything seems fine, e.g. I get
kubectl -n awx get service
NAME                                              TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
awx-operator-controller-manager-metrics-service   ClusterIP   <IP_ADDRESS>    <none>        8443/TCP   14m
awx-postgres-13                                   ClusterIP   None            <none>        5432/TCP   12m
awx-service                                       ClusterIP   <IP_ADDRESS>   <none>        80/TCP     12m
ubuntu@awx-restore:~$ curl --resolve awx.my.domain:80:<IP_ADDRESS> http://awx.my.domain/api/
ubuntu@awx-restore:~$ curl http://<IP_ADDRESS>:80/api/
{"description":"AWX REST API","current_version":"/api/v2/","available_versions":{"v2":"/api/v2/"},"oauth2":"/api/o/","custom_logo":"","custom_login_info":"","login_redirect_override":""}

but as soon as I try running it with the --resolve, I get:
ubuntu@awx-restore:~$ kubectl -n awx get ingress
NAME          CLASS     HOSTS                 ADDRESS    PORTS     AGE
awx-ingress   traefik   awx.clearsky.vision   <IP_ADDRESS>   80, 443   15m
ubuntu@awx-restore:~$ curl --resolve awx.clearsky.vision:80:<IP_ADDRESS> http://awx.clearsky.vision/api/
404 page not found
ubuntu@awx-restore:~$ curl -k --resolve awx.clearsky.vision:443:<IP_ADDRESS> https://awx.clearsky.vision/api/
404 page not found
ubuntu@awx-restore:~$ curl -kv --resolve awx.clearsky.vision:443:<IP_ADDRESS> https://awx.clearsky.vision/api/
* Added awx.clearsky.vision:443:<IP_ADDRESS> to DNS cache
* Hostname awx.clearsky.vision was found in DNS cache
*   Trying <IP_ADDRESS>:443...
* TCP_NODELAY set
* Connected to awx.clearsky.vision (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=awx.clearsky.vision
*  start date: Aug 31 07:03:07 2023 GMT
*  expire date: Nov 29 07:03:06 2023 GMT
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x5569fd45c8d0)
> GET /api/ HTTP/2
> Host: awx.clearsky.vision
> user-agent: curl/7.68.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
< HTTP/2 404
< content-type: text/plain; charset=utf-8
< x-content-type-options: nosniff
< content-length: 19
< date: Fri, 08 Sep 2023 09:00:45 GMT
<
404 page not found
* Connection #0 to host awx.clearsky.vision left intact

any ideas how to proceed? This is my first exposure to k*s in any shape or form, so I am not quite sure how to proceed with the investigation into why it fails to route it properly from the ingress.

@toutas
Thanks for making further investigation. Is there a conflict between the CIDR used by K3s and your environment-specific routing table?
Could you provide the output from following command? (If you don't want to paste logs from ip and iptables here, it's okay to send me by email)
kubectl -n awx describe pod <your awx-web pod>
kubectl -n awx describe ingress awx-ingress

sudo systemctl status firewalld
sudo ip addr
sudo ip route
sudo iptables -L

I believe this is not an issue that related to restoration, but simply internal routing issue for your K3s or traefik.
If additional investigation is available, you can try to check Traefik access logs (see tips in my comment above), and on the node that has this issue do a clean install instead of a restore to see if it works.

@kurokobo maybe you are on to the right track with the CIDR block. I am running the awx vm on azure where the vnet is defaulting to <IP_ADDRESS>/16. The only thing I modified is the awx.my.domian
kubectl -n awx describe pod awx-web:
Name:             awx-web-6447c576db-l677x
Namespace:        awx
Priority:         0
Service Account:  awx
Node:             awx-restore/<IP_ADDRESS>
Start Time:       Fri, 08 Sep 2023 11:57:30 +0000
Labels:           app.kubernetes.io/component=awx
                  app.kubernetes.io/managed-by=awx-operator
                  app.kubernetes.io/name=awx-web
                  app.kubernetes.io/operator-version=2.5.1
                  app.kubernetes.io/part-of=awx
                  app.kubernetes.io/version=22.7.0
                  pod-template-hash=6447c576db
Annotations:      checksum-configmaps-config: 9132252ebe19fcd96fb324508588003cfabef99f
                  checksum-secret-bundle_cacert: da39a3ee5e6b4b0d3255bfef95601890afd80709
                  checksum-secret-ldap_cacert: da39a3ee5e6b4b0d3255bfef95601890afd80709
                  checksum-secret-receptor_ca: 898ccf33a96ac820c1c7524bf7863a675f2c4e27
                  checksum-secret-receptor_work_signing: b198f665798d5be250703b5c9d65444bc1d6de4e
                  checksum-secret-route_tls: da39a3ee5e6b4b0d3255bfef95601890afd80709
                  checksum-secret-secret_key: e9491d79bddad9a8b72c563ac59bb549d508e73b
                  checksum-secrets-app_credentials: e88d82cb3481ff0126307d4804d598a3e9da99b0
                  checksum-storage-persistent: adc83b19e793491b1c6ea0fd8b46cd9f32e592fc
                  kubectl.kubernetes.io/default-container: awx-web
Status:           Running
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/awx-web-6447c576db
Init Containers:
  init:
    Container ID:  containerd://a287c57e8241fae280a8b0d25be2e074d009677acf0b0df4e26948e8af544f4a
    Image:         quay.io/ansible/awx-ee:latest
    Image ID:      quay.io/ansible/awx-ee@sha256:0bdbae1e87a89fbbca6308ea6d185410dae390fa5e1112ef9a82f5f1f292a39f
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
      -c

    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 08 Sep 2023 11:57:31 +0000
      Finished:     Fri, 08 Sep 2023 11:57:31 +0000
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-p429v (ro)
  init-projects:
    Container ID:  containerd://1586c6ee770be04a5f75aa1c082df4640e41fb844e00d24e2f715c8187881ad9
    Image:         quay.io/centos/centos:stream9
    Image ID:      quay.io/centos/centos@sha256:206e6ecdba86079d5acead9f7dbcfd1ebec5f11153a10fa81b043d2afdf96361
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
      -c
      chmod 775 /var/lib/awx/projects
      chgrp 1000 /var/lib/awx/projects

    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 08 Sep 2023 11:57:37 +0000
      Finished:     Fri, 08 Sep 2023 11:57:37 +0000
    Ready:          True
    Restart Count:  0
    Environment:
      MY_POD_NAME:  awx-web-6447c576db-l677x (v1:metadata.name)
    Mounts:
      /var/lib/awx/projects from awx-projects (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-p429v (ro)
Containers:
  redis:
    Container ID:  containerd://f8557f40c4dbb86b484fd18bdca2369a59b17dbdaff9429f54231a50cafb036a
    Image:         docker.io/redis:7
    Image ID:      docker.io/library/redis@sha256:f92a0be0ba8c085e6a5e2d2bea386365443485bcd67ced5ca8ddcdacdd4656d2
    Port:          <none>
    Host Port:     <none>
    Args:
      redis-server
      /etc/redis.conf
    State:          Running
      Started:      Fri, 08 Sep 2023 11:57:38 +0000
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:        50m
      memory:     64Mi
    Environment:  <none>
    Mounts:
      /data from awx-redis-data (rw)
      /etc/redis.conf from awx-redis-config (ro,path="redis.conf")
      /var/run/redis from awx-redis-socket (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-p429v (ro)
  awx-web:
    Container ID:  containerd://c0de4861042de115cbeaf8cf91c80e69eb6965dd865881cf93458bd2a1c889e8
    Image:         quay.io/ansible/awx:22.7.0
    Image ID:      quay.io/ansible/awx@sha256:835edca178ac1b4a77b906e4865bdd7451d95eaf4e382a5ee80aa8949f2e6b64
    Port:          8052/TCP
    Host Port:     0/TCP
    Args:
      /usr/bin/launch_awx_web.sh
    State:          Running
      Started:      Fri, 08 Sep 2023 11:57:39 +0000
    Ready:          True
    Restart Count:  0
    Environment:
      AWX_COMPONENT:           web
      SUPERVISOR_CONFIG_PATH:  /etc/supervisord_web.conf
      MY_POD_NAMESPACE:        awx (v1:metadata.namespace)
      MY_POD_IP:                (v1:status.podIP)
      UWSGI_MOUNT_PATH:        /
    Mounts:
      /etc/nginx/nginx.conf from awx-nginx-conf (ro,path="nginx.conf")
      /etc/receptor/tls/ca/mesh-CA.crt from awx-receptor-ca (ro,path="tls.crt")
      /etc/receptor/tls/ca/mesh-CA.key from awx-receptor-ca (ro,path="tls.key")
      /etc/receptor/work_public_key.pem from awx-receptor-work-signing (ro,path="work-public-key.pem")
      /etc/tower/SECRET_KEY from awx-secret-key (ro,path="SECRET_KEY")
      /etc/tower/conf.d/credentials.py from awx-application-credentials (ro,path="credentials.py")
      /etc/tower/conf.d/execution_environments.py from awx-application-credentials (ro,path="execution_environments.py")
      /etc/tower/conf.d/ldap.py from awx-application-credentials (ro,path="ldap.py")
      /etc/tower/settings.py from awx-settings (ro,path="settings.py")
      /etc/tower/uwsgi.ini from awx-uwsgi-config (ro,path="uwsgi.conf")
      /var/lib/awx/projects from awx-projects (rw)
      /var/run/awx-rsyslog from rsyslog-socket (rw)
      /var/run/redis from awx-redis-socket (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-p429v (ro)
  awx-rsyslog:
    Container ID:  containerd://0402a7dce10b7ed3b8d0dae36aee267dfc340f1be2ee297e6e17cadeb365ed01
    Image:         quay.io/ansible/awx:22.7.0
    Image ID:      quay.io/ansible/awx@sha256:835edca178ac1b4a77b906e4865bdd7451d95eaf4e382a5ee80aa8949f2e6b64
    Port:          <none>
    Host Port:     <none>
    Args:
      /usr/bin/launch_awx_rsyslog.sh
    State:          Running
      Started:      Fri, 08 Sep 2023 11:57:39 +0000
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:     100m
      memory:  128Mi
    Environment:
      SUPERVISOR_CONFIG_PATH:  /etc/supervisord_rsyslog.conf
    Mounts:
      /etc/tower/SECRET_KEY from awx-secret-key (ro,path="SECRET_KEY")
      /etc/tower/conf.d/credentials.py from awx-application-credentials (ro,path="credentials.py")
      /etc/tower/settings.py from awx-settings (ro,path="settings.py")
      /var/run/awx-rsyslog from rsyslog-socket (rw)
      /var/run/redis from awx-redis-socket (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-p429v (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  awx-receptor-ca:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  awx-receptor-ca
    Optional:    false
  awx-receptor-work-signing:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  awx-receptor-work-signing
    Optional:    false
  awx-application-credentials:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  awx-app-credentials
    Optional:    false
  awx-secret-key:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  awx-secret-key
    Optional:    false
  awx-settings:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      awx-awx-configmap
    Optional:  false
  awx-nginx-conf:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      awx-awx-configmap
    Optional:  false
  awx-redis-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      awx-awx-configmap
    Optional:  false
  awx-uwsgi-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      awx-awx-configmap
    Optional:  false
  awx-redis-socket:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  awx-redis-data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  rsyslog-socket:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  receptor-socket:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  awx-receptor-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      awx-awx-configmap
    Optional:  false
  awx-projects:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  awx-projects-claim
    ReadOnly:   false
  kube-api-access-p429v:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason     Age    From               Message
  ----    ------     ----   ----               -------
  Normal  Scheduled  4m27s  default-scheduler  Successfully assigned awx/awx-web-6447c576db-l677x to awx-restore
  Normal  Pulled     4m27s  kubelet            Container image "quay.io/ansible/awx-ee:latest" already present on machine
  Normal  Created    4m27s  kubelet            Created container init
  Normal  Started    4m27s  kubelet            Started container init
  Normal  Pulled     4m21s  kubelet            Container image "quay.io/centos/centos:stream9" already present on machine
  Normal  Created    4m21s  kubelet            Created container init-projects
  Normal  Started    4m21s  kubelet            Started container init-projects
  Normal  Pulled     4m20s  kubelet            Container image "docker.io/redis:7" already present on machine
  Normal  Created    4m20s  kubelet            Created container redis
  Normal  Started    4m20s  kubelet            Started container redis
  Normal  Pulled     4m20s  kubelet            Container image "quay.io/ansible/awx:22.7.0" already present on machine
  Normal  Created    4m19s  kubelet            Created container awx-web
  Normal  Started    4m19s  kubelet            Started container awx-web
  Normal  Pulled     4m19s  kubelet            Container image "quay.io/ansible/awx:22.7.0" already present on machine
  Normal  Created    4m19s  kubelet            Created container awx-rsyslog
  Normal  Started    4m19s  kubelet            Started container awx-rsyslog

kubectl -n awx describe ingress awx-ingress
Name:             awx-ingress
Labels:           app.kubernetes.io/component=awx
                  app.kubernetes.io/managed-by=awx-operator
                  app.kubernetes.io/operator-version=2.5.1
                  app.kubernetes.io/part-of=awx
Namespace:        awx
Address:          <IP_ADDRESS>
Ingress Class:    traefik
Default backend:  <default>
TLS:
  awx-secret-tls terminates awx.my.domain
Rules:
  Host                 Path  Backends
  ----                 ----  --------
  awx.my.domain
                       /   awx-service:80 (<IP_ADDRESS>:8052)
Annotations:           cert-manager.io/issuer: awx-issuer
                       traefik.ingress.kubernetes.io/router.middlewares: default-redirect@kubernetescrd
Events:
  Type    Reason             Age    From                       Message
  ----    ------             ----   ----                       -------
  Normal  CreateCertificate  7m58s  cert-manager-ingress-shim  Successfully created Certificate "awx-secret-tls"

sudo systemctl status firewalld
Unit firewalld.service could not be found.
sudo ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0d:3a:4a:80:9a brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::20d:3aff:fe4a:809a/64 scope link
       valid_lft forever preferred_lft forever
3: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default
    link/ether 2a:3e:1f:08:48:63 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/32 scope global flannel.1
       valid_lft forever preferred_lft forever
    inet6 fe80::283e:1fff:fe08:4863/64 scope link
       valid_lft forever preferred_lft forever
4: cni0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000
    link/ether 96:46:4c:c2:73:cf brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global cni0
       valid_lft forever preferred_lft forever
    inet6 fe80::9446:4cff:fec2:73cf/64 scope link
       valid_lft forever preferred_lft forever
7: vethea7ddda8@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether 62:c3:5b:28:5d:4c brd ff:ff:ff:ff:ff:ff link-netns cni-ce053c7e-c54f-2eb5-67dd-918afadc51c1
    inet6 fe80::60c3:5bff:fe28:5d4c/64 scope link
       valid_lft forever preferred_lft forever
8: vetha1c5d1a4@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether 7a:97:61:6d:20:3c brd ff:ff:ff:ff:ff:ff link-netns cni-87a55beb-b556-d152-760b-49c3f46ff300
    inet6 fe80::7897:61ff:fe6d:203c/64 scope link
       valid_lft forever preferred_lft forever
9: veth8b9b2137@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether 16:0a:61:df:6e:49 brd ff:ff:ff:ff:ff:ff link-netns cni-c5def7c6-3607-5287-7745-eb8a55b277cd
    inet6 fe80::140a:61ff:fedf:6e49/64 scope link
       valid_lft forever preferred_lft forever
10: vethd1ededd0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether 96:bb:70:d3:96:a3 brd ff:ff:ff:ff:ff:ff link-netns cni-a2119109-2cec-589b-4886-1c2c55b51a2b
    inet6 fe80::94bb:70ff:fed3:96a3/64 scope link
       valid_lft forever preferred_lft forever
11: vethc1df5acc@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether 1a:54:4e:63:2e:80 brd ff:ff:ff:ff:ff:ff link-netns cni-fac1b267-d7ec-d418-4d53-8fc9e2a1cf0a
    inet6 fe80::1854:4eff:fe63:2e80/64 scope link
       valid_lft forever preferred_lft forever
12: veth510c6dc2@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether f2:90:ed:be:46:1b brd ff:ff:ff:ff:ff:ff link-netns cni-dc48ac74-c01c-9740-3f0a-a6828a03a7aa
    inet6 fe80::f090:edff:febe:461b/64 scope link
       valid_lft forever preferred_lft forever
13: vethb003380b@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether 8a:a3:53:b1:31:8a brd ff:ff:ff:ff:ff:ff link-netns cni-f3ddf1f5-b3cc-4c2b-d97e-bb44f212428b
    inet6 fe80::88a3:53ff:feb1:318a/64 scope link
       valid_lft forever preferred_lft forever
14: vethd3851ac3@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether 16:ce:19:ca:52:d2 brd ff:ff:ff:ff:ff:ff link-netns cni-c6b27f9b-c67f-f6cf-0d44-acb4ad1fdd91
    inet6 fe80::14ce:19ff:feca:52d2/64 scope link
       valid_lft forever preferred_lft forever
15: vethd9fc0b15@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether d6:ba:a4:09:db:16 brd ff:ff:ff:ff:ff:ff link-netns cni-7cd774df-2c06-8293-8338-893443310d1e
    inet6 fe80::d4ba:a4ff:fe09:db16/64 scope link
       valid_lft forever preferred_lft forever
17: veth7596542e@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether b2:65:d3:0b:e5:06 brd ff:ff:ff:ff:ff:ff link-netns cni-e553ee7f-61f6-d2c5-e227-cc5b47daeb47
    inet6 fe80::b065:d3ff:fe0b:e506/64 scope link
       valid_lft forever preferred_lft forever
18: veth2e3e1ea2@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether 5e:d6:58:25:a0:8b brd ff:ff:ff:ff:ff:ff link-netns cni-0a49cfa2-23f6-31eb-2296-5f2bbdaa867d
    inet6 fe80::5cd6:58ff:fe25:a08b/64 scope link
       valid_lft forever preferred_lft forever
19: veth03e077a7@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
    link/ether 06:16:bb:29:bc:75 brd ff:ff:ff:ff:ff:ff link-netns cni-59a6ae5a-a8c7-eee5-0e7f-636242acec6e
    inet6 fe80::416:bbff:fe29:bc75/64 scope link
       valid_lft forever preferred_lft forever

sudo ip route
default via <IP_ADDRESS> dev eth0 proto dhcp src <IP_ADDRESS> metric 100
<IP_ADDRESS>/24 dev eth0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev cni0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS> via <IP_ADDRESS> dev eth0 proto dhcp src <IP_ADDRESS> metric 100
<IP_ADDRESS> via <IP_ADDRESS> dev eth0 proto dhcp src <IP_ADDRESS> metric 100

sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-ROUTER-INPUT  all  --  anywhere             anywhere             /* kube-router netpol - 4IA2OSFRMVNDXBVV */
KUBE-PROXY-FIREWALL  all  --  anywhere             anywhere             ctstate NEW /* kubernetes load balancer firewall */
KUBE-NODEPORTS  all  --  anywhere             anywhere             /* kubernetes health check service ports */
KUBE-EXTERNAL-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes externally-visible service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             /* KUBE-ROUTER rule to explicitly ACCEPT traffic that comply to network policies */ mark match 0x20000/0x20000

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
KUBE-ROUTER-FORWARD  all  --  anywhere             anywhere             /* kube-router netpol - TEMCG2JMHZYE7H7T */
KUBE-PROXY-FIREWALL  all  --  anywhere             anywhere             ctstate NEW /* kubernetes load balancer firewall */
KUBE-FORWARD  all  --  anywhere             anywhere             /* kubernetes forwarding rules */
KUBE-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes service portals */
KUBE-EXTERNAL-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes externally-visible service portals */
ACCEPT     all  --  anywhere             anywhere             /* KUBE-ROUTER rule to explicitly ACCEPT traffic that comply to network policies */ mark match 0x20000/0x20000
FLANNEL-FWD  all  --  anywhere             anywhere             /* flanneld forward */

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-ROUTER-OUTPUT  all  --  anywhere             anywhere             /* kube-router netpol - VEAAIY32XVBHCSCY */
KUBE-PROXY-FIREWALL  all  --  anywhere             anywhere             ctstate NEW /* kubernetes load balancer firewall */
KUBE-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             /* KUBE-ROUTER rule to explicitly ACCEPT traffic that comply to network policies */ mark match 0x20000/0x20000

Chain FLANNEL-FWD (1 references)
target     prot opt source               destination
ACCEPT     all  --  awx-restore/16       anywhere             /* flanneld forward */
ACCEPT     all  --  anywhere             awx-restore/16       /* flanneld forward */

Chain KUBE-EXTERNAL-SERVICES (2 references)
target     prot opt source               destination

Chain KUBE-FIREWALL (2 references)
target     prot opt source               destination
DROP       all  -- !localhost/8          localhost/8          /* block incoming localnet connections */ ! ctstate RELATED,ESTABLISHED,DNAT

Chain KUBE-FORWARD (1 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere             ctstate INVALID
ACCEPT     all  --  anywhere             anywhere             /* kubernetes forwarding rules */ mark match 0x4000/0x4000
ACCEPT     all  --  anywhere             anywhere             /* kubernetes forwarding conntrack rule */ ctstate RELATED,ESTABLISHED

Chain KUBE-KUBELET-CANARY (0 references)
target     prot opt source               destination

Chain KUBE-NODEPORTS (1 references)
target     prot opt source               destination

Chain KUBE-NWPLCY-DEFAULT (24 references)
target     prot opt source               destination
MARK       all  --  anywhere             anywhere             /* rule to mark traffic matching a network policy */ MARK or 0x10000

Chain KUBE-POD-FW-6PGQHSKCWC2EK3WX (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>            /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>            anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>            /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:metrics-server-648b5df564-rlpkk namespace: kube-system */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:metrics-server-648b5df564-rlpkk namespace: kube-system */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-C2J3BGP5HSZ3SH2J (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>           /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>           anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>           /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:awx-postgres-13-0 namespace: awx */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:awx-postgres-13-0 namespace: awx */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-M7EDKTG7ROVF6NFU (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>            /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>            anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>            /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:cert-manager-d6cd78457-km2fn namespace: cert-manager */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:cert-manager-d6cd78457-km2fn namespace: cert-manager */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-MKCSP54VAAC3UKGU (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>            /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>            anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>            /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:cert-manager-webhook-56ffdd7c44-bjnxf namespace: cert-manager */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:cert-manager-webhook-56ffdd7c44-bjnxf namespace: cert-manager */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-NIOCHCVW2YX5KCPN (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>            /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>            anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>            /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:coredns-77ccd57875-5sqdc namespace: kube-system */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:coredns-77ccd57875-5sqdc namespace: kube-system */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-O4GGHLRNNAA4D4ZA (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>           /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>           anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>           /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:traefik-64f55bb67d-dtqph namespace: kube-system */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:traefik-64f55bb67d-dtqph namespace: kube-system */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-R6RPYFXXLXLNFXPQ (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>           /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>           anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>           /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:awx-task-758f8f959b-clbzt namespace: awx */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:awx-task-758f8f959b-clbzt namespace: awx */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-TLCEQ2DXSA3DQ2ER (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>            /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>            anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>            /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:awx-operator-controller-manager-564f8dc4fc-mmq84 namespace: awx */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:awx-operator-controller-manager-564f8dc4fc-mmq84 namespace: awx */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-TVCZC4KJET7PEBGW (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>           /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>           anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>           /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:awx-web-6447c576db-l677x namespace: awx */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:awx-web-6447c576db-l677x namespace: awx */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-WQR35CSFBMLBEFIT (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>           /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>           anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>           /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:svclb-traefik-27285fa9-wvj9s namespace: kube-system */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:svclb-traefik-27285fa9-wvj9s namespace: kube-system */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-Y4VHKLT7K7QPP35E (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>           /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>           anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>           /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:cert-manager-cainjector-84cdd9dd4b-9bwh7 namespace: cert-manager */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:cert-manager-cainjector-84cdd9dd4b-9bwh7 namespace: cert-manager */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-POD-FW-ZPWN2AUVOI7YZJV3 (7 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* rule for stateful firewall for pod */ ctstate RELATED,ESTABLISHED
DROP       all  --  anywhere             anywhere             /* rule to drop invalid state for pod */ ctstate INVALID
ACCEPT     all  --  anywhere             <IP_ADDRESS>            /* rule to permit the traffic traffic to pods when source is the pod's local node */ ADDRTYPE match src-type LOCAL
KUBE-NWPLCY-DEFAULT  all  --  <IP_ADDRESS>            anywhere             /* run through default egress network policy chain */
KUBE-NWPLCY-DEFAULT  all  --  anywhere             <IP_ADDRESS>            /* run through default ingress network policy chain */
NFLOG      all  --  anywhere             anywhere             /* rule to log dropped traffic POD name:local-path-provisioner-957fdf8bc-rvqqs namespace: kube-system */ mark match ! 0x10000/0x10000 limit: avg 10/min burst 10 nflog-group 100
REJECT     all  --  anywhere             anywhere             /* rule to REJECT traffic destined for POD name:local-path-provisioner-957fdf8bc-rvqqs namespace: kube-system */ mark match ! 0x10000/0x10000 reject-with icmp-port-unreachable
MARK       all  --  anywhere             anywhere             MARK and 0xfffeffff
MARK       all  --  anywhere             anywhere             /* set mark to ACCEPT traffic that comply to network policies */ MARK or 0x20000

Chain KUBE-PROXY-CANARY (0 references)
target     prot opt source               destination

Chain KUBE-PROXY-FIREWALL (3 references)
target     prot opt source               destination

Chain KUBE-ROUTER-FORWARD (1 references)
target     prot opt source               destination
KUBE-POD-FW-Y4VHKLT7K7QPP35E  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:cert-manager-cainjector-84cdd9dd4b-9bwh7 namespace: cert-manager to chain KUBE-POD-FW-Y4VHKLT7K7QPP35E */
KUBE-POD-FW-Y4VHKLT7K7QPP35E  all  --  anywhere             <IP_ADDRESS>           PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:cert-manager-cainjector-84cdd9dd4b-9bwh7 namespace: cert-manager to chain KUBE-POD-FW-Y4VHKLT7K7QPP35E */
KUBE-POD-FW-Y4VHKLT7K7QPP35E  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:cert-manager-cainjector-84cdd9dd4b-9bwh7 namespace: cert-manager to chain KUBE-POD-FW-Y4VHKLT7K7QPP35E */
KUBE-POD-FW-Y4VHKLT7K7QPP35E  all  --  <IP_ADDRESS>           anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:cert-manager-cainjector-84cdd9dd4b-9bwh7 namespace: cert-manager to chain KUBE-POD-FW-Y4VHKLT7K7QPP35E */
KUBE-POD-FW-M7EDKTG7ROVF6NFU  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:cert-manager-d6cd78457-km2fn namespace: cert-manager to chain KUBE-POD-FW-M7EDKTG7ROVF6NFU */
KUBE-POD-FW-M7EDKTG7ROVF6NFU  all  --  anywhere             <IP_ADDRESS>            PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:cert-manager-d6cd78457-km2fn namespace: cert-manager to chain KUBE-POD-FW-M7EDKTG7ROVF6NFU */
KUBE-POD-FW-M7EDKTG7ROVF6NFU  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:cert-manager-d6cd78457-km2fn namespace: cert-manager to chain KUBE-POD-FW-M7EDKTG7ROVF6NFU */
KUBE-POD-FW-M7EDKTG7ROVF6NFU  all  --  <IP_ADDRESS>            anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:cert-manager-d6cd78457-km2fn namespace: cert-manager to chain KUBE-POD-FW-M7EDKTG7ROVF6NFU */
KUBE-POD-FW-O4GGHLRNNAA4D4ZA  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:traefik-64f55bb67d-dtqph namespace: kube-system to chain KUBE-POD-FW-O4GGHLRNNAA4D4ZA */
KUBE-POD-FW-O4GGHLRNNAA4D4ZA  all  --  anywhere             <IP_ADDRESS>           PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:traefik-64f55bb67d-dtqph namespace: kube-system to chain KUBE-POD-FW-O4GGHLRNNAA4D4ZA */
KUBE-POD-FW-O4GGHLRNNAA4D4ZA  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:traefik-64f55bb67d-dtqph namespace: kube-system to chain KUBE-POD-FW-O4GGHLRNNAA4D4ZA */
KUBE-POD-FW-O4GGHLRNNAA4D4ZA  all  --  <IP_ADDRESS>           anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:traefik-64f55bb67d-dtqph namespace: kube-system to chain KUBE-POD-FW-O4GGHLRNNAA4D4ZA */
KUBE-POD-FW-ZPWN2AUVOI7YZJV3  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:local-path-provisioner-957fdf8bc-rvqqs namespace: kube-system to chain KUBE-POD-FW-ZPWN2AUVOI7YZJV3 */
KUBE-POD-FW-ZPWN2AUVOI7YZJV3  all  --  anywhere             <IP_ADDRESS>            PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:local-path-provisioner-957fdf8bc-rvqqs namespace: kube-system to chain KUBE-POD-FW-ZPWN2AUVOI7YZJV3 */
KUBE-POD-FW-ZPWN2AUVOI7YZJV3  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:local-path-provisioner-957fdf8bc-rvqqs namespace: kube-system to chain KUBE-POD-FW-ZPWN2AUVOI7YZJV3 */
KUBE-POD-FW-ZPWN2AUVOI7YZJV3  all  --  <IP_ADDRESS>            anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:local-path-provisioner-957fdf8bc-rvqqs namespace: kube-system to chain KUBE-POD-FW-ZPWN2AUVOI7YZJV3 */
KUBE-POD-FW-NIOCHCVW2YX5KCPN  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:coredns-77ccd57875-5sqdc namespace: kube-system to chain KUBE-POD-FW-NIOCHCVW2YX5KCPN */
KUBE-POD-FW-NIOCHCVW2YX5KCPN  all  --  anywhere             <IP_ADDRESS>            PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:coredns-77ccd57875-5sqdc namespace: kube-system to chain KUBE-POD-FW-NIOCHCVW2YX5KCPN */
KUBE-POD-FW-NIOCHCVW2YX5KCPN  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:coredns-77ccd57875-5sqdc namespace: kube-system to chain KUBE-POD-FW-NIOCHCVW2YX5KCPN */
KUBE-POD-FW-NIOCHCVW2YX5KCPN  all  --  <IP_ADDRESS>            anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:coredns-77ccd57875-5sqdc namespace: kube-system to chain KUBE-POD-FW-NIOCHCVW2YX5KCPN */
KUBE-POD-FW-R6RPYFXXLXLNFXPQ  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:awx-task-758f8f959b-clbzt namespace: awx to chain KUBE-POD-FW-R6RPYFXXLXLNFXPQ */
KUBE-POD-FW-R6RPYFXXLXLNFXPQ  all  --  anywhere             <IP_ADDRESS>           PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:awx-task-758f8f959b-clbzt namespace: awx to chain KUBE-POD-FW-R6RPYFXXLXLNFXPQ */
KUBE-POD-FW-R6RPYFXXLXLNFXPQ  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:awx-task-758f8f959b-clbzt namespace: awx to chain KUBE-POD-FW-R6RPYFXXLXLNFXPQ */
KUBE-POD-FW-R6RPYFXXLXLNFXPQ  all  --  <IP_ADDRESS>           anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:awx-task-758f8f959b-clbzt namespace: awx to chain KUBE-POD-FW-R6RPYFXXLXLNFXPQ */
KUBE-POD-FW-MKCSP54VAAC3UKGU  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:cert-manager-webhook-56ffdd7c44-bjnxf namespace: cert-manager to chain KUBE-POD-FW-MKCSP54VAAC3UKGU */
KUBE-POD-FW-MKCSP54VAAC3UKGU  all  --  anywhere             <IP_ADDRESS>            PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:cert-manager-webhook-56ffdd7c44-bjnxf namespace: cert-manager to chain KUBE-POD-FW-MKCSP54VAAC3UKGU */
KUBE-POD-FW-MKCSP54VAAC3UKGU  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:cert-manager-webhook-56ffdd7c44-bjnxf namespace: cert-manager to chain KUBE-POD-FW-MKCSP54VAAC3UKGU */
KUBE-POD-FW-MKCSP54VAAC3UKGU  all  --  <IP_ADDRESS>            anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:cert-manager-webhook-56ffdd7c44-bjnxf namespace: cert-manager to chain KUBE-POD-FW-MKCSP54VAAC3UKGU */
KUBE-POD-FW-TLCEQ2DXSA3DQ2ER  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:awx-operator-controller-manager-564f8dc4fc-mmq84 namespace: awx to chain KUBE-POD-FW-TLCEQ2DXSA3DQ2ER */
KUBE-POD-FW-TLCEQ2DXSA3DQ2ER  all  --  anywhere             <IP_ADDRESS>            PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:awx-operator-controller-manager-564f8dc4fc-mmq84 namespace: awx to chain KUBE-POD-FW-TLCEQ2DXSA3DQ2ER */
KUBE-POD-FW-TLCEQ2DXSA3DQ2ER  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:awx-operator-controller-manager-564f8dc4fc-mmq84 namespace: awx to chain KUBE-POD-FW-TLCEQ2DXSA3DQ2ER */
KUBE-POD-FW-TLCEQ2DXSA3DQ2ER  all  --  <IP_ADDRESS>            anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:awx-operator-controller-manager-564f8dc4fc-mmq84 namespace: awx to chain KUBE-POD-FW-TLCEQ2DXSA3DQ2ER */
KUBE-POD-FW-6PGQHSKCWC2EK3WX  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:metrics-server-648b5df564-rlpkk namespace: kube-system to chain KUBE-POD-FW-6PGQHSKCWC2EK3WX */
KUBE-POD-FW-6PGQHSKCWC2EK3WX  all  --  anywhere             <IP_ADDRESS>            PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:metrics-server-648b5df564-rlpkk namespace: kube-system to chain KUBE-POD-FW-6PGQHSKCWC2EK3WX */
KUBE-POD-FW-6PGQHSKCWC2EK3WX  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:metrics-server-648b5df564-rlpkk namespace: kube-system to chain KUBE-POD-FW-6PGQHSKCWC2EK3WX */
KUBE-POD-FW-6PGQHSKCWC2EK3WX  all  --  <IP_ADDRESS>            anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:metrics-server-648b5df564-rlpkk namespace: kube-system to chain KUBE-POD-FW-6PGQHSKCWC2EK3WX */
KUBE-POD-FW-WQR35CSFBMLBEFIT  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:svclb-traefik-27285fa9-wvj9s namespace: kube-system to chain KUBE-POD-FW-WQR35CSFBMLBEFIT */
KUBE-POD-FW-WQR35CSFBMLBEFIT  all  --  anywhere             <IP_ADDRESS>           PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:svclb-traefik-27285fa9-wvj9s namespace: kube-system to chain KUBE-POD-FW-WQR35CSFBMLBEFIT */
KUBE-POD-FW-WQR35CSFBMLBEFIT  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:svclb-traefik-27285fa9-wvj9s namespace: kube-system to chain KUBE-POD-FW-WQR35CSFBMLBEFIT */
KUBE-POD-FW-WQR35CSFBMLBEFIT  all  --  <IP_ADDRESS>           anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:svclb-traefik-27285fa9-wvj9s namespace: kube-system to chain KUBE-POD-FW-WQR35CSFBMLBEFIT */
KUBE-POD-FW-C2J3BGP5HSZ3SH2J  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:awx-postgres-13-0 namespace: awx to chain KUBE-POD-FW-C2J3BGP5HSZ3SH2J */
KUBE-POD-FW-C2J3BGP5HSZ3SH2J  all  --  anywhere             <IP_ADDRESS>           PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:awx-postgres-13-0 namespace: awx to chain KUBE-POD-FW-C2J3BGP5HSZ3SH2J */
KUBE-POD-FW-C2J3BGP5HSZ3SH2J  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:awx-postgres-13-0 namespace: awx to chain KUBE-POD-FW-C2J3BGP5HSZ3SH2J */
KUBE-POD-FW-C2J3BGP5HSZ3SH2J  all  --  <IP_ADDRESS>           anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:awx-postgres-13-0 namespace: awx to chain KUBE-POD-FW-C2J3BGP5HSZ3SH2J */
KUBE-POD-FW-TVCZC4KJET7PEBGW  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:awx-web-6447c576db-l677x namespace: awx to chain KUBE-POD-FW-TVCZC4KJET7PEBGW */
KUBE-POD-FW-TVCZC4KJET7PEBGW  all  --  anywhere             <IP_ADDRESS>           PHYSDEV match --physdev-is-bridged /* rule to jump traffic destined to POD name:awx-web-6447c576db-l677x namespace: awx to chain KUBE-POD-FW-TVCZC4KJET7PEBGW */
KUBE-POD-FW-TVCZC4KJET7PEBGW  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:awx-web-6447c576db-l677x namespace: awx to chain KUBE-POD-FW-TVCZC4KJET7PEBGW */
KUBE-POD-FW-TVCZC4KJET7PEBGW  all  --  <IP_ADDRESS>           anywhere             PHYSDEV match --physdev-is-bridged /* rule to jump traffic from POD name:awx-web-6447c576db-l677x namespace: awx to chain KUBE-POD-FW-TVCZC4KJET7PEBGW */

Chain KUBE-ROUTER-INPUT (1 references)
target     prot opt source               destination
RETURN     all  --  anywhere             <IP_ADDRESS>/16         /* allow traffic to primary/secondary cluster IP range - EKROEGTNIJ3AP3LC */
RETURN     tcp  --  anywhere             anywhere             /* allow LOCAL TCP traffic to node ports - LR7XO7NXDBGQJD2M */ ADDRTYPE match dst-type LOCAL multiport dports 30000:32767
RETURN     udp  --  anywhere             anywhere             /* allow LOCAL UDP traffic to node ports - 76UCBPIZNGJNWNUZ */ ADDRTYPE match dst-type LOCAL multiport dports 30000:32767
KUBE-POD-FW-Y4VHKLT7K7QPP35E  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:cert-manager-cainjector-84cdd9dd4b-9bwh7 namespace: cert-manager to chain KUBE-POD-FW-Y4VHKLT7K7QPP35E */
KUBE-POD-FW-M7EDKTG7ROVF6NFU  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:cert-manager-d6cd78457-km2fn namespace: cert-manager to chain KUBE-POD-FW-M7EDKTG7ROVF6NFU */
KUBE-POD-FW-O4GGHLRNNAA4D4ZA  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:traefik-64f55bb67d-dtqph namespace: kube-system to chain KUBE-POD-FW-O4GGHLRNNAA4D4ZA */
KUBE-POD-FW-ZPWN2AUVOI7YZJV3  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:local-path-provisioner-957fdf8bc-rvqqs namespace: kube-system to chain KUBE-POD-FW-ZPWN2AUVOI7YZJV3 */
KUBE-POD-FW-NIOCHCVW2YX5KCPN  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:coredns-77ccd57875-5sqdc namespace: kube-system to chain KUBE-POD-FW-NIOCHCVW2YX5KCPN */
KUBE-POD-FW-R6RPYFXXLXLNFXPQ  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:awx-task-758f8f959b-clbzt namespace: awx to chain KUBE-POD-FW-R6RPYFXXLXLNFXPQ */
KUBE-POD-FW-MKCSP54VAAC3UKGU  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:cert-manager-webhook-56ffdd7c44-bjnxf namespace: cert-manager to chain KUBE-POD-FW-MKCSP54VAAC3UKGU */
KUBE-POD-FW-TLCEQ2DXSA3DQ2ER  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:awx-operator-controller-manager-564f8dc4fc-mmq84 namespace: awx to chain KUBE-POD-FW-TLCEQ2DXSA3DQ2ER */
KUBE-POD-FW-6PGQHSKCWC2EK3WX  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:metrics-server-648b5df564-rlpkk namespace: kube-system to chain KUBE-POD-FW-6PGQHSKCWC2EK3WX */
KUBE-POD-FW-WQR35CSFBMLBEFIT  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:svclb-traefik-27285fa9-wvj9s namespace: kube-system to chain KUBE-POD-FW-WQR35CSFBMLBEFIT */
KUBE-POD-FW-C2J3BGP5HSZ3SH2J  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:awx-postgres-13-0 namespace: awx to chain KUBE-POD-FW-C2J3BGP5HSZ3SH2J */
KUBE-POD-FW-TVCZC4KJET7PEBGW  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:awx-web-6447c576db-l677x namespace: awx to chain KUBE-POD-FW-TVCZC4KJET7PEBGW */

Chain KUBE-ROUTER-OUTPUT (1 references)
target     prot opt source               destination
KUBE-POD-FW-Y4VHKLT7K7QPP35E  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:cert-manager-cainjector-84cdd9dd4b-9bwh7 namespace: cert-manager to chain KUBE-POD-FW-Y4VHKLT7K7QPP35E */
KUBE-POD-FW-Y4VHKLT7K7QPP35E  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:cert-manager-cainjector-84cdd9dd4b-9bwh7 namespace: cert-manager to chain KUBE-POD-FW-Y4VHKLT7K7QPP35E */
KUBE-POD-FW-M7EDKTG7ROVF6NFU  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:cert-manager-d6cd78457-km2fn namespace: cert-manager to chain KUBE-POD-FW-M7EDKTG7ROVF6NFU */
KUBE-POD-FW-M7EDKTG7ROVF6NFU  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:cert-manager-d6cd78457-km2fn namespace: cert-manager to chain KUBE-POD-FW-M7EDKTG7ROVF6NFU */
KUBE-POD-FW-O4GGHLRNNAA4D4ZA  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:traefik-64f55bb67d-dtqph namespace: kube-system to chain KUBE-POD-FW-O4GGHLRNNAA4D4ZA */
KUBE-POD-FW-O4GGHLRNNAA4D4ZA  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:traefik-64f55bb67d-dtqph namespace: kube-system to chain KUBE-POD-FW-O4GGHLRNNAA4D4ZA */
KUBE-POD-FW-ZPWN2AUVOI7YZJV3  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:local-path-provisioner-957fdf8bc-rvqqs namespace: kube-system to chain KUBE-POD-FW-ZPWN2AUVOI7YZJV3 */
KUBE-POD-FW-ZPWN2AUVOI7YZJV3  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:local-path-provisioner-957fdf8bc-rvqqs namespace: kube-system to chain KUBE-POD-FW-ZPWN2AUVOI7YZJV3 */
KUBE-POD-FW-NIOCHCVW2YX5KCPN  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:coredns-77ccd57875-5sqdc namespace: kube-system to chain KUBE-POD-FW-NIOCHCVW2YX5KCPN */
KUBE-POD-FW-NIOCHCVW2YX5KCPN  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:coredns-77ccd57875-5sqdc namespace: kube-system to chain KUBE-POD-FW-NIOCHCVW2YX5KCPN */
KUBE-POD-FW-R6RPYFXXLXLNFXPQ  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:awx-task-758f8f959b-clbzt namespace: awx to chain KUBE-POD-FW-R6RPYFXXLXLNFXPQ */
KUBE-POD-FW-R6RPYFXXLXLNFXPQ  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:awx-task-758f8f959b-clbzt namespace: awx to chain KUBE-POD-FW-R6RPYFXXLXLNFXPQ */
KUBE-POD-FW-MKCSP54VAAC3UKGU  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:cert-manager-webhook-56ffdd7c44-bjnxf namespace: cert-manager to chain KUBE-POD-FW-MKCSP54VAAC3UKGU */
KUBE-POD-FW-MKCSP54VAAC3UKGU  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:cert-manager-webhook-56ffdd7c44-bjnxf namespace: cert-manager to chain KUBE-POD-FW-MKCSP54VAAC3UKGU */
KUBE-POD-FW-TLCEQ2DXSA3DQ2ER  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:awx-operator-controller-manager-564f8dc4fc-mmq84 namespace: awx to chain KUBE-POD-FW-TLCEQ2DXSA3DQ2ER */
KUBE-POD-FW-TLCEQ2DXSA3DQ2ER  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:awx-operator-controller-manager-564f8dc4fc-mmq84 namespace: awx to chain KUBE-POD-FW-TLCEQ2DXSA3DQ2ER */
KUBE-POD-FW-6PGQHSKCWC2EK3WX  all  --  anywhere             <IP_ADDRESS>            /* rule to jump traffic destined to POD name:metrics-server-648b5df564-rlpkk namespace: kube-system to chain KUBE-POD-FW-6PGQHSKCWC2EK3WX */
KUBE-POD-FW-6PGQHSKCWC2EK3WX  all  --  <IP_ADDRESS>            anywhere             /* rule to jump traffic from POD name:metrics-server-648b5df564-rlpkk namespace: kube-system to chain KUBE-POD-FW-6PGQHSKCWC2EK3WX */
KUBE-POD-FW-WQR35CSFBMLBEFIT  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:svclb-traefik-27285fa9-wvj9s namespace: kube-system to chain KUBE-POD-FW-WQR35CSFBMLBEFIT */
KUBE-POD-FW-WQR35CSFBMLBEFIT  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:svclb-traefik-27285fa9-wvj9s namespace: kube-system to chain KUBE-POD-FW-WQR35CSFBMLBEFIT */
KUBE-POD-FW-C2J3BGP5HSZ3SH2J  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:awx-postgres-13-0 namespace: awx to chain KUBE-POD-FW-C2J3BGP5HSZ3SH2J */
KUBE-POD-FW-C2J3BGP5HSZ3SH2J  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:awx-postgres-13-0 namespace: awx to chain KUBE-POD-FW-C2J3BGP5HSZ3SH2J */
KUBE-POD-FW-TVCZC4KJET7PEBGW  all  --  anywhere             <IP_ADDRESS>           /* rule to jump traffic destined to POD name:awx-web-6447c576db-l677x namespace: awx to chain KUBE-POD-FW-TVCZC4KJET7PEBGW */
KUBE-POD-FW-TVCZC4KJET7PEBGW  all  --  <IP_ADDRESS>           anywhere             /* rule to jump traffic from POD name:awx-web-6447c576db-l677x namespace: awx to chain KUBE-POD-FW-TVCZC4KJET7PEBGW */

Chain KUBE-SERVICES (2 references)
target     prot opt source               destination

the vnet that my restore test is being created in has my current AWX VM as well, so will attempt to create it in a separate vnet and see if there's a change.

@kurokobo I have now also tested with the vm being in a separate vnet completely alone, using 172.16/12, and it still fails the same way.

@kurokobo I now investigated the traefik logs, and I see this:

looks like there is some redirect middleware that is bonked out?

if it's not required for you, you should remove ingress_annotations from your
Ah, sorry, ingress_annotations is required to enable cert manager, so remove traefik.ingress.kubernetes.io/router.middlewares from your ingress_annotations.

if it's not required for you, you should remove ingress_annotations from your spec

Ah, sorry, ingress_annotations is required to enable cert manager, so if the redirection is not required for you, remove traefik.ingress.kubernetes.io/router.middlewares from your ingress_annotations.

I tested removing it from the awx.yaml and doing kubectl apply -k base on the restored VM, but it changed nothing. Any ideas?

Good to hear that, nice work!

Maybe put that part in the restore documentation, or alongside the https redirection?

Indeed, it should be noted somewhere that we should make our own backups and restores for additional resources unless they were made in Operator. I will consider it. Thanks for the idea.
Closing this issue, have fun!


Have you any plans for add App Engine?

I would like use automatic deploy via cloud functions. But now is not very ussefull because this client doesn't have API for App Engine.
Have you any plans for add App Engine?

Hi @adostal,
Right now, we do not have any short-term plans to add the App Engine API, although this is something it would be interesting to do in the future.
Thank you for asking, and we will keep this request in mind!


sql: cluster-wide settings

RFC: https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/settings_table.md
PRs:

https://github.com/cockroachdb/cockroach/pull/15307
opt-out stats reporting
sql: migrate the tracing flags to cluster settings
sql: support SHOW ALL CLUSTER SETTINGS
https://github.com/cockroachdb/cockroach/pull/14913
https://github.com/cockroachdb/cockroach/pull/14646
https://github.com/cockroachdb/cockroach/pull/14688
https://github.com/cockroachdb/cockroach/pull/14691

Documented in https://github.com/cockroachdb/docs/pull/1336. Opening a new issue to follow-up with more detailed explanations/guidance for each setting.


Nodes going window xp error on Krom

Above happen only on krom, works fine on html5
Kha and krom taken from Kode

Sorry but I am unable to reproduce, I tested with latest Kha + Krom from Kode using the provided Nodes example on Windows 10.

I guess, it is again MacOS + Metal bug. Will have to switch back to older version of krom(lastest have error when trying to use opengl) and use opengl

Will do my best to send more Metal pull-requests into Kinc, so we can abandon opengl. Robert already started updating the krafix shader compiler, once that is finished it should  hopefully handle all of the armory shaders so I can focus more on Metal. 🙂


Cannot save edits in .bin file

I really like the look and feel of this hex editor in VSCode.  It has many of the features I am looking for and is a vital tool doing embedded work.
I have run across a small problem where edits made to a .bin file are not being saved.
Steps to reproduce:
1.) create a text file with a single word in it.  I chose "hello"
2.) save the file, then change the file extension from .txt to .bin
3.) open the .bin file in VS code and open the hexdump
4.) edit any byte by right clicking and selecting "edit value under cursor" or by hitting shift+enter (I changed "hello" to "henlo" by modifying byte 2 from 0x6C to 0x6E
5.) save the file.  Save all, save as, save, ctrl-s, any way you want.
6.) close the file
7.) open the file
8.) observe that the file is unchanged (it still says "hello")
This problem seems to occur even if the file is a .txt file.
Win 7, 64 bit
hexdump for VSCode v1.2.1
VSCode v1.10.2

Can you try to use the Export to Binary File.. command ?
You can use the right-click menu, or ctrl-shift-s shortcut in a hexdump document.

That works.  Am I doing something wrong by trying to save the file?

There is no way (that I know of) for a extension to hijack the save event of a TextDocumentContentProvider. The best I can do is to assign export command to similar shortcuts.
As a side note, it seems the file refresh doesn't work properly. I'll have a look.

I guess I got confused because under commands you list:

save (ctrl+s, cmd+s) Save file

Is that meant for something else?

This seems fixed now with version 1.3.0. Please update.


Fixed Math Function Declaration

Fixed function declaration of DecomposeTransform() function
When @TheCherno copied the DecomposeTransform() function diff, the declaration he created in Math.h class was different from the definition, which could lead to some inconsistencies
PR impact
List of related issues/PRs this will solve:

Impact
Issue/PR

Issues this solves
None

Other PRs this solves
None

Proposed fix
Changed the declaration variable names to the ones which were copied in diff

I really think it should have been the other way around, i.e. keep the "out" prefix for the arguments in the declaration and change the definition's signature to match. That way it is clear that those arguments are the output of the Hazel::Math::DecomposeTransform() function.

That's indeed how he intended it to be when he prepared the diff during the livestream (to be more explicit), however in the youtube video he didn't do this.. I did think about this, in the end I went with how he implemented it in the youtube video, which is the usual approach I take when deciding these things... It's only a minor detail, and it should be obvious from the name of the function what it does anyway...


Update Dockerfile - robust parsing of .env

Resolves #424. Add checks when parsing .env to make Dockerfile more robust, preventing crashes when creating containers and giving more descriptive errors when something is really wrong.
Details:

Added a check to prevent container creation from crashing due to blank lines in .env file
Added strip for variable name and value in case user has whitespace around the '='
Added descriptive error for bad line in .env that contains no '='
Added descriptive error for bad line in .env that contains no variable name before '='

Testing:
Honestly I have no idea if this is covered by automatic tests. I tested manually by doing the following:

Navigate to the task-standard/workbench directory
Create a .env file
Include some correct definitions, including new lines and whitespace around the equal line on some lines.
Add an incorrect line that contains text with no variable definition (no '=')
Run npm run task -- <path_to_task_family_directory> <task_name>
Inspect error message for correct/descriptive output
Add '=' to the start of the bad line in .env to represent a variable definition with no variable name.
Repeat steps 5-6
Remove bad line in .env
Repeat step 5, container should be created with no error.

Resolves #424

@mtaran thanks for the feedback! I've made changes based on your suggestions.


Add ability to pull data from any temp sensor or fan speed that exists in klipper

Is your feature request related to a problem? Please describe.
Strictly a feature request for additional sensors being monitored, but I gotta be honest, its gonna be big one that might not be entirely feasible due to possible different naming conventions that can happen in klipper.
I would like to see sensors for other temp sensors and various fan speeds if they exist in the klipper config, regardless of what they are named.
Describe your setup
Depends on the printer for if they are running a pi or a cb1 or something else. Stack is debian, kiauh for managing the installs, klipper, moonraker, fluidd or mainsail, dealers choice depending on the printer or my mood. Printers are mostly different Vorons and a V400. Typical "I hate enders" deployment.
Describe the solution you'd like
As stated above, having some additional sensor data coming into home assistant to match what I can do with a simple rest sensor would be nice.
Being that these can have any naming convention and isn't standard like heater_bed it can create an interesting problem for implementing this. Maybe grab the list of all enabled heaters per printer and then have it create sensors per entry... Not sure how that would look on the implementation side.
Same concept but for fan speeds as well would be good as well. I'm happy to split this into a separate feature request.
Additional context
Here is a snippet from the list objects API call from one of my machines to give you an example of the types of objects/sensors I'm looking for. These names could be anything machine to machine, hence the possible challenge with this part.
            "fan_generic BedFans",
            "heater_fan filter_fan",
            "heater_fan controller_fan",
            "temperature_sensor enclosure_temp",
            "temperature_sensor frame",
            "temperature_sensor bed_top",

Hi @DasBurninator, we just merged a pr #47 that adds the support for those temperature sensors.
It will be part of next release.
I'll try to had the fan sensor as well since it's pretty similar

I should have glanced at the closed PRs!
That is great to see getting added in.

added in release 0.5.0


why?

read README first...

you don't have nodejs installed

Don't increase point to paint

Open a new issue. This one is done


not useable on mobile

Fallout from #131 : it does not appear to render well in iOS mobile.   Previously the app looks like a mini desktop version requiring squinting but functional.   using Safari's dev tools, the app in iOS large size now looks like this:

TO DO for this issue:

[ ]  set left side form to use stacking or dynamic col width for small sizes
[ ] OR create icon to show/hide (collapse) job menu in small sizes
[ ]  need to add icon to display menu when it's off-screen at small sizes

this was completed with manuscript submission.


Add a instruction text for the controls.

Add a text line below the game window that contains the game control instructions.

so basically we have to write what we have to do in this game?

Although I want to work on this issue under JWOC

Hey @vk20july you just need to specify that the game uses the arrow keys to move the base. I would recommend you to use the key icons so that the instruction looks good.
Icon example:

But make sure that the instruction is descriptive like :
Use (icon) to move the base left and (icon) to move it to the right.

got it


Paperwhite - Page is not updating - how to debug

Thanks for developing this.
My kindle fetches the image I specified, when I run start.sh.
But then it never updates the image. I just stays at the original image
My cron expression is set to 15 minutes, see below.
Any idea why my screen is not updating?
I think I also amended some of the other settings (partial update -> 1)

Meanwhile I found the log file in /logs
I hope this helps
update_to_display: update_mode=FULL, wave_mode=2 inverted=0
swipe feature is not supported in this platfom G1
Starting dashboard with */15 5-23 * * * refresh...
./dash.sh: line 30: /etc/init.d/framework: not found
Mon Aug 26 08:08:56 EEDT 2024 Battery level: 53%.
Refreshing dashboard
Wi-Fi connected
Partial screen refresh
update_to_display: update_mode=PARTIAL, wave_mode=2 inverted=0
swipe feature is not supported in this platfom G1
Going to suspend, next wakeup in 363s
cat: can't open '/sys/devices/platform/mxc_rtc.0/wakeup_enable': No such file or directory
sh: bad number
Mon Aug 26 13:41:01 EEDT 2024 Battery level: 51%.
Refreshing dashboard
Wi-Fi connected

It seems like my kindle (I think I have a PW3, Generation 7; but Amazon's naming is confusing!) is lacking some files that your script uses....

So I have fixed this issue (for my Paperwhite Kindle).
let me know if I should open a pull request.
This code works for me: https://github.com/kafisatz/kindle-dash


Two feature requests/questions (directory level export and embedded images)

Just tested. This is awesome!
Is it possible to only export from Obsidian a selected directory?
And also include export of embedded images?
Thank you in advance!!

Thank you for your feedback.
The image feature is on my roadmap.
I'll add the folder selection feature too.

Being able to export specific folders from Obsidian would be incredible. Thank you!

I've created #11 and #10 to answer your feedback.

This is incredible!!


BodyContainer with Route issue

Hello,
I like your responsive drawer idea!
I am experiencing some issues with nested <Route> (react-router v4) elements inside the <BodyContainer>. I was expecting that the routing will still work. However, the render does not trigger after a route change.
I was able to change the <BodyContainer> to a simple <div> to make it work but now I need to handle the widths manually. Is there any plan for this to be supported?
Thanks

Hi,
Have you tried to put the BodyContainer inside the Route?
Take a look into this demo project that demonstrates the usage of this and other libraries.

The demo project looks great.
This does indeed fix my issue.
Thanks!


fix: shutdown supervisor in healthcheck.sh on fatal error, fixes #5993

The Issue

#5993

How This PR Solves The Issue
I checked https://docs.docker.com/reference/dockerfile/#healthcheck before doing any change and when we use start_period, no matter what we do during this period, the container cannot become unhealthy.

start period provides initialization time for containers that need time to bootstrap. Probe failure during that period will not be counted towards the maximum number of retries.

I also searched for a fast fail when starting the container, but that's all I found:
https://forums.docker.com/t/healthcheck-fail-fast-feature-during-container-start-up/121201
So, in the end, I decided to do the same thing as suggested in:

#5906

but in a simpler way.
Also I decreased startretries=10 to startretries=3 in supervisor, there is no reason to try more and wait longer, if the process cannot start several times already.
Manual Testing Instructions
See error for php-fpm after 20-30 seconds (without waiting for 2 minutes default timeout):
echo 'RUN chmod 000 /run/php' > .ddev/web-build/Dockerfile
ddev restart
...
Failed waiting for web/db containers to become ready: web container failed: log=&{2024-03-29 21:42:41.347467771 +0200 EET 2024-03-29 21:42:42.086281673 +0200 EET 143 php-fpm:FATAL Shut down
}, err=ddev-d10-web container is unhealthy: &{2024-03-29 21:42:41.347467771 +0200 EET 2024-03-29 21:42:42.086281673 +0200 EET 143 php-fpm:FATAL Shut down
}, please use 'ddev logs -s web' and 'docker logs ddev-d10-web' and 'docker inspect --format "{{ json .State.Health }}" ddev-d10-web' to find out why it failed

Automated Testing Overview

Related Issue Link(s)
Release/Deployment Notes

Just looking at the code says this is fine, will manually test, thanks!

Rebased, and pushed the image again.


mark Thread.start as nothrow

might only fail on resource exhaustion

updated

Auto-merge toggled on

@MartinNowak It looks like this set of changes - specifically "round thread stack size to pagesize and min stack size" - is what's causing https://issues.dlang.org/show_bug.cgi?id=14476
The unittest black that it introduces at the end of core.thread to test the functionality that it adds fails on FreeBSD 9+ (whereas the autotesters are running 8.4, which is why they didn't catch it).


CSS change to fit dashboard in VR

Hi,
You have an amazing product here and I wanted to contribute to it. I tried it out in VR and it's great, but I couldn't see the enter VR mode in certain view width of the browser. Hopefully, this can help.
Before:

After:

Thank you @AlexChum for this contribution.
Don't hesitate to contribute further to this project.


chore: upgrade eth dependencies

What was wrong?
I need to upgrade my eth dependencies
How was it fixed?
I have to first upgrade this https://github.com/ethereum/py-evm/pull/2062
and then maybe include that it in the py-evm dependencies as part of this PR
To-Do:

[ ] Add entry to the release notes

Cute Animal Picture

Thanks for the PR! See my comment here

This should be fixed now in a more sensible way. Lmk if you're still having dependency problems though, and we'll prioritize fixing!


Can't specify multiple times /lib

Hey,
for some reason it doesn't work when I provide multiple /lib, here are the commands I use:
./ILRepack.exe C:/Users/X/Desktop/A.exe /out:C:/Users/X/Desktop/SomeDir/A.exe /lib:C:/Users/X/Desktop/SomeDir /lib:C:/Users/X/Desktop/AnotherDir
Only the first /lib is used, but not the second. Does anybody have a idea how the /lib is used multiple times?
Thanks for any help! :)

Can you try the latest version? Seems to be working fine for me.


Menu item is not displayed as selected

Current behavior

The menu item is not displayed as selected for any of the page.
Expected behavior

Steps to reproduce the issue

Go to threshold management app
Go to settings page
Open menu
Verify that the settinga item in the menu is not enabled/selected

Can you handle fixing this bug by yourself?

[x] YES
[ ] NO

Environment details

Browser:
OS:
Code Version:

Additional information

Closing as completed https://github.com/hotwax/threshold-management/pull/231


What is the data type for LetsPeppol?

What do we call the data type that LetsPeppol provides? Is it "Invoice" or "Bookkeeping" or ...?

We can call it "Invoice". A more generic term, that is also used in Peppol docs would be "Business Document", but I think once we start working on Purchase Orders etc we would probably treat them separately anyway, so "Invoice" should be fine!


Use \mod for mod emit in latex and wrap latex emit as inline math

cc @timothycobrien

done

@ayazhafiz I believe there shouldn't be a \ before characters such as ( or ) (see file here)

you're right. want to send a patch?

Will do

Associated exponents are not correct, how should we go about modifying them? @ayazhafiz
$2 ^ 3 ^ 2$ errors, for example

Yes, I noticed that too. They will need to be wrapped in braces according to the association. So that example should be $2 ^ {3 ^ 2}$.


[DOC] Life of a contract

Is your feature request related to a problem? Please describe.
Smart contracts are an alien term for most developers.
Specifically, properties around immutability, trust and others should be clearly communicate for people who are new to blockchain.
Additionally, there are various ways contracts can behave and live on MainNet.
For example here are set of options described - https://github.com/nearprotocol/NEPs/issues/40#issuecomment-602025607
Describe the solution you'd like
We should have a description that guides people:

mental model for smart contracts (and separately how NEAR can be used for serverless functions vs contracts)
various trust models, how to identify contracts that are trust-less, community ran or company/individual ran.
how the deployment will look like - specifically, key management, upgrades, financial questions

We now have this included in our documentation  here https://docs.near.org/docs/tutorials/contracts/nfts/upgrade-contract/#redeploying-contract


Add missing default class in react emoji components

#869 and #866 don't depend on each other so I don't understand why you pushed it together.


Exception for broken SVO

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, bug report, or anything other than a feature request directly related to this project.

Proposal
When opening an corrupted SVO with sl.Camera.open no exception is thrown. In Windows, the process keeps running (apparently it is IO bound forever). In Linux, the process is aborted. I tried a lot of thing, but all I can do is to have some workarounds done. It would be really nice if I could just have a try-except block to treat an eventual exception.
Use-Case
It would make possible to just treat errors instead of just closing the script or having to close the terminal.
Anything else?
No response

Thanks for the report, could you share an SVO file that trigger this error? You can send it to<EMAIL_ADDRESS>if it's not meant to be public

Okay, I will send it to you right now. Thank you!

The ZED SDK 3.6.4 is released and includes the fix for this issue https://www.stereolabs.com/developers/release/

Thank you!


Function Support

Add syntax for calling functions, and a framework for adding functions to the environment.

Completed in b3a582004d138c49987e325f7582e6a042395a55


fix: save output from the backport create-pr step to job outputs

Adding a backport label failed to create a PR, but didn't create an associated issue.
I reproduced a failing backport on my fork and was able to verify an issue was created once these changes were included. The root cause is the outputs from the backport action are available at the step level, but are not automatically included in the outputs for the job.
Once this PR is merged, I'll verify the fix by removing/re-adding the backport releases/v0.1 label to https://github.com/fedimint/fedimint/pull/3156. This will trigger the backport workflow and should create an issue once the backport PR fails to create.

Once this PR is merged, I'll verify the fix by removing/re-adding the backport releases/v0.1 label to https://github.com/fedimint/fedimint/pull/3156. This will trigger the backport workflow and should create an issue once the backport PR fails to create.

Re-adding the label and triggering the backport workflow was able to successfully create a backport PR. I'll keep an eye out for additional backport releases/v0.1 tags to verify this fix works.


[ADD] Custom token support for SOL

To be congruent with all other chains and have the possibility to add custom SPL tokens please add the "Custom Token" option to SOLANA

QA done.


Uniform circular motion influencer for 3d particles

created a new DynamicsModifier called CircularMotion and added it to the Flame tool and the GdxTests. The CircularMotion influencer adds a velocity to a particle in the activateParticles method and applies a force toward an axis specified by theta and phi, which is the axis of rotation for uniform circular motion.

The only files I changed here are gdx/src/com/badlogic/gdx/graphics/g3d/particles/influencers/DynamicsModifier.java and CHANGES. All the other changes are from rebasing.