apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: 48cc8168-aeb2-4c3c-9577-5b9c2f455ead resourceVersion: "21276" uid: b2047cdb-61b9-4ba7-917e-4147e0ef4344 spec: sourcePod: network-check-source-56499946bc-drd44 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T12:49:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 839.092µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:03:53Z" - latency: 1.114992ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:02:53Z" - latency: 1.316098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:53Z" - latency: 1.246813ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:53Z" - latency: 899.11µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:53Z" - latency: 860.586µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:53Z" - latency: 985.836µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:53Z" - latency: 1.123471ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:53Z" - latency: 1.020825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:55:53Z" - latency: 978.238µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:54:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: 48cc8168-aeb2-4c3c-9577-5b9c2f455ead resourceVersion: "19863" uid: 420c02d0-be99-4eef-9713-c4091e64926a spec: sourcePod: network-check-source-56499946bc-drd44 targetEndpoint: a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T12:48:53Z" message: 'load-balancer-api-external: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.264979ms message: 'load-balancer-api-external: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:53Z" - latency: 13.098072ms message: 'load-balancer-api-external: resolved host name a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T13:00:53Z" - latency: 5.65317ms message: 'load-balancer-api-external: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:53Z" - latency: 10.340948ms message: 'load-balancer-api-external: resolved host name a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:59:53Z" - latency: 6.349688ms message: 'load-balancer-api-external: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:53Z" - latency: 7.193184ms message: 'load-balancer-api-external: resolved host name a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:58:53Z" - latency: 4.653502ms message: 'load-balancer-api-external: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:53Z" - latency: 8.74056ms message: 'load-balancer-api-external: resolved host name a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:57:53Z" - latency: 6.106127ms message: 'load-balancer-api-external: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:53Z" - latency: 8.180189ms message: 'load-balancer-api-external: resolved host name a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:56:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: 48cc8168-aeb2-4c3c-9577-5b9c2f455ead resourceVersion: "19864" uid: 3ba7471e-b412-4da9-9351-5e1936239161 spec: sourcePod: network-check-source-56499946bc-drd44 targetEndpoint: a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T12:48:53Z" message: 'load-balancer-api-internal: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.074531ms message: 'load-balancer-api-internal: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:53Z" - latency: 13.011786ms message: 'load-balancer-api-internal: resolved host name a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T13:00:53Z" - latency: 5.683941ms message: 'load-balancer-api-internal: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:53Z" - latency: 10.44131ms message: 'load-balancer-api-internal: resolved host name a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:59:53Z" - latency: 6.316932ms message: 'load-balancer-api-internal: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:53Z" - latency: 7.120218ms message: 'load-balancer-api-internal: resolved host name a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:58:53Z" - latency: 4.724091ms message: 'load-balancer-api-internal: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:53Z" - latency: 8.803751ms message: 'load-balancer-api-internal: resolved host name a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:57:53Z" - latency: 7.196963ms message: 'load-balancer-api-internal: tcp connection to a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:53Z" - latency: 8.245191ms message: 'load-balancer-api-internal: resolved host name a0fd54a36f705431fae669e26712efe0-7015e6543468dd8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T12:56:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-134-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: 48cc8168-aeb2-4c3c-9577-5b9c2f455ead resourceVersion: "21274" uid: 3af9d8b7-c2c9-4319-935a-6c706f284f8d spec: sourcePod: network-check-source-56499946bc-drd44 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T12:49:53Z" message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.138191ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:03:53Z" - latency: 2.207383ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:02:53Z" - latency: 2.095518ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:53Z" - latency: 2.279788ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:53Z" - latency: 2.432925ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:53Z" - latency: 2.149648ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:53Z" - latency: 2.132872ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:53Z" - latency: 2.565422ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:53Z" - latency: 2.572335ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:55:53Z" - latency: 2.301468ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:54:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-137-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: 48cc8168-aeb2-4c3c-9577-5b9c2f455ead resourceVersion: "21273" uid: e11d420c-e92d-4b86-9c63-6650dfc71349 spec: sourcePod: network-check-source-56499946bc-drd44 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T12:49:53Z" message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.287838ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:03:53Z" - latency: 833.1µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:02:53Z" - latency: 744.532µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:53Z" - latency: 1.450369ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:53Z" - latency: 791.53µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:53Z" - latency: 880.121µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:53Z" - latency: 888.754µs message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:53Z" - latency: 1.083385ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:53Z" - latency: 1.508847ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:55:53Z" - latency: 1.381402ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:54:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-143-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: 48cc8168-aeb2-4c3c-9577-5b9c2f455ead resourceVersion: "21275" uid: 9b5bf8de-5e5e-4955-a452-cf1835f50a2e spec: sourcePod: network-check-source-56499946bc-drd44 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T12:49:53Z" message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.059141ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:03:53Z" - latency: 2.370205ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:02:53Z" - latency: 2.680009ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:01:53Z" - latency: 2.102716ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:53Z" - latency: 2.117423ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:53Z" - latency: 2.311485ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:53Z" - latency: 2.213301ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:53Z" - latency: 2.272231ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:53Z" - latency: 2.552535ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:55:53Z" - latency: 2.383948ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:54:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T12:42:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-242-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-242.ec2.internal uid: 48cc8168-aeb2-4c3c-9577-5b9c2f455ead resourceVersion: "19861" uid: 3bc02220-2f3f-40e0-9485-e960791135d3 spec: sourcePod: network-check-source-56499946bc-drd44 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T12:48:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.152µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T13:00:53Z" - latency: 1.579307ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T13:00:53Z" - latency: 863.118µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:59:53Z" - latency: 1.722689ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T12:59:53Z" - latency: 1.077253ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:58:53Z" - latency: 1.653468ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T12:58:53Z" - latency: 838.637µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:57:53Z" - latency: 1.684288ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T12:57:53Z" - latency: 1.406277ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T12:56:53Z" - latency: 1.899215ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T12:56:53Z" kind: List metadata: resourceVersion: ""