apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:06:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: 586e17fa-eeb6-4cae-8da5-a053a633af6f resourceVersion: "53777" uid: ec7be72e-ee2a-4662-8500-48a607bec836 spec: sourcePod: network-check-source-869dcfcdcd-7tn8s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T15:13:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.039738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:52Z" - latency: 1.136099ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:52Z" - latency: 1.016532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:52Z" - latency: 1.159365ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:52Z" - latency: 1.387199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:52Z" - latency: 1.102632ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:52Z" - latency: 1.122856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:52Z" - latency: 1.013731ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:34:52Z" - latency: 770.764µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:33:52Z" - latency: 840.921µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:32:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:06:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: 586e17fa-eeb6-4cae-8da5-a053a633af6f resourceVersion: "54554" uid: 447169a9-e01c-4ded-b9c2-84f5c57e09c9 spec: sourcePod: network-check-source-869dcfcdcd-7tn8s targetEndpoint: afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T15:12:52Z" message: 'load-balancer-api-external: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.876271ms message: 'load-balancer-api-external: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:52Z" - latency: 7.900861ms message: 'load-balancer-api-external: resolved host name afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:42:52Z" - latency: 4.944075ms message: 'load-balancer-api-external: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:52Z" - latency: 7.785914ms message: 'load-balancer-api-external: resolved host name afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:41:52Z" - latency: 7.319092ms message: 'load-balancer-api-external: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:52Z" - latency: 8.911023ms message: 'load-balancer-api-external: resolved host name afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:40:52Z" - latency: 5.141592ms message: 'load-balancer-api-external: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:52Z" - latency: 8.085787ms message: 'load-balancer-api-external: resolved host name afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:39:52Z" - latency: 7.56876ms message: 'load-balancer-api-external: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:52Z" - latency: 8.498086ms message: 'load-balancer-api-external: resolved host name afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:38:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:06:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: 586e17fa-eeb6-4cae-8da5-a053a633af6f resourceVersion: "54553" uid: 95da8d9a-981f-43c2-a0fe-2c44b6287ea6 spec: sourcePod: network-check-source-869dcfcdcd-7tn8s targetEndpoint: afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T15:12:52Z" message: 'load-balancer-api-internal: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.647874ms message: 'load-balancer-api-internal: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:52Z" - latency: 7.92878ms message: 'load-balancer-api-internal: resolved host name afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:42:52Z" - latency: 4.969922ms message: 'load-balancer-api-internal: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:52Z" - latency: 7.818222ms message: 'load-balancer-api-internal: resolved host name afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:41:52Z" - latency: 7.347576ms message: 'load-balancer-api-internal: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:52Z" - latency: 8.951409ms message: 'load-balancer-api-internal: resolved host name afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:40:52Z" - latency: 5.614447ms message: 'load-balancer-api-internal: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:52Z" - latency: 8.035486ms message: 'load-balancer-api-internal: resolved host name afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:39:52Z" - latency: 6.3306ms message: 'load-balancer-api-internal: tcp connection to afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:52Z" - latency: 8.53152ms message: 'load-balancer-api-internal: resolved host name afddda9bbbf9f4859ae622b14c4d8d27-77ada1a940198dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:38:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:06:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-network-check-target-ip-10-0-129-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: 586e17fa-eeb6-4cae-8da5-a053a633af6f resourceVersion: "53775" uid: 44867a43-b2ba-4c67-911c-5cc0eb37c351 spec: sourcePod: network-check-source-869dcfcdcd-7tn8s targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:13:52Z" message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.226163ms message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:52Z" - latency: 2.084366ms message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:52Z" - latency: 2.006225ms message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:52Z" - latency: 2.139813ms message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:52Z" - latency: 2.213602ms message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:52Z" - latency: 2.370627ms message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:52Z" - latency: 2.262505ms message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:52Z" - latency: 2.335365ms message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:34:52Z" - latency: 1.932077ms message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:33:52Z" - latency: 2.402276ms message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:32:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:06:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-network-check-target-ip-10-0-130-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: 586e17fa-eeb6-4cae-8da5-a053a633af6f resourceVersion: "53776" uid: 71f67e58-c6ab-427e-9135-32267f7173b2 spec: sourcePod: network-check-source-869dcfcdcd-7tn8s targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:13:52Z" message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.095474ms message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:52Z" - latency: 2.077877ms message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:52Z" - latency: 2.043223ms message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:52Z" - latency: 2.296226ms message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:52Z" - latency: 2.019517ms message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:52Z" - latency: 2.321215ms message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:52Z" - latency: 2.219681ms message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:52Z" - latency: 1.982477ms message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:34:52Z" - latency: 1.898993ms message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:33:52Z" - latency: 1.818794ms message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:32:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:06:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-network-check-target-ip-10-0-138-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: 586e17fa-eeb6-4cae-8da5-a053a633af6f resourceVersion: "53774" uid: aadc697a-5fd2-4803-9041-f40d084e5b0d spec: sourcePod: network-check-source-869dcfcdcd-7tn8s targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T15:13:52Z" message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 837.394µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:52Z" - latency: 640.956µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:52Z" - latency: 1.456276ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:52Z" - latency: 696.967µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:52Z" - latency: 972.114µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:37:52Z" - latency: 746.721µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:36:52Z" - latency: 1.247198ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:35:52Z" - latency: 747.853µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:34:52Z" - latency: 1.415575ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:33:52Z" - latency: 699.196µs message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:32:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T15:06:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-70-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-70.ec2.internal uid: 586e17fa-eeb6-4cae-8da5-a053a633af6f resourceVersion: "54552" uid: 56794e5a-3c45-4842-8135-bcf3ef262e53 spec: sourcePod: network-check-source-869dcfcdcd-7tn8s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T15:12:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 716.409µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:42:52Z" - latency: 1.648832ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:42:52Z" - latency: 938.763µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:41:52Z" - latency: 1.789627ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:41:52Z" - latency: 830.768µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:40:52Z" - latency: 2.151751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:40:52Z" - latency: 882.071µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:39:52Z" - latency: 1.862094ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:39:52Z" - latency: 1.134975ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:38:52Z" - latency: 1.593857ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:38:52Z" kind: List metadata: resourceVersion: ""