apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-31T17:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-63-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-63.ec2.internal uid: 9c55cf42-6882-45ad-ac00-0a94f79338c4 resourceVersion: "46027" uid: 83cfdf3a-ff02-4068-8f92-b2e0040878fa spec: sourcePod: network-check-source-56d84b9f44-5q5hq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-31T17:36:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.05933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:57:14Z" - latency: 916.169µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:56:14Z" - latency: 1.156759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:55:14Z" - latency: 1.516596ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:54:14Z" - latency: 1.137548ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:53:14Z" - latency: 1.017925ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:52:14Z" - latency: 1.112757ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:51:14Z" - latency: 1.498879ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:50:14Z" - latency: 1.191518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:49:14Z" - latency: 1.467833ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:48:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-31T17:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-63-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-63.ec2.internal uid: 9c55cf42-6882-45ad-ac00-0a94f79338c4 resourceVersion: "48117" uid: 464546b4-7331-4f8d-9569-29c11ebbc9fc spec: sourcePod: network-check-source-56d84b9f44-5q5hq targetEndpoint: a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-31T17:35:14Z" message: 'load-balancer-api-external: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.467211ms message: 'load-balancer-api-external: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:59:14Z" - latency: 6.962512ms message: 'load-balancer-api-external: resolved host name a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-31T17:59:14Z" - latency: 5.708334ms message: 'load-balancer-api-external: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:58:14Z" - latency: 7.136645ms message: 'load-balancer-api-external: resolved host name a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-31T17:58:14Z" - latency: 4.710463ms message: 'load-balancer-api-external: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:57:14Z" - latency: 7.170028ms message: 'load-balancer-api-external: resolved host name a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-31T17:57:14Z" - latency: 4.640731ms message: 'load-balancer-api-external: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:56:14Z" - latency: 12.728676ms message: 'load-balancer-api-external: resolved host name a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-31T17:56:14Z" - latency: 4.015519ms message: 'load-balancer-api-external: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:55:14Z" - latency: 7.008091ms message: 'load-balancer-api-external: resolved host name a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-31T17:55:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-31T17:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-63-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-63.ec2.internal uid: 9c55cf42-6882-45ad-ac00-0a94f79338c4 resourceVersion: "48118" uid: 5b539030-2236-4f25-ac88-1dea500a0ac9 spec: sourcePod: network-check-source-56d84b9f44-5q5hq targetEndpoint: a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-31T17:35:14Z" message: 'load-balancer-api-internal: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.510987ms message: 'load-balancer-api-internal: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:59:14Z" - latency: 6.912204ms message: 'load-balancer-api-internal: resolved host name a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-31T17:59:14Z" - latency: 5.700432ms message: 'load-balancer-api-internal: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:58:14Z" - latency: 7.049759ms message: 'load-balancer-api-internal: resolved host name a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-31T17:58:14Z" - latency: 4.71279ms message: 'load-balancer-api-internal: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:57:14Z" - latency: 7.261894ms message: 'load-balancer-api-internal: resolved host name a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-31T17:57:14Z" - latency: 3.482496ms message: 'load-balancer-api-internal: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:56:14Z" - latency: 12.774229ms message: 'load-balancer-api-internal: resolved host name a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-31T17:56:14Z" - latency: 4.320611ms message: 'load-balancer-api-internal: tcp connection to a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:55:14Z" - latency: 7.072934ms message: 'load-balancer-api-internal: resolved host name a668889008d1443919bc3b1df83134a3-1744d5d22b4b7c61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-31T17:55:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-31T17:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-63-to-network-check-target-ip-10-0-132-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-63.ec2.internal uid: 9c55cf42-6882-45ad-ac00-0a94f79338c4 resourceVersion: "46026" uid: 7d2dd0fa-c7c7-4666-9bc0-0ccc1aa41213 spec: sourcePod: network-check-source-56d84b9f44-5q5hq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-31T17:36:14Z" message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.375557ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:57:14Z" - latency: 2.239525ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:56:14Z" - latency: 2.194067ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:55:14Z" - latency: 2.891801ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:54:14Z" - latency: 1.917091ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:53:14Z" - latency: 2.228885ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:52:14Z" - latency: 2.42983ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:51:14Z" - latency: 2.900456ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:50:14Z" - latency: 2.390533ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:49:14Z" - latency: 2.323224ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:48:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-31T17:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-63-to-network-check-target-ip-10-0-142-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-63.ec2.internal uid: 9c55cf42-6882-45ad-ac00-0a94f79338c4 resourceVersion: "46024" uid: 2a00efec-f6db-47a8-a8be-7c03786d4632 spec: sourcePod: network-check-source-56d84b9f44-5q5hq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-31T17:36:14Z" message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 963.455µs message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:57:14Z" - latency: 895.528µs message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:56:14Z" - latency: 817.516µs message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:55:14Z" - latency: 970.857µs message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:54:14Z" - latency: 879.373µs message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:53:14Z" - latency: 1.182137ms message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:52:14Z" - latency: 861.088µs message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:51:14Z" - latency: 1.847783ms message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:50:14Z" - latency: 1.001016ms message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:49:14Z" - latency: 1.642438ms message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:48:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-31T17:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-63-to-network-check-target-ip-10-0-143-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-63.ec2.internal uid: 9c55cf42-6882-45ad-ac00-0a94f79338c4 resourceVersion: "46025" uid: 3d5c348a-8a8b-4de9-a08f-439683268be1 spec: sourcePod: network-check-source-56d84b9f44-5q5hq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-31T17:36:14Z" message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.259717ms message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:57:14Z" - latency: 1.690202ms message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:56:14Z" - latency: 2.063221ms message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:55:14Z" - latency: 1.910283ms message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:54:14Z" - latency: 1.870061ms message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:53:14Z" - latency: 1.81657ms message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:52:14Z" - latency: 2.072025ms message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:51:14Z" - latency: 1.809822ms message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:50:14Z" - latency: 1.887604ms message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:49:14Z" - latency: 1.965282ms message: 'network-check-target-ip-10-0-143-182: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:48:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-31T17:29:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-63-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-63.ec2.internal uid: 9c55cf42-6882-45ad-ac00-0a94f79338c4 resourceVersion: "48116" uid: 2c50e879-de31-4127-a376-642e6cb80f8c spec: sourcePod: network-check-source-56d84b9f44-5q5hq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-31T17:35:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.411µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:59:14Z" - latency: 1.783662ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-31T17:59:14Z" - latency: 821.918µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:58:14Z" - latency: 1.973841ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-31T17:58:14Z" - latency: 1.113529ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:57:14Z" - latency: 2.003988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-31T17:57:14Z" - latency: 892.797µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:56:14Z" - latency: 1.745694ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-31T17:56:14Z" - latency: 947.009µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-31T17:55:14Z" - latency: 1.64442ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-31T17:55:14Z" kind: List metadata: resourceVersion: ""