apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T00:47:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-85-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-85.ec2.internal uid: 60348e70-35e2-4d0a-89ab-7413ee3f7619 resourceVersion: "75230" uid: 5672401c-835f-4f48-b02b-57715008f985 spec: sourcePod: network-check-source-7d88cb55d8-lwmtc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T00:54:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.806µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:43:55Z" - latency: 996.995µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:42:55Z" - latency: 1.008514ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:41:55Z" - latency: 1.097254ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:40:55Z" - latency: 1.549357ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:39:55Z" - latency: 1.370845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:38:55Z" - latency: 1.095737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:37:55Z" - latency: 888.96µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:36:55Z" - latency: 1.235815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:35:55Z" - latency: 900.669µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T00:47:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-85-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-85.ec2.internal uid: 60348e70-35e2-4d0a-89ab-7413ee3f7619 resourceVersion: "79167" uid: 710b481d-0dc5-4967-ab55-b9089aa42d03 spec: sourcePod: network-check-source-7d88cb55d8-lwmtc targetEndpoint: aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T00:53:55Z" message: 'load-balancer-api-external: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.250848ms message: 'load-balancer-api-external: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:47:55Z" - latency: 13.43307ms message: 'load-balancer-api-external: resolved host name aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T01:47:55Z" - latency: 5.112828ms message: 'load-balancer-api-external: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:46:55Z" - latency: 8.827189ms message: 'load-balancer-api-external: resolved host name aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T01:46:55Z" - latency: 4.176882ms message: 'load-balancer-api-external: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:45:55Z" - latency: 13.316827ms message: 'load-balancer-api-external: resolved host name aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T01:45:55Z" - latency: 4.359569ms message: 'load-balancer-api-external: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:44:55Z" - latency: 9.337664ms message: 'load-balancer-api-external: resolved host name aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T01:44:55Z" - latency: 5.13955ms message: 'load-balancer-api-external: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:43:55Z" - latency: 10.091834ms message: 'load-balancer-api-external: resolved host name aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T01:43:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T00:47:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-85-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-85.ec2.internal uid: 60348e70-35e2-4d0a-89ab-7413ee3f7619 resourceVersion: "79168" uid: 6bdcef9a-b995-44c4-9551-a6e21b96addc spec: sourcePod: network-check-source-7d88cb55d8-lwmtc targetEndpoint: aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T00:53:55Z" message: 'load-balancer-api-internal: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.2571ms message: 'load-balancer-api-internal: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:47:55Z" - latency: 13.462727ms message: 'load-balancer-api-internal: resolved host name aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T01:47:55Z" - latency: 5.11758ms message: 'load-balancer-api-internal: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:46:55Z" - latency: 8.92017ms message: 'load-balancer-api-internal: resolved host name aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T01:46:55Z" - latency: 4.207217ms message: 'load-balancer-api-internal: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:45:55Z" - latency: 13.257756ms message: 'load-balancer-api-internal: resolved host name aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T01:45:55Z" - latency: 4.885655ms message: 'load-balancer-api-internal: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:44:55Z" - latency: 9.379664ms message: 'load-balancer-api-internal: resolved host name aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T01:44:55Z" - latency: 5.156128ms message: 'load-balancer-api-internal: tcp connection to aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:43:55Z" - latency: 10.036079ms message: 'load-balancer-api-internal: resolved host name aaaf2b0575b064b2f810d3afd10e17a3-3b3a83a2aed0679a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T01:43:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T00:47:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-85-to-network-check-target-ip-10-0-134-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-85.ec2.internal uid: 60348e70-35e2-4d0a-89ab-7413ee3f7619 resourceVersion: "75229" uid: 17727158-7cf1-4340-b3a3-f0d85eff4293 spec: sourcePod: network-check-source-7d88cb55d8-lwmtc targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T00:54:55Z" message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.9109ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:43:55Z" - latency: 2.442595ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:42:55Z" - latency: 2.254257ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:41:55Z" - latency: 1.907716ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:40:55Z" - latency: 2.131041ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:39:55Z" - latency: 2.559726ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:38:55Z" - latency: 2.463426ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:37:55Z" - latency: 2.069631ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:36:55Z" - latency: 2.097636ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:35:55Z" - latency: 2.210078ms message: 'network-check-target-ip-10-0-134-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T00:47:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-85-to-network-check-target-ip-10-0-136-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-85.ec2.internal uid: 60348e70-35e2-4d0a-89ab-7413ee3f7619 resourceVersion: "75228" uid: a196c9ac-4bba-4031-94e6-1371af8295af spec: sourcePod: network-check-source-7d88cb55d8-lwmtc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T00:54:55Z" message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.107133ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:43:55Z" - latency: 2.463407ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:42:55Z" - latency: 2.337443ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:41:55Z" - latency: 2.075657ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:40:55Z" - latency: 2.306536ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:39:55Z" - latency: 2.128768ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:38:55Z" - latency: 2.379283ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:37:55Z" - latency: 2.384443ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:36:55Z" - latency: 1.974231ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:35:55Z" - latency: 2.369629ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T00:47:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-85-to-network-check-target-ip-10-0-141-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-85.ec2.internal uid: 60348e70-35e2-4d0a-89ab-7413ee3f7619 resourceVersion: "75227" uid: 03e9bb60-276c-4cfd-8aa2-41604aeba461 spec: sourcePod: network-check-source-7d88cb55d8-lwmtc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-30T00:54:55Z" message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 869.114µs message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:43:55Z" - latency: 1.192665ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:42:55Z" - latency: 858.423µs message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:41:55Z" - latency: 1.119313ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:40:55Z" - latency: 1.178231ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:39:55Z" - latency: 855.68µs message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:38:55Z" - latency: 1.478759ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:37:55Z" - latency: 1.284821ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:36:55Z" - latency: 864.997µs message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:35:55Z" - latency: 1.052079ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:34:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T00:47:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-85-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-85.ec2.internal uid: 60348e70-35e2-4d0a-89ab-7413ee3f7619 resourceVersion: "79166" uid: f4add47a-6ceb-4397-873e-4ea9810c02c3 spec: sourcePod: network-check-source-7d88cb55d8-lwmtc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T00:53:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 748.621µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:47:55Z" - latency: 2.157046ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T01:47:55Z" - latency: 981.052µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:46:55Z" - latency: 1.887519ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T01:46:55Z" - latency: 979.998µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:45:55Z" - latency: 1.93042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T01:45:55Z" - latency: 953.465µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:44:55Z" - latency: 2.236169ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T01:44:55Z" - latency: 1.353993ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T01:43:55Z" - latency: 1.794111ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T01:43:55Z" kind: List metadata: resourceVersion: ""