apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T15:59:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-127-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-127.ec2.internal uid: 40703e20-7f2b-46ac-8607-b9d13ce63047 resourceVersion: "49551" uid: 4375cc86-4df2-42c8-8ff3-1223d9ade384 spec: sourcePod: network-check-source-869dcfcdcd-mjg46 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T16:06:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.156µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:34:31Z" - latency: 914.666µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:33:31Z" - latency: 942.97µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:32:31Z" - latency: 944.881µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:31:31Z" - latency: 977.066µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:30:31Z" - latency: 1.264833ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:29:31Z" - latency: 834.448µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:28:31Z" - latency: 968.652µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:27:31Z" - latency: 881.077µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:26:31Z" - latency: 1.003466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:25:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T15:59:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-127-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-127.ec2.internal uid: 40703e20-7f2b-46ac-8607-b9d13ce63047 resourceVersion: "50628" uid: 5095530c-e004-4a7d-ae32-fa249771f8b1 spec: sourcePod: network-check-source-869dcfcdcd-mjg46 targetEndpoint: a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T16:05:31Z" message: 'load-balancer-api-external: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.775601ms message: 'load-balancer-api-external: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:35:31Z" - latency: 5.816298ms message: 'load-balancer-api-external: resolved host name a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T16:35:31Z" - latency: 5.90541ms message: 'load-balancer-api-external: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:34:31Z" - latency: 7.077344ms message: 'load-balancer-api-external: resolved host name a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T16:34:31Z" - latency: 3.771675ms message: 'load-balancer-api-external: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:33:31Z" - latency: 6.695911ms message: 'load-balancer-api-external: resolved host name a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T16:33:31Z" - latency: 4.605207ms message: 'load-balancer-api-external: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:32:31Z" - latency: 8.433708ms message: 'load-balancer-api-external: resolved host name a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T16:32:31Z" - latency: 4.77899ms message: 'load-balancer-api-external: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:31:31Z" - latency: 7.480001ms message: 'load-balancer-api-external: resolved host name a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T16:31:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T15:59:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-127-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-127.ec2.internal uid: 40703e20-7f2b-46ac-8607-b9d13ce63047 resourceVersion: "50629" uid: b8f52b10-836e-49dc-9991-27820b0e47ce spec: sourcePod: network-check-source-869dcfcdcd-mjg46 targetEndpoint: a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T16:05:31Z" message: 'load-balancer-api-internal: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.238566ms message: 'load-balancer-api-internal: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:35:31Z" - latency: 5.864382ms message: 'load-balancer-api-internal: resolved host name a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T16:35:31Z" - latency: 5.911449ms message: 'load-balancer-api-internal: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:34:31Z" - latency: 7.166225ms message: 'load-balancer-api-internal: resolved host name a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T16:34:31Z" - latency: 4.16008ms message: 'load-balancer-api-internal: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:33:31Z" - latency: 6.753712ms message: 'load-balancer-api-internal: resolved host name a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T16:33:31Z" - latency: 4.572092ms message: 'load-balancer-api-internal: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:32:31Z" - latency: 8.518386ms message: 'load-balancer-api-internal: resolved host name a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T16:32:31Z" - latency: 4.731431ms message: 'load-balancer-api-internal: tcp connection to a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:31:31Z" - latency: 7.504371ms message: 'load-balancer-api-internal: resolved host name a27a73d279699400c9a144893d103c2a-98713f9be102b809.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T16:31:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T15:59:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-127-to-network-check-target-ip-10-0-129-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-127.ec2.internal uid: 40703e20-7f2b-46ac-8607-b9d13ce63047 resourceVersion: "49549" uid: 0dad6dee-a5aa-43a4-8dbe-9d858671c8db spec: sourcePod: network-check-source-869dcfcdcd-mjg46 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T16:06:31Z" message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.241547ms message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:34:31Z" - latency: 2.283868ms message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:33:31Z" - latency: 2.204491ms message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:32:31Z" - latency: 2.415392ms message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:31:31Z" - latency: 2.202813ms message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:30:31Z" - latency: 2.650891ms message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:29:31Z" - latency: 2.075642ms message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:28:31Z" - latency: 2.400251ms message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:27:31Z" - latency: 2.187738ms message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:26:31Z" - latency: 2.470001ms message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:25:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T15:59:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-127-to-network-check-target-ip-10-0-135-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-127.ec2.internal uid: 40703e20-7f2b-46ac-8607-b9d13ce63047 resourceVersion: "49550" uid: 74aa7335-21a5-4918-a231-ef5cc4514003 spec: sourcePod: network-check-source-869dcfcdcd-mjg46 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T16:06:31Z" message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.192603ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:34:31Z" - latency: 2.228901ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:33:31Z" - latency: 2.260335ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:32:31Z" - latency: 2.03932ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:31:31Z" - latency: 2.217248ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:30:31Z" - latency: 2.428242ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:29:31Z" - latency: 1.917537ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:28:31Z" - latency: 2.203504ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:27:31Z" - latency: 2.154768ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:26:31Z" - latency: 2.061688ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:25:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T15:59:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-127-to-network-check-target-ip-10-0-138-127 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-127.ec2.internal uid: 40703e20-7f2b-46ac-8607-b9d13ce63047 resourceVersion: "49548" uid: 0488eec8-ca6f-442d-b930-022226b9b494 spec: sourcePod: network-check-source-869dcfcdcd-mjg46 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T16:06:31Z" message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.048175ms message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:34:31Z" - latency: 920.739µs message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:33:31Z" - latency: 967.214µs message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:32:31Z" - latency: 828.817µs message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:31:31Z" - latency: 957.308µs message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:30:31Z" - latency: 875.233µs message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:29:31Z" - latency: 928.364µs message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:28:31Z" - latency: 1.530113ms message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:27:31Z" - latency: 1.447679ms message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:26:31Z" - latency: 1.347753ms message: 'network-check-target-ip-10-0-138-127: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:25:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T15:59:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-127-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-127.ec2.internal uid: 40703e20-7f2b-46ac-8607-b9d13ce63047 resourceVersion: "50627" uid: 91041a01-615d-45cd-83d7-65acaebb5756 spec: sourcePod: network-check-source-869dcfcdcd-mjg46 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T16:05:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.00234ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:35:31Z" - latency: 1.714818ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T16:35:31Z" - latency: 1.080212ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:34:31Z" - latency: 1.927062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T16:34:31Z" - latency: 1.117207ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:33:31Z" - latency: 1.786393ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T16:33:31Z" - latency: 894.548µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:32:31Z" - latency: 1.8854ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T16:32:31Z" - latency: 956.985µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T16:31:31Z" - latency: 1.741938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T16:31:31Z" kind: List metadata: resourceVersion: ""