apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:52:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: f1816c8b-57d4-47d7-bcfc-60ea480e588d resourceVersion: "54933" uid: a489db2a-d3e8-4153-abdd-b5b6c58cbcef spec: sourcePod: network-check-source-989f8b8dc-tqzsb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T23:59:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 810.459µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:11Z" - latency: 1.085156ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:11Z" - latency: 705.363µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:11Z" - latency: 856.963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:11Z" - latency: 1.126993ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:11Z" - latency: 1.103737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:11Z" - latency: 902.963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:11Z" - latency: 885.215µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:11Z" - latency: 1.143738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:11Z" - latency: 912.064µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:52:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: f1816c8b-57d4-47d7-bcfc-60ea480e588d resourceVersion: "55888" uid: 84cd0bb4-43fe-4b59-9701-7bde9faba66d spec: sourcePod: network-check-source-989f8b8dc-tqzsb targetEndpoint: ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T23:58:11Z" message: 'load-balancer-api-external: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.873054ms message: 'load-balancer-api-external: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:11Z" - latency: 9.137843ms message: 'load-balancer-api-external: resolved host name ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:28:11Z" - latency: 4.537465ms message: 'load-balancer-api-external: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:11Z" - latency: 8.443682ms message: 'load-balancer-api-external: resolved host name ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:27:11Z" - latency: 5.547368ms message: 'load-balancer-api-external: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:11Z" - latency: 8.672758ms message: 'load-balancer-api-external: resolved host name ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:26:11Z" - latency: 4.766308ms message: 'load-balancer-api-external: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:11Z" - latency: 8.162411ms message: 'load-balancer-api-external: resolved host name ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:25:11Z" - latency: 3.914042ms message: 'load-balancer-api-external: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:11Z" - latency: 8.251989ms message: 'load-balancer-api-external: resolved host name ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:24:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:52:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: f1816c8b-57d4-47d7-bcfc-60ea480e588d resourceVersion: "55887" uid: 20b432de-c9e0-4bc6-b9c9-a1c2c9c4f5b6 spec: sourcePod: network-check-source-989f8b8dc-tqzsb targetEndpoint: ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T23:58:11Z" message: 'load-balancer-api-internal: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.233832ms message: 'load-balancer-api-internal: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:11Z" - latency: 9.088374ms message: 'load-balancer-api-internal: resolved host name ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:28:11Z" - latency: 6.158577ms message: 'load-balancer-api-internal: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:11Z" - latency: 8.387596ms message: 'load-balancer-api-internal: resolved host name ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:27:11Z" - latency: 5.578072ms message: 'load-balancer-api-internal: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:11Z" - latency: 8.653697ms message: 'load-balancer-api-internal: resolved host name ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:26:11Z" - latency: 4.645985ms message: 'load-balancer-api-internal: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:11Z" - latency: 8.130956ms message: 'load-balancer-api-internal: resolved host name ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:25:11Z" - latency: 3.924236ms message: 'load-balancer-api-internal: tcp connection to ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:11Z" - latency: 8.202958ms message: 'load-balancer-api-internal: resolved host name ab2b9b75447e340688122ffc5b5424c7-74edc1af15526444.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:24:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:52:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-ip-10-0-130-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: f1816c8b-57d4-47d7-bcfc-60ea480e588d resourceVersion: "54932" uid: 548d16b5-b1a2-48a8-97bd-0448a281c09d spec: sourcePod: network-check-source-989f8b8dc-tqzsb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:59:11Z" message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.121053ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:11Z" - latency: 2.143295ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:11Z" - latency: 2.191884ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:11Z" - latency: 2.601741ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:11Z" - latency: 2.55187ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:11Z" - latency: 2.679163ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:11Z" - latency: 2.481899ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:11Z" - latency: 2.427548ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:11Z" - latency: 2.253607ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:11Z" - latency: 2.361461ms message: 'network-check-target-ip-10-0-130-213: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:52:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-ip-10-0-135-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: f1816c8b-57d4-47d7-bcfc-60ea480e588d resourceVersion: "54931" uid: aa9b424f-f58f-4dda-a49b-18e72ee5966f spec: sourcePod: network-check-source-989f8b8dc-tqzsb targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:59:11Z" message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.228043ms message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:11Z" - latency: 2.312652ms message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:11Z" - latency: 2.083148ms message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:11Z" - latency: 2.368004ms message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:11Z" - latency: 2.281038ms message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:11Z" - latency: 2.349598ms message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:11Z" - latency: 2.318399ms message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:11Z" - latency: 2.412672ms message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:11Z" - latency: 2.074778ms message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:11Z" - latency: 2.465813ms message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:52:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-ip-10-0-139-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: f1816c8b-57d4-47d7-bcfc-60ea480e588d resourceVersion: "54930" uid: 788ab027-d73e-4ed0-8073-c9cb05d1b20c spec: sourcePod: network-check-source-989f8b8dc-tqzsb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T23:59:11Z" message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 859.87µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:11Z" - latency: 1.132242ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:11Z" - latency: 876.5µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:11Z" - latency: 849.522µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:11Z" - latency: 1.31854ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:11Z" - latency: 1.03457ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:11Z" - latency: 934.487µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:11Z" - latency: 1.39624ms message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:11Z" - latency: 979.932µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:11Z" - latency: 973.364µs message: 'network-check-target-ip-10-0-139-100: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:18:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:52:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-100-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-100.ec2.internal uid: f1816c8b-57d4-47d7-bcfc-60ea480e588d resourceVersion: "55886" uid: 41312973-3e0e-4598-8b86-9951564dfd02 spec: sourcePod: network-check-source-989f8b8dc-tqzsb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T23:58:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 866.451µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:11Z" - latency: 2.233487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:28:11Z" - latency: 909.868µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:11Z" - latency: 1.704329ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:27:11Z" - latency: 966.598µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:11Z" - latency: 1.749039ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:26:11Z" - latency: 1.021648ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:11Z" - latency: 1.616132ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:25:11Z" - latency: 902.802µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:11Z" - latency: 1.58234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:24:11Z" kind: List metadata: resourceVersion: ""