apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T13:51:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-214-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-214.ec2.internal uid: 62d45ac4-7673-42d4-b2d5-c3663d6bd9d3 resourceVersion: "37325" uid: 29b08553-ca0e-42bc-8728-543f64c5e3c5 spec: sourcePod: network-check-source-dbd9cf844-ns5hn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T13:58:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.117186ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:12:58Z" - latency: 866.293µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:11:58Z" - latency: 1.048191ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:10:58Z" - latency: 916.197µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:09:58Z" - latency: 938.113µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:08:58Z" - latency: 1.316288ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:07:58Z" - latency: 1.047428ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:06:58Z" - latency: 853.591µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:05:58Z" - latency: 854.396µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:04:58Z" - latency: 937.457µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:03:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T13:51:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-214-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-214.ec2.internal uid: 62d45ac4-7673-42d4-b2d5-c3663d6bd9d3 resourceVersion: "34868" uid: 8c4a0131-db22-4050-a009-c3ddaf24f471 spec: sourcePod: network-check-source-dbd9cf844-ns5hn targetEndpoint: a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T13:57:58Z" message: 'load-balancer-api-external: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.529193ms message: 'load-balancer-api-external: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:09:58Z" - latency: 6.580838ms message: 'load-balancer-api-external: resolved host name a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:09:58Z" - latency: 6.885257ms message: 'load-balancer-api-external: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:08:58Z" - latency: 6.368243ms message: 'load-balancer-api-external: resolved host name a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:08:58Z" - latency: 5.906612ms message: 'load-balancer-api-external: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:07:58Z" - latency: 6.768676ms message: 'load-balancer-api-external: resolved host name a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:07:58Z" - latency: 4.652653ms message: 'load-balancer-api-external: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:06:58Z" - latency: 5.991604ms message: 'load-balancer-api-external: resolved host name a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:06:58Z" - latency: 4.771117ms message: 'load-balancer-api-external: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:05:58Z" - latency: 6.872597ms message: 'load-balancer-api-external: resolved host name a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:05:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T13:51:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-214-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-214.ec2.internal uid: 62d45ac4-7673-42d4-b2d5-c3663d6bd9d3 resourceVersion: "34867" uid: 98637a0e-1364-42bb-8420-6a0cdf4305e5 spec: sourcePod: network-check-source-dbd9cf844-ns5hn targetEndpoint: a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T13:57:58Z" message: 'load-balancer-api-internal: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.23728ms message: 'load-balancer-api-internal: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:09:58Z" - latency: 6.636785ms message: 'load-balancer-api-internal: resolved host name a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:09:58Z" - latency: 4.501652ms message: 'load-balancer-api-internal: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:08:58Z" - latency: 6.413039ms message: 'load-balancer-api-internal: resolved host name a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:08:58Z" - latency: 5.479651ms message: 'load-balancer-api-internal: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:07:58Z" - latency: 6.745955ms message: 'load-balancer-api-internal: resolved host name a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:07:58Z" - latency: 4.286163ms message: 'load-balancer-api-internal: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:06:58Z" - latency: 5.929521ms message: 'load-balancer-api-internal: resolved host name a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:06:58Z" - latency: 4.759178ms message: 'load-balancer-api-internal: tcp connection to a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:05:58Z" - latency: 6.925688ms message: 'load-balancer-api-internal: resolved host name a68346f81dd964a6bbea7893e625ecde-abf684109027a1ce.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T14:05:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T13:51:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-214-to-network-check-target-ip-10-0-136-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-214.ec2.internal uid: 62d45ac4-7673-42d4-b2d5-c3663d6bd9d3 resourceVersion: "37324" uid: 704a5ea4-8ce2-4711-8288-efb74e5bfc42 spec: sourcePod: network-check-source-dbd9cf844-ns5hn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T13:58:58Z" message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.506612ms message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:12:58Z" - latency: 2.279571ms message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:11:58Z" - latency: 2.053576ms message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:10:58Z" - latency: 2.188407ms message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:09:58Z" - latency: 2.418194ms message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:08:58Z" - latency: 2.362938ms message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:07:58Z" - latency: 2.104498ms message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:06:58Z" - latency: 2.292632ms message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:05:58Z" - latency: 2.798282ms message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:04:58Z" - latency: 2.358404ms message: 'network-check-target-ip-10-0-136-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:03:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T13:51:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-214-to-network-check-target-ip-10-0-137-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-214.ec2.internal uid: 62d45ac4-7673-42d4-b2d5-c3663d6bd9d3 resourceVersion: "37322" uid: 241ed9c2-3b82-43e1-9328-28b0d8d91ffa spec: sourcePod: network-check-source-dbd9cf844-ns5hn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T13:58:58Z" message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.63µs message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:12:58Z" - latency: 1.005491ms message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:11:58Z" - latency: 1.25655ms message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:10:58Z" - latency: 873.512µs message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:09:58Z" - latency: 1.121894ms message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:08:58Z" - latency: 856.362µs message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:07:58Z" - latency: 844.364µs message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:06:58Z" - latency: 895.706µs message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:05:58Z" - latency: 996.828µs message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:04:58Z" - latency: 888.08µs message: 'network-check-target-ip-10-0-137-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:03:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T13:51:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-214-to-network-check-target-ip-10-0-137-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-214.ec2.internal uid: 62d45ac4-7673-42d4-b2d5-c3663d6bd9d3 resourceVersion: "37323" uid: da39073d-a128-46fe-aadb-7e651b21031c spec: sourcePod: network-check-source-dbd9cf844-ns5hn targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T13:58:58Z" message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.310509ms message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:12:58Z" - latency: 2.535448ms message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:11:58Z" - latency: 2.326533ms message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:10:58Z" - latency: 2.294875ms message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:09:58Z" - latency: 2.501037ms message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:08:58Z" - latency: 2.237596ms message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:07:58Z" - latency: 1.950628ms message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:06:58Z" - latency: 2.398919ms message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:05:58Z" - latency: 1.935689ms message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:04:58Z" - latency: 2.051875ms message: 'network-check-target-ip-10-0-137-34: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:03:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T13:51:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-214-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-214.ec2.internal uid: 62d45ac4-7673-42d4-b2d5-c3663d6bd9d3 resourceVersion: "34866" uid: 071890e9-9917-49fe-9089-91885343b80c spec: sourcePod: network-check-source-dbd9cf844-ns5hn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T13:57:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 758.568µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:09:58Z" - latency: 1.72495ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T14:09:58Z" - latency: 1.137778ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:08:58Z" - latency: 1.808136ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T14:08:58Z" - latency: 813.201µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:07:58Z" - latency: 1.696295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T14:07:58Z" - latency: 979.398µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:06:58Z" - latency: 1.687784ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T14:06:58Z" - latency: 896.886µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T14:05:58Z" - latency: 1.694445ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T14:05:58Z" kind: List metadata: resourceVersion: ""