apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:42:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-19-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-19.ec2.internal uid: 2c0ca239-9228-4021-be7c-10dca2c58c48 resourceVersion: "56000" uid: 976a13b3-a72a-4f75-b9c7-18ad743bafc7 spec: sourcePod: network-check-source-989f8b8dc-r9jmn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T14:49:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.049531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:22Z" - latency: 962.643µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:22Z" - latency: 1.009665ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:22Z" - latency: 966.59µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:22Z" - latency: 1.020947ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:13:22Z" - latency: 1.156121ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:12:22Z" - latency: 1.028136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:11:22Z" - latency: 1.106246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:10:22Z" - latency: 935.862µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:09:22Z" - latency: 1.051116ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:08:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:42:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-19-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-19.ec2.internal uid: 2c0ca239-9228-4021-be7c-10dca2c58c48 resourceVersion: "56981" uid: 2cfa1099-2c59-405e-b617-acb58aa6501c spec: sourcePod: network-check-source-989f8b8dc-r9jmn targetEndpoint: a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T14:48:22Z" message: 'load-balancer-api-external: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.653541ms message: 'load-balancer-api-external: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:18:22Z" - latency: 7.923992ms message: 'load-balancer-api-external: resolved host name a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:18:22Z" - latency: 6.135904ms message: 'load-balancer-api-external: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:22Z" - latency: 8.448687ms message: 'load-balancer-api-external: resolved host name a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:17:22Z" - latency: 5.45633ms message: 'load-balancer-api-external: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:22Z" - latency: 7.247227ms message: 'load-balancer-api-external: resolved host name a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:16:22Z" - latency: 4.073288ms message: 'load-balancer-api-external: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:22Z" - latency: 7.041962ms message: 'load-balancer-api-external: resolved host name a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:15:22Z" - latency: 5.674399ms message: 'load-balancer-api-external: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:22Z" - latency: 7.592163ms message: 'load-balancer-api-external: resolved host name a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:14:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:42:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-19-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-19.ec2.internal uid: 2c0ca239-9228-4021-be7c-10dca2c58c48 resourceVersion: "56980" uid: b2272253-a72b-4ccc-9414-4b90237a8020 spec: sourcePod: network-check-source-989f8b8dc-r9jmn targetEndpoint: a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T14:48:22Z" message: 'load-balancer-api-internal: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.57663ms message: 'load-balancer-api-internal: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:18:22Z" - latency: 7.896085ms message: 'load-balancer-api-internal: resolved host name a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:18:22Z" - latency: 6.118749ms message: 'load-balancer-api-internal: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:22Z" - latency: 8.540671ms message: 'load-balancer-api-internal: resolved host name a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:17:22Z" - latency: 5.421333ms message: 'load-balancer-api-internal: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:22Z" - latency: 7.379764ms message: 'load-balancer-api-internal: resolved host name a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:16:22Z" - latency: 4.711895ms message: 'load-balancer-api-internal: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:22Z" - latency: 7.062207ms message: 'load-balancer-api-internal: resolved host name a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:15:22Z" - latency: 3.770041ms message: 'load-balancer-api-internal: tcp connection to a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:22Z" - latency: 7.668794ms message: 'load-balancer-api-internal: resolved host name a5fd46704566640f392ad05bde7b11f4-1a850be9751576bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:14:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:42:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-19-to-network-check-target-ip-10-0-131-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-19.ec2.internal uid: 2c0ca239-9228-4021-be7c-10dca2c58c48 resourceVersion: "55999" uid: bfc779db-3b52-40b2-8fbd-f415481f72d6 spec: sourcePod: network-check-source-989f8b8dc-r9jmn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:49:22Z" message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.538016ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:22Z" - latency: 2.384607ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:22Z" - latency: 2.275735ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:22Z" - latency: 2.261353ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:22Z" - latency: 2.519476ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:13:22Z" - latency: 2.577303ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:12:22Z" - latency: 2.263253ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:11:22Z" - latency: 2.56595ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:10:22Z" - latency: 2.4012ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:09:22Z" - latency: 2.228735ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:08:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:42:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-19-to-network-check-target-ip-10-0-136-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-19.ec2.internal uid: 2c0ca239-9228-4021-be7c-10dca2c58c48 resourceVersion: "55997" uid: ff0c1dd2-75cc-4730-829f-3227688873a7 spec: sourcePod: network-check-source-989f8b8dc-r9jmn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:49:22Z" message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 975.079µs message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:22Z" - latency: 1.194935ms message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:22Z" - latency: 1.106548ms message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:22Z" - latency: 979.855µs message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:22Z" - latency: 973.86µs message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:13:22Z" - latency: 1.216961ms message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:12:22Z" - latency: 1.029093ms message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:11:22Z" - latency: 1.013709ms message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:10:22Z" - latency: 959.136µs message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:09:22Z" - latency: 1.005839ms message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:08:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:42:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-19-to-network-check-target-ip-10-0-142-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-19.ec2.internal uid: 2c0ca239-9228-4021-be7c-10dca2c58c48 resourceVersion: "55998" uid: 0a261929-46fd-4b85-a851-131d56755d8b spec: sourcePod: network-check-source-989f8b8dc-r9jmn targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T14:49:22Z" message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.212788ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:22Z" - latency: 2.126602ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:22Z" - latency: 2.067696ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:22Z" - latency: 2.372857ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:22Z" - latency: 2.361672ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:13:22Z" - latency: 2.292195ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:12:22Z" - latency: 2.152158ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:11:22Z" - latency: 2.449169ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:10:22Z" - latency: 2.523715ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:09:22Z" - latency: 2.487697ms message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:08:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T14:42:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-19-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-19.ec2.internal uid: 2c0ca239-9228-4021-be7c-10dca2c58c48 resourceVersion: "56979" uid: de221137-3df7-4e5b-8c52-ff64ebc1e0af spec: sourcePod: network-check-source-989f8b8dc-r9jmn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T14:48:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.876µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:18:22Z" - latency: 1.753702ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:18:22Z" - latency: 1.292534ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:17:22Z" - latency: 2.157971ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:17:22Z" - latency: 1.256724ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:16:22Z" - latency: 1.795438ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:16:22Z" - latency: 749.463µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:15:22Z" - latency: 2.177687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:15:22Z" - latency: 980.061µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:14:22Z" - latency: 1.818686ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:14:22Z" kind: List metadata: resourceVersion: ""