apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:25:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-57-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-57.ec2.internal uid: 22821eea-9de9-4640-9074-9ff4c46eec77 resourceVersion: "25050" uid: 25ed0141-07f8-47ae-a0fe-a9b685b11cf0 spec: sourcePod: network-check-source-7cbc45fddc-b8qvp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-18T16:32:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.866µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:46:33Z" - latency: 937.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:45:33Z" - latency: 736.263µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:44:33Z" - latency: 966.075µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:43:33Z" - latency: 646.966µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:42:33Z" - latency: 740.695µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:41:33Z" - latency: 1.312876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:40:33Z" - latency: 732.793µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:39:33Z" - latency: 954.258µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:38:33Z" - latency: 910.705µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:37:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:25:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-57-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-57.ec2.internal uid: 22821eea-9de9-4640-9074-9ff4c46eec77 resourceVersion: "26478" uid: a4866938-54aa-4305-ba18-9d2ea990de8c spec: sourcePod: network-check-source-7cbc45fddc-b8qvp targetEndpoint: a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T16:31:33Z" message: 'load-balancer-api-external: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.365411ms message: 'load-balancer-api-external: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:49:33Z" - latency: 8.754987ms message: 'load-balancer-api-external: resolved host name a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:49:33Z" - latency: 6.038719ms message: 'load-balancer-api-external: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:48:33Z" - latency: 8.954902ms message: 'load-balancer-api-external: resolved host name a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:48:33Z" - latency: 4.643025ms message: 'load-balancer-api-external: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:47:33Z" - latency: 8.017808ms message: 'load-balancer-api-external: resolved host name a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:47:33Z" - latency: 4.761386ms message: 'load-balancer-api-external: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:46:33Z" - latency: 9.132794ms message: 'load-balancer-api-external: resolved host name a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:46:33Z" - latency: 6.628037ms message: 'load-balancer-api-external: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:45:33Z" - latency: 9.011011ms message: 'load-balancer-api-external: resolved host name a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:45:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:25:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-57-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-57.ec2.internal uid: 22821eea-9de9-4640-9074-9ff4c46eec77 resourceVersion: "26477" uid: 634cd8f7-f898-41e4-b7f5-e747eeea0ece spec: sourcePod: network-check-source-7cbc45fddc-b8qvp targetEndpoint: a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T16:31:33Z" message: 'load-balancer-api-internal: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.658055ms message: 'load-balancer-api-internal: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:49:33Z" - latency: 8.60224ms message: 'load-balancer-api-internal: resolved host name a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:49:33Z" - latency: 6.190255ms message: 'load-balancer-api-internal: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:48:33Z" - latency: 9.008103ms message: 'load-balancer-api-internal: resolved host name a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:48:33Z" - latency: 4.651911ms message: 'load-balancer-api-internal: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:47:33Z" - latency: 8.047523ms message: 'load-balancer-api-internal: resolved host name a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:47:33Z" - latency: 6.062411ms message: 'load-balancer-api-internal: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:46:33Z" - latency: 9.105938ms message: 'load-balancer-api-internal: resolved host name a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:46:33Z" - latency: 4.815085ms message: 'load-balancer-api-internal: tcp connection to a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:45:33Z" - latency: 8.971947ms message: 'load-balancer-api-internal: resolved host name a00087c056dc648c8a3505a60a229e45-7180a410eb648cc1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T16:45:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:25:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-57-to-network-check-target-ip-10-0-136-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-57.ec2.internal uid: 22821eea-9de9-4640-9074-9ff4c46eec77 resourceVersion: "25048" uid: 24c57c7b-f92f-4432-86b0-f2afa8dbc9e2 spec: sourcePod: network-check-source-7cbc45fddc-b8qvp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-18T16:32:33Z" message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.021236ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:46:33Z" - latency: 2.289885ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:45:33Z" - latency: 1.64167ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:44:33Z" - latency: 3.493428ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:43:33Z" - latency: 2.188235ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:42:33Z" - latency: 2.060343ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:41:33Z" - latency: 1.872198ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:40:33Z" - latency: 1.971202ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:39:33Z" - latency: 2.084368ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:38:33Z" - latency: 2.236894ms message: 'network-check-target-ip-10-0-136-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:37:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:25:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-57-to-network-check-target-ip-10-0-138-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-57.ec2.internal uid: 22821eea-9de9-4640-9074-9ff4c46eec77 resourceVersion: "25049" uid: 3cb3e873-8830-4190-b574-5fd5543ee71f spec: sourcePod: network-check-source-7cbc45fddc-b8qvp targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-18T16:32:33Z" message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.284832ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:46:33Z" - latency: 1.89731ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:45:33Z" - latency: 1.665504ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:44:33Z" - latency: 2.92873ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:43:33Z" - latency: 1.976453ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:42:33Z" - latency: 1.935912ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:41:33Z" - latency: 1.923399ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:40:33Z" - latency: 1.850695ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:39:33Z" - latency: 2.447255ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:38:33Z" - latency: 1.791138ms message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:37:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:25:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-57-to-network-check-target-ip-10-0-139-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-57.ec2.internal uid: 22821eea-9de9-4640-9074-9ff4c46eec77 resourceVersion: "25047" uid: 0fbb8a94-b892-4d5c-b817-98c64be65020 spec: sourcePod: network-check-source-7cbc45fddc-b8qvp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-18T16:32:33Z" message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 723.504µs message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:46:33Z" - latency: 1.107846ms message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:45:33Z" - latency: 666.168µs message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:44:33Z" - latency: 1.172425ms message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:43:33Z" - latency: 830.165µs message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:42:33Z" - latency: 990.825µs message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:41:33Z" - latency: 665.366µs message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:40:33Z" - latency: 729.064µs message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:39:33Z" - latency: 861.571µs message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:38:33Z" - latency: 720.164µs message: 'network-check-target-ip-10-0-139-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:37:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T16:25:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-57-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-57.ec2.internal uid: 22821eea-9de9-4640-9074-9ff4c46eec77 resourceVersion: "26476" uid: 7b052aaa-ff45-4f80-bcfe-a098e8038115 spec: sourcePod: network-check-source-7cbc45fddc-b8qvp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-18T16:31:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.154003ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:49:33Z" - latency: 1.732096ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T16:49:33Z" - latency: 963.86µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:48:33Z" - latency: 1.992412ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T16:48:33Z" - latency: 792.392µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:47:33Z" - latency: 1.734059ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T16:47:33Z" - latency: 827.806µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:46:33Z" - latency: 2.343912ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T16:46:33Z" - latency: 954.062µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T16:45:33Z" - latency: 1.770564ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T16:45:33Z" kind: List metadata: resourceVersion: ""