apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-153-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-153.ec2.internal uid: 87772314-5e85-401a-8196-543e5c6b3ad7 resourceVersion: "26837" uid: e3b31e56-9928-4f43-b30f-c4248837c9ff spec: sourcePod: network-check-source-989f8b8dc-pd9fx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T18:59:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.324µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:06:53Z" - latency: 896.522µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:05:53Z" - latency: 911.358µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:04:53Z" - latency: 919.729µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:03:53Z" - latency: 1.012255ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:02:53Z" - latency: 868.62µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:01:53Z" - latency: 907.828µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:00:53Z" - latency: 799.433µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:59:53Z" - latency: 704.544µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:58:53Z" - latency: 1.200307ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:57:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-153-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-153.ec2.internal uid: 87772314-5e85-401a-8196-543e5c6b3ad7 resourceVersion: "25614" uid: fe664fc1-c7b9-4f63-9a0c-58f10a5a5d38 spec: sourcePod: network-check-source-989f8b8dc-pd9fx targetEndpoint: a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T18:58:53Z" message: 'load-balancer-api-external: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.610001ms message: 'load-balancer-api-external: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:04:53Z" - latency: 8.73722ms message: 'load-balancer-api-external: resolved host name a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:04:53Z" - latency: 4.829459ms message: 'load-balancer-api-external: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:03:53Z" - latency: 8.061778ms message: 'load-balancer-api-external: resolved host name a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:03:53Z" - latency: 6.066105ms message: 'load-balancer-api-external: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:02:53Z" - latency: 7.805069ms message: 'load-balancer-api-external: resolved host name a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:02:53Z" - latency: 5.631725ms message: 'load-balancer-api-external: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:01:53Z" - latency: 9.946075ms message: 'load-balancer-api-external: resolved host name a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:01:53Z" - latency: 4.79152ms message: 'load-balancer-api-external: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:00:53Z" - latency: 7.481207ms message: 'load-balancer-api-external: resolved host name a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:00:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-153-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-153.ec2.internal uid: 87772314-5e85-401a-8196-543e5c6b3ad7 resourceVersion: "25613" uid: f42526b8-919a-4a2f-b8d3-593b2dcb1c2b spec: sourcePod: network-check-source-989f8b8dc-pd9fx targetEndpoint: a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T18:58:53Z" message: 'load-balancer-api-internal: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.647972ms message: 'load-balancer-api-internal: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:04:53Z" - latency: 8.715004ms message: 'load-balancer-api-internal: resolved host name a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:04:53Z" - latency: 4.840706ms message: 'load-balancer-api-internal: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:03:53Z" - latency: 8.033696ms message: 'load-balancer-api-internal: resolved host name a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:03:53Z" - latency: 6.263792ms message: 'load-balancer-api-internal: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:02:53Z" - latency: 7.77601ms message: 'load-balancer-api-internal: resolved host name a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:02:53Z" - latency: 5.630295ms message: 'load-balancer-api-internal: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:01:53Z" - latency: 9.895468ms message: 'load-balancer-api-internal: resolved host name a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:01:53Z" - latency: 4.807965ms message: 'load-balancer-api-internal: tcp connection to a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:00:53Z" - latency: 7.467456ms message: 'load-balancer-api-internal: resolved host name a3b4af360272a484e965370b321d100d-257dd9086e133a29.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:00:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-153-to-network-check-target-ip-10-0-133-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-153.ec2.internal uid: 87772314-5e85-401a-8196-543e5c6b3ad7 resourceVersion: "26835" uid: c24f9ce5-1740-4334-9218-e3a1497ff89c spec: sourcePod: network-check-source-989f8b8dc-pd9fx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T18:59:53Z" message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.347143ms message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:06:53Z" - latency: 2.39854ms message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:05:53Z" - latency: 2.360485ms message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:04:53Z" - latency: 2.431973ms message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:03:53Z" - latency: 1.864613ms message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:02:53Z" - latency: 2.50379ms message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:01:53Z" - latency: 2.228704ms message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:00:53Z" - latency: 2.158719ms message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:59:53Z" - latency: 2.071698ms message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:58:53Z" - latency: 2.219916ms message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:57:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-153-to-network-check-target-ip-10-0-135-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-153.ec2.internal uid: 87772314-5e85-401a-8196-543e5c6b3ad7 resourceVersion: "26834" uid: 7c616bae-7811-4dd4-815c-caec0046fedd spec: sourcePod: network-check-source-989f8b8dc-pd9fx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T18:59:53Z" message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.311852ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:06:53Z" - latency: 2.282355ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:05:53Z" - latency: 2.035483ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:04:53Z" - latency: 2.190719ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:03:53Z" - latency: 2.127991ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:02:53Z" - latency: 2.197516ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:01:53Z" - latency: 2.324848ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:00:53Z" - latency: 1.974201ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:59:53Z" - latency: 1.756119ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:58:53Z" - latency: 2.442977ms message: 'network-check-target-ip-10-0-135-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:57:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-153-to-network-check-target-ip-10-0-140-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-153.ec2.internal uid: 87772314-5e85-401a-8196-543e5c6b3ad7 resourceVersion: "26833" uid: 5aaa9e2e-a152-4dc0-a417-93e1e5d1d339 spec: sourcePod: network-check-source-989f8b8dc-pd9fx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T18:59:53Z" message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.439732ms message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:06:53Z" - latency: 1.111982ms message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:05:53Z" - latency: 806.963µs message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:04:53Z" - latency: 845.611µs message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:03:53Z" - latency: 802.014µs message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:02:53Z" - latency: 1.229779ms message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:01:53Z" - latency: 1.29221ms message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:00:53Z" - latency: 836.972µs message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:59:53Z" - latency: 786.13µs message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:58:53Z" - latency: 1.347833ms message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:57:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:52:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-153-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-153.ec2.internal uid: 87772314-5e85-401a-8196-543e5c6b3ad7 resourceVersion: "25612" uid: 18804bf7-04a2-4682-89c9-f18a8e30c7c6 spec: sourcePod: network-check-source-989f8b8dc-pd9fx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T18:58:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 813.35µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:04:53Z" - latency: 1.606527ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:04:53Z" - latency: 897.089µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:03:53Z" - latency: 1.567304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:03:53Z" - latency: 1.082417ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:02:53Z" - latency: 1.547424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:02:53Z" - latency: 1.227376ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:01:53Z" - latency: 2.223111ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:01:53Z" - latency: 751.391µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:00:53Z" - latency: 1.510029ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:00:53Z" kind: List metadata: resourceVersion: ""