apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:49:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-71-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-71.ec2.internal uid: 590c1928-4148-454e-a249-a66817969455 resourceVersion: "42830" uid: 78b5eacc-5afc-4fa7-83b5-155781cb5182 spec: sourcePod: network-check-source-7f44b6dd87-q9k58 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T19:56:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.038888ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:17:03Z" - latency: 1.088946ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:16:03Z" - latency: 1.041658ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:15:03Z" - latency: 1.12369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:14:03Z" - latency: 875.354µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:13:03Z" - latency: 699.648µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:12:03Z" - latency: 773.52µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:11:03Z" - latency: 933.887µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:10:03Z" - latency: 1.303608ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:09:03Z" - latency: 1.38577ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:08:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:49:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-71-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-71.ec2.internal uid: 590c1928-4148-454e-a249-a66817969455 resourceVersion: "44977" uid: 726c2136-fe75-4ed5-a70b-0ff2852ff910 spec: sourcePod: network-check-source-7f44b6dd87-q9k58 targetEndpoint: aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T19:55:03Z" message: 'load-balancer-api-external: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.964409ms message: 'load-balancer-api-external: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:19:03Z" - latency: 9.039792ms message: 'load-balancer-api-external: resolved host name aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:19:03Z" - latency: 6.137104ms message: 'load-balancer-api-external: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:18:03Z" - latency: 8.361276ms message: 'load-balancer-api-external: resolved host name aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:18:03Z" - latency: 4.538087ms message: 'load-balancer-api-external: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:17:03Z" - latency: 8.093889ms message: 'load-balancer-api-external: resolved host name aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:17:03Z" - latency: 4.070873ms message: 'load-balancer-api-external: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:16:03Z" - latency: 8.599824ms message: 'load-balancer-api-external: resolved host name aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:16:03Z" - latency: 3.866222ms message: 'load-balancer-api-external: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:15:03Z" - latency: 8.11192ms message: 'load-balancer-api-external: resolved host name aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:15:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:49:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-71-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-71.ec2.internal uid: 590c1928-4148-454e-a249-a66817969455 resourceVersion: "44976" uid: 2d62fd9a-8efb-4d15-9730-335265842b50 spec: sourcePod: network-check-source-7f44b6dd87-q9k58 targetEndpoint: aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T19:55:03Z" message: 'load-balancer-api-internal: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.960456ms message: 'load-balancer-api-internal: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:19:03Z" - latency: 9.007705ms message: 'load-balancer-api-internal: resolved host name aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:19:03Z" - latency: 6.142156ms message: 'load-balancer-api-internal: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:18:03Z" - latency: 8.334143ms message: 'load-balancer-api-internal: resolved host name aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:18:03Z" - latency: 2.997258ms message: 'load-balancer-api-internal: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:17:03Z" - latency: 8.063011ms message: 'load-balancer-api-internal: resolved host name aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:17:03Z" - latency: 3.82508ms message: 'load-balancer-api-internal: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:16:03Z" - latency: 8.574548ms message: 'load-balancer-api-internal: resolved host name aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:16:03Z" - latency: 4.396034ms message: 'load-balancer-api-internal: tcp connection to aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:15:03Z" - latency: 8.063834ms message: 'load-balancer-api-internal: resolved host name aa3bf8e3dc64b4f0c868360a26dbe46a-d7835f163b87874e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T20:15:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:49:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-71-to-network-check-target-ip-10-0-134-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-71.ec2.internal uid: 590c1928-4148-454e-a249-a66817969455 resourceVersion: "42828" uid: d9192fbb-7809-4c3d-80c1-8b9f43c96234 spec: sourcePod: network-check-source-7f44b6dd87-q9k58 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T19:56:03Z" message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.459954ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:17:03Z" - latency: 2.216601ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:16:03Z" - latency: 2.433887ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:15:03Z" - latency: 2.485509ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:14:03Z" - latency: 2.389207ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:13:03Z" - latency: 2.426798ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:12:03Z" - latency: 2.407211ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:11:03Z" - latency: 2.185205ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:10:03Z" - latency: 2.147733ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:09:03Z" - latency: 2.346907ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:08:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:49:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-71-to-network-check-target-ip-10-0-137-112 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-71.ec2.internal uid: 590c1928-4148-454e-a249-a66817969455 resourceVersion: "42829" uid: df13757d-3d48-456a-ab65-0c6ee5a45e51 spec: sourcePod: network-check-source-7f44b6dd87-q9k58 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T19:56:03Z" message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.178024ms message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:17:03Z" - latency: 2.076811ms message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:16:03Z" - latency: 2.300945ms message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:15:03Z" - latency: 2.219793ms message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:14:03Z" - latency: 2.027402ms message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:13:03Z" - latency: 2.174128ms message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:12:03Z" - latency: 1.964129ms message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:11:03Z" - latency: 2.266893ms message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:10:03Z" - latency: 2.042392ms message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:09:03Z" - latency: 1.972322ms message: 'network-check-target-ip-10-0-137-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:08:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:49:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-71-to-network-check-target-ip-10-0-142-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-71.ec2.internal uid: 590c1928-4148-454e-a249-a66817969455 resourceVersion: "42827" uid: 176d99b5-6700-4779-9ef7-554dfe508a02 spec: sourcePod: network-check-source-7f44b6dd87-q9k58 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-20T19:56:03Z" message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 816.624µs message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:17:03Z" - latency: 758.128µs message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:16:03Z" - latency: 779.82µs message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:15:03Z" - latency: 1.017005ms message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:14:03Z" - latency: 789.053µs message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:13:03Z" - latency: 845.536µs message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:12:03Z" - latency: 810.438µs message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:11:03Z" - latency: 781.988µs message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:10:03Z" - latency: 1.044642ms message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:09:03Z" - latency: 777.181µs message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:08:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T19:49:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-71-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-71.ec2.internal uid: 590c1928-4148-454e-a249-a66817969455 resourceVersion: "44974" uid: d8916e86-f325-4e0c-a4c7-f0cd81700800 spec: sourcePod: network-check-source-7f44b6dd87-q9k58 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T19:55:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 983.566µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:19:03Z" - latency: 1.804452ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T20:19:03Z" - latency: 844.049µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:18:03Z" - latency: 1.832711ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T20:18:03Z" - latency: 1.066614ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:17:03Z" - latency: 1.647242ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T20:17:03Z" - latency: 656.243µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:16:03Z" - latency: 1.535486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T20:16:03Z" - latency: 735.211µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T20:15:03Z" - latency: 1.720501ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T20:15:03Z" kind: List metadata: resourceVersion: ""