apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:24:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-138-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-138.ec2.internal uid: 1e03bbe4-9c9c-48cd-ab5a-6655478db5d3 resourceVersion: "46649" uid: 6d3a0adb-d3c3-47e7-b60c-bb8f289ae937 spec: sourcePod: network-check-source-869dcfcdcd-b9fxd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-12T08:31:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.185448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:52:45Z" - latency: 1.164647ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:51:45Z" - latency: 922.401µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:50:45Z" - latency: 1.574809ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:49:45Z" - latency: 962.694µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:48:45Z" - latency: 1.401483ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:47:45Z" - latency: 1.332832ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:46:45Z" - latency: 1.730938ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:45:45Z" - latency: 914.918µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:44:45Z" - latency: 1.072725ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:43:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:24:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-138-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-138.ec2.internal uid: 1e03bbe4-9c9c-48cd-ab5a-6655478db5d3 resourceVersion: "49051" uid: 7d65f03a-3a1e-4c0f-a8b5-06112b2182f5 spec: sourcePod: network-check-source-869dcfcdcd-b9fxd targetEndpoint: abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T08:30:45Z" message: 'load-balancer-api-external: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.767989ms message: 'load-balancer-api-external: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:54:45Z" - latency: 6.637523ms message: 'load-balancer-api-external: resolved host name abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:54:45Z" - latency: 4.869707ms message: 'load-balancer-api-external: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:53:45Z" - latency: 7.431021ms message: 'load-balancer-api-external: resolved host name abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:53:45Z" - latency: 4.856272ms message: 'load-balancer-api-external: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:52:45Z" - latency: 6.875038ms message: 'load-balancer-api-external: resolved host name abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:52:45Z" - latency: 4.947036ms message: 'load-balancer-api-external: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:51:45Z" - latency: 7.607455ms message: 'load-balancer-api-external: resolved host name abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:51:45Z" - latency: 4.089971ms message: 'load-balancer-api-external: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:50:45Z" - latency: 6.803898ms message: 'load-balancer-api-external: resolved host name abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:50:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:24:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-138-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-138.ec2.internal uid: 1e03bbe4-9c9c-48cd-ab5a-6655478db5d3 resourceVersion: "49050" uid: 559e9d1e-65ba-40fe-9a39-10a56eab4ded spec: sourcePod: network-check-source-869dcfcdcd-b9fxd targetEndpoint: abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T08:30:45Z" message: 'load-balancer-api-internal: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.783245ms message: 'load-balancer-api-internal: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:54:45Z" - latency: 6.578926ms message: 'load-balancer-api-internal: resolved host name abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:54:45Z" - latency: 4.860956ms message: 'load-balancer-api-internal: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:53:45Z" - latency: 7.466199ms message: 'load-balancer-api-internal: resolved host name abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:53:45Z" - latency: 4.77591ms message: 'load-balancer-api-internal: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:52:45Z" - latency: 6.822859ms message: 'load-balancer-api-internal: resolved host name abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:52:45Z" - latency: 4.181852ms message: 'load-balancer-api-internal: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:51:45Z" - latency: 7.546526ms message: 'load-balancer-api-internal: resolved host name abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:51:45Z" - latency: 4.105833ms message: 'load-balancer-api-internal: tcp connection to abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:50:45Z" - latency: 6.909885ms message: 'load-balancer-api-internal: resolved host name abff49f317b704d2b917142b8e55b340-b0ec89f5d2e08c3f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:50:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:24:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-138-to-network-check-target-ip-10-0-131-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-138.ec2.internal uid: 1e03bbe4-9c9c-48cd-ab5a-6655478db5d3 resourceVersion: "46647" uid: adf0d1cc-3929-4a05-aec0-442d34dbceec spec: sourcePod: network-check-source-869dcfcdcd-b9fxd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-12T08:31:45Z" message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.047536ms message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:52:45Z" - latency: 1.919426ms message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:51:45Z" - latency: 1.893878ms message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:50:45Z" - latency: 1.94945ms message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:49:45Z" - latency: 2.025942ms message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:48:45Z" - latency: 2.23106ms message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:47:45Z" - latency: 1.874085ms message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:46:45Z" - latency: 2.053847ms message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:45:45Z" - latency: 2.035188ms message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:44:45Z" - latency: 2.342087ms message: 'network-check-target-ip-10-0-131-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:43:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:24:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-138-to-network-check-target-ip-10-0-136-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-138.ec2.internal uid: 1e03bbe4-9c9c-48cd-ab5a-6655478db5d3 resourceVersion: "46646" uid: c0b8870e-660e-432c-a039-68ac3fb3a494 spec: sourcePod: network-check-source-869dcfcdcd-b9fxd targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-12T08:31:45Z" message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.30794ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:52:45Z" - latency: 960.56µs message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:51:45Z" - latency: 858.453µs message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:50:45Z" - latency: 1.620128ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:49:45Z" - latency: 753.314µs message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:48:45Z" - latency: 793.608µs message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:47:45Z" - latency: 908.223µs message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:46:45Z" - latency: 900.163µs message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:45:45Z" - latency: 984.44µs message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:44:45Z" - latency: 884.28µs message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:43:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:24:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-138-to-network-check-target-ip-10-0-136-78 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-138.ec2.internal uid: 1e03bbe4-9c9c-48cd-ab5a-6655478db5d3 resourceVersion: "46648" uid: c93bd31c-a1cf-4cfa-b371-2754e269ffbb spec: sourcePod: network-check-source-869dcfcdcd-b9fxd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-12T08:31:45Z" message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.348717ms message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:52:45Z" - latency: 2.00233ms message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:51:45Z" - latency: 2.352922ms message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:50:45Z" - latency: 2.538342ms message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:49:45Z" - latency: 2.225617ms message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:48:45Z" - latency: 2.155699ms message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:47:45Z" - latency: 2.227526ms message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:46:45Z" - latency: 2.227773ms message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:45:45Z" - latency: 2.300618ms message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:44:45Z" - latency: 2.115597ms message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:43:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:24:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-138-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-138.ec2.internal uid: 1e03bbe4-9c9c-48cd-ab5a-6655478db5d3 resourceVersion: "49049" uid: 6b45ea28-46b4-4000-94ac-7a60042aee73 spec: sourcePod: network-check-source-869dcfcdcd-b9fxd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-12T08:30:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.049152ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:54:45Z" - latency: 1.836898ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T08:54:45Z" - latency: 1.106219ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:53:45Z" - latency: 1.926005ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T08:53:45Z" - latency: 1.040076ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:52:45Z" - latency: 1.692051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T08:52:45Z" - latency: 1.169799ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:51:45Z" - latency: 1.934098ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T08:51:45Z" - latency: 934.802µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:50:45Z" - latency: 1.785861ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T08:50:45Z" kind: List metadata: resourceVersion: ""