apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:14:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-102.ec2.internal uid: dedadf45-cd6b-4019-89db-ea8d7bd4c809 resourceVersion: "64748" uid: 66f1a1ed-2094-4cf7-9cbe-932c02475a4d spec: sourcePod: network-check-source-7d88cb55d8-7cgsr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T00:21:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.593699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:25Z" - latency: 2.003422ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:25Z" - latency: 1.592341ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:25Z" - latency: 1.283762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:25Z" - latency: 935.869µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:25Z" - latency: 3.015631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:51:25Z" - latency: 975.669µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:50:25Z" - latency: 2.168323ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:49:25Z" - latency: 1.204024ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:48:25Z" - latency: 1.249729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:47:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:14:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-102.ec2.internal uid: dedadf45-cd6b-4019-89db-ea8d7bd4c809 resourceVersion: "64750" uid: 3a653227-6828-4519-ad20-f148e9c8d0af spec: sourcePod: network-check-source-7d88cb55d8-7cgsr targetEndpoint: a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T00:20:25Z" message: 'load-balancer-api-external: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.650899ms message: 'load-balancer-api-external: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:25Z" - latency: 6.842508ms message: 'load-balancer-api-external: resolved host name a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:56:25Z" - latency: 5.429113ms message: 'load-balancer-api-external: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:25Z" - latency: 8.417834ms message: 'load-balancer-api-external: resolved host name a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:55:25Z" - latency: 5.294074ms message: 'load-balancer-api-external: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:25Z" - latency: 9.004531ms message: 'load-balancer-api-external: resolved host name a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:54:25Z" - latency: 4.98468ms message: 'load-balancer-api-external: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:25Z" - latency: 8.54308ms message: 'load-balancer-api-external: resolved host name a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:53:25Z" - latency: 4.247155ms message: 'load-balancer-api-external: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:25Z" - latency: 8.206121ms message: 'load-balancer-api-external: resolved host name a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:52:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:14:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-102.ec2.internal uid: dedadf45-cd6b-4019-89db-ea8d7bd4c809 resourceVersion: "64749" uid: bf99f0ec-50c5-463f-9709-45e516f98485 spec: sourcePod: network-check-source-7d88cb55d8-7cgsr targetEndpoint: a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T00:20:25Z" message: 'load-balancer-api-internal: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.657193ms message: 'load-balancer-api-internal: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:25Z" - latency: 6.809905ms message: 'load-balancer-api-internal: resolved host name a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:56:25Z" - latency: 4.076299ms message: 'load-balancer-api-internal: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:25Z" - latency: 8.356637ms message: 'load-balancer-api-internal: resolved host name a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:55:25Z" - latency: 5.319012ms message: 'load-balancer-api-internal: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:25Z" - latency: 9.051222ms message: 'load-balancer-api-internal: resolved host name a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:54:25Z" - latency: 5.053891ms message: 'load-balancer-api-internal: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:25Z" - latency: 8.584332ms message: 'load-balancer-api-internal: resolved host name a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:53:25Z" - latency: 4.283645ms message: 'load-balancer-api-internal: tcp connection to a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:25Z" - latency: 8.121384ms message: 'load-balancer-api-internal: resolved host name a2c6e616c1c9d41b080e7bc2ebf0fa26-826ce65f571150b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T00:52:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:14:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-102-to-network-check-target-ip-10-0-136-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-102.ec2.internal uid: dedadf45-cd6b-4019-89db-ea8d7bd4c809 resourceVersion: "64744" uid: 360040af-bd36-458d-8cea-f58359f936e8 spec: sourcePod: network-check-source-7d88cb55d8-7cgsr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T00:21:25Z" message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.785978ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:25Z" - latency: 2.436381ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:25Z" - latency: 1.069357ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:25Z" - latency: 1.734695ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:25Z" - latency: 1.246113ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:25Z" - latency: 1.893156ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:51:25Z" - latency: 1.928863ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:50:25Z" - latency: 2.763208ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:49:25Z" - latency: 1.587866ms message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:48:25Z" - latency: 930.677µs message: 'network-check-target-ip-10-0-136-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:47:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:14:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-102-to-network-check-target-ip-10-0-139-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-102.ec2.internal uid: dedadf45-cd6b-4019-89db-ea8d7bd4c809 resourceVersion: "64745" uid: 5e6d3e1c-643d-423d-b8ae-45675265f8b6 spec: sourcePod: network-check-source-7d88cb55d8-7cgsr targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T00:21:25Z" message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.21972ms message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:25Z" - latency: 2.441314ms message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:25Z" - latency: 2.00898ms message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:25Z" - latency: 1.992921ms message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:25Z" - latency: 2.626197ms message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:25Z" - latency: 2.44277ms message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:51:25Z" - latency: 1.8458ms message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:50:25Z" - latency: 2.57446ms message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:49:25Z" - latency: 1.776753ms message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:48:25Z" - latency: 1.963557ms message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:47:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:14:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-102-to-network-check-target-ip-10-0-139-9 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-102.ec2.internal uid: dedadf45-cd6b-4019-89db-ea8d7bd4c809 resourceVersion: "64747" uid: 66a617f6-84e5-4c42-a1fa-96f1912a3035 spec: sourcePod: network-check-source-7d88cb55d8-7cgsr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T00:21:25Z" message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.580656ms message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:25Z" - latency: 2.267467ms message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:25Z" - latency: 2.3202ms message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:25Z" - latency: 2.047505ms message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:25Z" - latency: 2.592959ms message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:25Z" - latency: 3.130961ms message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:51:25Z" - latency: 2.623833ms message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:50:25Z" - latency: 3.488121ms message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:49:25Z" - latency: 2.509126ms message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:48:25Z" - latency: 2.375659ms message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:47:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T00:14:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-102.ec2.internal uid: dedadf45-cd6b-4019-89db-ea8d7bd4c809 resourceVersion: "64746" uid: e431ad72-d3ce-470f-8063-ebbb536f38b1 spec: sourcePod: network-check-source-7d88cb55d8-7cgsr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T00:20:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 914.818µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:56:25Z" - latency: 1.64811ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T00:56:25Z" - latency: 898.664µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:55:25Z" - latency: 2.405086ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T00:55:25Z" - latency: 932.851µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:54:25Z" - latency: 2.290681ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T00:54:25Z" - latency: 834.503µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:53:25Z" - latency: 1.915044ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T00:53:25Z" - latency: 1.244261ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T00:52:25Z" - latency: 2.248725ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T00:52:25Z" kind: List metadata: resourceVersion: ""