apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:10:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 3e8ad4ea-7141-4341-9836-1416121d952a resourceVersion: "41039" uid: 3d3eb4c6-6289-4303-98d2-dd0cf253554f spec: sourcePod: network-check-source-7f44b6dd87-wkp7s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-29T10:17: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.738412ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:58Z" - latency: 896.431µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:58Z" - latency: 1.07131ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:58Z" - latency: 1.178183ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:58Z" - latency: 1.04695ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:58Z" - latency: 1.249206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:58Z" - latency: 1.516165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:58Z" - latency: 1.298079ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:58Z" - latency: 1.05328ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:58Z" - latency: 1.21911ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:10:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 3e8ad4ea-7141-4341-9836-1416121d952a resourceVersion: "43130" uid: d7d192c4-ad05-4fa3-bb0b-1b36aa4ca9b4 spec: sourcePod: network-check-source-7f44b6dd87-wkp7s targetEndpoint: abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T10:16:58Z" message: 'load-balancer-api-external: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.102636ms message: 'load-balancer-api-external: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:40:58Z" - latency: 7.340621ms message: 'load-balancer-api-external: resolved host name abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:40:58Z" - latency: 5.346081ms message: 'load-balancer-api-external: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:39:58Z" - latency: 8.736056ms message: 'load-balancer-api-external: resolved host name abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:39:58Z" - latency: 3.734112ms message: 'load-balancer-api-external: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:58Z" - latency: 7.649073ms message: 'load-balancer-api-external: resolved host name abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:38:58Z" - latency: 5.468313ms message: 'load-balancer-api-external: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:58Z" - latency: 8.16808ms message: 'load-balancer-api-external: resolved host name abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:37:58Z" - latency: 4.212062ms message: 'load-balancer-api-external: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:58Z" - latency: 8.347458ms message: 'load-balancer-api-external: resolved host name abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:36:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:10:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 3e8ad4ea-7141-4341-9836-1416121d952a resourceVersion: "43131" uid: 586bff75-1b8e-4d4b-aab4-e5281e304289 spec: sourcePod: network-check-source-7f44b6dd87-wkp7s targetEndpoint: abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T10:16:58Z" message: 'load-balancer-api-internal: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.131689ms message: 'load-balancer-api-internal: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:40:58Z" - latency: 7.254362ms message: 'load-balancer-api-internal: resolved host name abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:40:58Z" - latency: 5.196798ms message: 'load-balancer-api-internal: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:39:58Z" - latency: 8.683238ms message: 'load-balancer-api-internal: resolved host name abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:39:58Z" - latency: 5.596701ms message: 'load-balancer-api-internal: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:58Z" - latency: 7.716238ms message: 'load-balancer-api-internal: resolved host name abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:38:58Z" - latency: 4.997714ms message: 'load-balancer-api-internal: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:58Z" - latency: 8.10799ms message: 'load-balancer-api-internal: resolved host name abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:37:58Z" - latency: 5.53952ms message: 'load-balancer-api-internal: tcp connection to abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:58Z" - latency: 8.245068ms message: 'load-balancer-api-internal: resolved host name abccda9d45bfa43cb81a31efaf61f6a9-b97244e31a1ea5a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:36:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:10:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-network-check-target-ip-10-0-132-42 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 3e8ad4ea-7141-4341-9836-1416121d952a resourceVersion: "41037" uid: 024395b7-a547-4ae2-a6ef-54d8e97148ab spec: sourcePod: network-check-source-7f44b6dd87-wkp7s targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-29T10:17:58Z" message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.07401ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:58Z" - latency: 1.791614ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:58Z" - latency: 1.787715ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:58Z" - latency: 1.988913ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:58Z" - latency: 2.386276ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:58Z" - latency: 2.10486ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:58Z" - latency: 2.382165ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:58Z" - latency: 2.085537ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:58Z" - latency: 2.053205ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:58Z" - latency: 2.034203ms message: 'network-check-target-ip-10-0-132-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:10:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-network-check-target-ip-10-0-136-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 3e8ad4ea-7141-4341-9836-1416121d952a resourceVersion: "41038" uid: 041f3cd2-e53f-4253-abcd-08707af1bd82 spec: sourcePod: network-check-source-7f44b6dd87-wkp7s targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T10:17:58Z" message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.00592ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:58Z" - latency: 1.730933ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:58Z" - latency: 1.883286ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:58Z" - latency: 1.936108ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:58Z" - latency: 2.035334ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:58Z" - latency: 2.053711ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:58Z" - latency: 2.11548ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:58Z" - latency: 1.667598ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:58Z" - latency: 1.98861ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:58Z" - latency: 1.860432ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:10:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-network-check-target-ip-10-0-139-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 3e8ad4ea-7141-4341-9836-1416121d952a resourceVersion: "41036" uid: 7bb410a5-e755-4ae3-b404-910c17efc2b1 spec: sourcePod: network-check-source-7f44b6dd87-wkp7s targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T10:17:58Z" message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 735.742µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:58Z" - latency: 810.475µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:58Z" - latency: 1.509109ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:58Z" - latency: 852.791µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:58Z" - latency: 820.945µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:58Z" - latency: 1.337842ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:58Z" - latency: 801.477µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:58Z" - latency: 862.446µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:58Z" - latency: 912.33µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:58Z" - latency: 1.238974ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:10:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 3e8ad4ea-7141-4341-9836-1416121d952a resourceVersion: "43125" uid: 95c6aa02-d2fd-4d30-acdc-847651e208fa spec: sourcePod: network-check-source-7f44b6dd87-wkp7s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-29T10:16:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 765.385µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:40:58Z" - latency: 1.629252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:40:58Z" - latency: 933.701µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:39:58Z" - latency: 2.012714ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:39:58Z" - latency: 792.938µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:58Z" - latency: 1.703252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:38:58Z" - latency: 758.242µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:58Z" - latency: 1.726173ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:37:58Z" - latency: 767.059µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:58Z" - latency: 1.702924ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:36:58Z" kind: List metadata: resourceVersion: ""