apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:49:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 84f81e1a-1728-4214-a5d4-4e851bdb90e8 resourceVersion: "69181" uid: e66e4292-b7e0-4a77-96f3-395a610020d8 spec: sourcePod: network-check-source-7d88cb55d8-jq4rd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T19:56:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.066231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:38:46Z" - latency: 1.189708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:37:46Z" - latency: 1.246768ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:36:46Z" - latency: 1.047465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:35:46Z" - latency: 1.236525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:34:46Z" - latency: 1.252534ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:33:46Z" - latency: 1.378139ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:32:46Z" - latency: 962.528µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:31:46Z" - latency: 947.554µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:30:46Z" - latency: 994.492µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:49:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 84f81e1a-1728-4214-a5d4-4e851bdb90e8 resourceVersion: "74209" uid: 57b5c9a7-35eb-4899-a089-e58fd1eeb280 spec: sourcePod: network-check-source-7d88cb55d8-jq4rd targetEndpoint: aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T19:55:46Z" message: 'load-balancer-api-external: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.163092ms message: 'load-balancer-api-external: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:43:46Z" - latency: 9.107229ms message: 'load-balancer-api-external: resolved host name aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:43:46Z" - latency: 7.060952ms message: 'load-balancer-api-external: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:42:46Z" - latency: 8.516832ms message: 'load-balancer-api-external: resolved host name aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:42:46Z" - latency: 5.009736ms message: 'load-balancer-api-external: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:41:46Z" - latency: 11.26532ms message: 'load-balancer-api-external: resolved host name aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:41:46Z" - latency: 5.743408ms message: 'load-balancer-api-external: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:40:46Z" - latency: 7.714216ms message: 'load-balancer-api-external: resolved host name aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:40:46Z" - latency: 5.072485ms message: 'load-balancer-api-external: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:39:46Z" - latency: 10.349609ms message: 'load-balancer-api-external: resolved host name aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:39:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:49:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 84f81e1a-1728-4214-a5d4-4e851bdb90e8 resourceVersion: "74210" uid: 68253122-4222-4253-bd69-e263f70d82fe spec: sourcePod: network-check-source-7d88cb55d8-jq4rd targetEndpoint: aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T19:55:46Z" message: 'load-balancer-api-internal: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.206941ms message: 'load-balancer-api-internal: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:43:46Z" - latency: 9.02251ms message: 'load-balancer-api-internal: resolved host name aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:43:46Z" - latency: 14.504922ms message: 'load-balancer-api-internal: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:42:46Z" - latency: 8.59114ms message: 'load-balancer-api-internal: resolved host name aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:42:46Z" - latency: 5.138596ms message: 'load-balancer-api-internal: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:41:46Z" - latency: 11.232686ms message: 'load-balancer-api-internal: resolved host name aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:41:46Z" - latency: 5.169103ms message: 'load-balancer-api-internal: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:40:46Z" - latency: 7.783222ms message: 'load-balancer-api-internal: resolved host name aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:40:46Z" - latency: 4.831061ms message: 'load-balancer-api-internal: tcp connection to aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:39:46Z" - latency: 10.273101ms message: 'load-balancer-api-internal: resolved host name aa979334b93d940abac5498428a8699d-aaf420da2669882f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:39:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:49:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-network-check-target-ip-10-0-128-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 84f81e1a-1728-4214-a5d4-4e851bdb90e8 resourceVersion: "69180" uid: 03d04378-e096-42c4-9d5c-0524e773b82c spec: sourcePod: network-check-source-7d88cb55d8-jq4rd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T19:56:46Z" message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.943279ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:38:46Z" - latency: 2.816847ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:37:46Z" - latency: 2.592808ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:36:46Z" - latency: 2.659104ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:35:46Z" - latency: 2.714547ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:34:46Z" - latency: 2.750829ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:33:46Z" - latency: 2.689783ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:32:46Z" - latency: 2.639143ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:31:46Z" - latency: 2.571971ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:30:46Z" - latency: 2.573195ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:49:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-network-check-target-ip-10-0-133-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 84f81e1a-1728-4214-a5d4-4e851bdb90e8 resourceVersion: "69178" uid: 87a8d3b1-f74d-48cc-bace-b108b5fc0641 spec: sourcePod: network-check-source-7d88cb55d8-jq4rd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T19:56:46Z" message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.026007ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:38:46Z" - latency: 1.455513ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:37:46Z" - latency: 944.102µs message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:36:46Z" - latency: 997.134µs message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:35:46Z" - latency: 1.069972ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:34:46Z" - latency: 1.052699ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:33:46Z" - latency: 1.45482ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:32:46Z" - latency: 1.033795ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:31:46Z" - latency: 1.276331ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:30:46Z" - latency: 1.075863ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:49:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-network-check-target-ip-10-0-134-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 84f81e1a-1728-4214-a5d4-4e851bdb90e8 resourceVersion: "69179" uid: 52a12e80-5ee3-4468-8560-c94caa21d45f spec: sourcePod: network-check-source-7d88cb55d8-jq4rd targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T19:56:46Z" message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.436592ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:38:46Z" - latency: 2.378606ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:37:46Z" - latency: 2.218172ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:36:46Z" - latency: 2.297987ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:35:46Z" - latency: 2.135506ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:34:46Z" - latency: 2.274417ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:33:46Z" - latency: 2.28323ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:32:46Z" - latency: 2.256206ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:31:46Z" - latency: 2.116791ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:30:46Z" - latency: 2.187881ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:49:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 84f81e1a-1728-4214-a5d4-4e851bdb90e8 resourceVersion: "74208" uid: 2767d25e-6fc1-4764-ab6c-9822bb2cdcce spec: sourcePod: network-check-source-7d88cb55d8-jq4rd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T19:55:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 798.323µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:43:46Z" - latency: 1.849823ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:43:46Z" - latency: 887.32µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:42:46Z" - latency: 2.387947ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:42:46Z" - latency: 893.985µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:41:46Z" - latency: 2.148808ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:41:46Z" - latency: 958.714µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:40:46Z" - latency: 1.853963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:40:46Z" - latency: 933.891µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:39:46Z" - latency: 2.024593ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:39:46Z" kind: List metadata: resourceVersion: ""