apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-71-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-71.ec2.internal uid: bc5d5e1c-4d0a-430f-a40b-a5cf618402c3 resourceVersion: "47767" uid: 44ab14e3-6c70-40e5-80c9-301667a070fa spec: sourcePod: network-check-source-869dcfcdcd-hp7j6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-12T08:18:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.311032ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:39:13Z" - latency: 920.99µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:38:13Z" - latency: 926.053µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:37:13Z" - latency: 1.571622ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:36:13Z" - latency: 1.062739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:35:13Z" - latency: 1.177312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:34:13Z" - latency: 1.163009ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:33:13Z" - latency: 1.134989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:32:13Z" - latency: 1.309644ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:31:13Z" - latency: 1.494221ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:30:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-71-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-71.ec2.internal uid: bc5d5e1c-4d0a-430f-a40b-a5cf618402c3 resourceVersion: "50601" uid: 9666c014-48e2-4bc9-81ef-4921a853eca4 spec: sourcePod: network-check-source-869dcfcdcd-hp7j6 targetEndpoint: ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T08:17:13Z" message: 'load-balancer-api-external: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.372142ms message: 'load-balancer-api-external: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:41:13Z" - latency: 9.100683ms message: 'load-balancer-api-external: resolved host name ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:41:13Z" - latency: 4.550364ms message: 'load-balancer-api-external: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:40:13Z" - latency: 9.030022ms message: 'load-balancer-api-external: resolved host name ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:40:13Z" - latency: 4.870641ms message: 'load-balancer-api-external: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:39:13Z" - latency: 6.877955ms message: 'load-balancer-api-external: resolved host name ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:39:13Z" - latency: 4.815816ms message: 'load-balancer-api-external: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:38:13Z" - latency: 8.232751ms message: 'load-balancer-api-external: resolved host name ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:38:13Z" - latency: 5.552779ms message: 'load-balancer-api-external: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:37:13Z" - latency: 8.995964ms message: 'load-balancer-api-external: resolved host name ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:37:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-71-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-71.ec2.internal uid: bc5d5e1c-4d0a-430f-a40b-a5cf618402c3 resourceVersion: "50602" uid: 35e972c0-8ea8-42b5-80fe-cb366ec6f5ea spec: sourcePod: network-check-source-869dcfcdcd-hp7j6 targetEndpoint: ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T08:17:13Z" message: 'load-balancer-api-internal: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.749889ms message: 'load-balancer-api-internal: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:41:13Z" - latency: 9.135656ms message: 'load-balancer-api-internal: resolved host name ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:41:13Z" - latency: 4.571127ms message: 'load-balancer-api-internal: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:40:13Z" - latency: 9.04391ms message: 'load-balancer-api-internal: resolved host name ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:40:13Z" - latency: 3.759466ms message: 'load-balancer-api-internal: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:39:13Z" - latency: 6.955784ms message: 'load-balancer-api-internal: resolved host name ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:39:13Z" - latency: 4.888618ms message: 'load-balancer-api-internal: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:38:13Z" - latency: 8.223418ms message: 'load-balancer-api-internal: resolved host name ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:38:13Z" - latency: 6.501449ms message: 'load-balancer-api-internal: tcp connection to ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:37:13Z" - latency: 9.045513ms message: 'load-balancer-api-internal: resolved host name ab174750416f14c2da54632243845639-2b84a2840a1de1dc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T08:37:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-71-to-network-check-target-ip-10-0-128-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-71.ec2.internal uid: bc5d5e1c-4d0a-430f-a40b-a5cf618402c3 resourceVersion: "47766" uid: 40419ebe-7fcd-43b1-a2fd-8931ff08f01e spec: sourcePod: network-check-source-869dcfcdcd-hp7j6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-12T08:18:13Z" message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.632507ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:39:13Z" - latency: 2.364816ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:38:13Z" - latency: 2.454907ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:37:13Z" - latency: 2.181842ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:36:13Z" - latency: 2.439912ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:35:13Z" - latency: 2.389812ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:34:13Z" - latency: 2.295434ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:33:13Z" - latency: 2.511633ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:32:13Z" - latency: 2.316763ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:31:13Z" - latency: 2.725461ms message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:30:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-71-to-network-check-target-ip-10-0-128-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-71.ec2.internal uid: bc5d5e1c-4d0a-430f-a40b-a5cf618402c3 resourceVersion: "47764" uid: 4b4c6317-b369-4f6e-b697-e49a9c05c281 spec: sourcePod: network-check-source-869dcfcdcd-hp7j6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-12T08:18:13Z" message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.007214ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:39:13Z" - latency: 1.341148ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:38:13Z" - latency: 1.115545ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:37:13Z" - latency: 968.372µs message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:36:13Z" - latency: 905.29µs message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:35:13Z" - latency: 1.596143ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:34:13Z" - latency: 915.164µs message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:33:13Z" - latency: 805.221µs message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:32:13Z" - latency: 1.589988ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:31:13Z" - latency: 889.385µs message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:30:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-71-to-network-check-target-ip-10-0-139-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-71.ec2.internal uid: bc5d5e1c-4d0a-430f-a40b-a5cf618402c3 resourceVersion: "47765" uid: ec8aa309-c05e-489f-b799-48878211f3d4 spec: sourcePod: network-check-source-869dcfcdcd-hp7j6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-12T08:18:13Z" message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.103742ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:39:13Z" - latency: 2.123107ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:38:13Z" - latency: 2.349297ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:37:13Z" - latency: 2.214832ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:36:13Z" - latency: 1.989979ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:35:13Z" - latency: 2.362641ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:34:13Z" - latency: 2.664569ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:33:13Z" - latency: 2.243024ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:32:13Z" - latency: 2.325492ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:31:13Z" - latency: 2.256264ms message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:30:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T08:11:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-71-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-71.ec2.internal uid: bc5d5e1c-4d0a-430f-a40b-a5cf618402c3 resourceVersion: "50600" uid: f6073ebd-0ed6-48d7-9131-e948e1705b31 spec: sourcePod: network-check-source-869dcfcdcd-hp7j6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-12T08:17:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.184253ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:41:13Z" - latency: 1.89053ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T08:41:13Z" - latency: 890.892µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:40:13Z" - latency: 1.823524ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T08:40:13Z" - latency: 1.120195ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:39:13Z" - latency: 1.878153ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T08:39:13Z" - latency: 876.372µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:38:13Z" - latency: 2.043754ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T08:38:13Z" - latency: 807.943µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T08:37:13Z" - latency: 1.719955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T08:37:13Z" kind: List metadata: resourceVersion: ""