apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:38:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-12-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-12.ec2.internal uid: 2b4643bd-be4b-4b96-86f0-bb402c338dc2 resourceVersion: "54580" uid: c5e60b2e-6010-47c7-abad-7e5bcca8061e spec: sourcePod: network-check-source-7d88cb55d8-mznsz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T14:45:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.175702ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:13:41Z" - latency: 1.07435ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:12:41Z" - latency: 1.08439ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:11:41Z" - latency: 830.196µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:41Z" - latency: 939.383µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:41Z" - latency: 1.143731ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:41Z" - latency: 1.04509ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:41Z" - latency: 1.06078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:41Z" - latency: 1.053456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:05:41Z" - latency: 919.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:38:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-12-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-12.ec2.internal uid: 2b4643bd-be4b-4b96-86f0-bb402c338dc2 resourceVersion: "55211" uid: 55ec67ba-1dbb-4a50-a891-86f631a2ecb4 spec: sourcePod: network-check-source-7d88cb55d8-mznsz targetEndpoint: a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T14:44:41Z" message: 'load-balancer-api-external: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.463276ms message: 'load-balancer-api-external: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:14:41Z" - latency: 6.988329ms message: 'load-balancer-api-external: resolved host name a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:14:41Z" - latency: 4.409261ms message: 'load-balancer-api-external: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:13:41Z" - latency: 8.235983ms message: 'load-balancer-api-external: resolved host name a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:13:41Z" - latency: 4.137011ms message: 'load-balancer-api-external: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:12:41Z" - latency: 7.469843ms message: 'load-balancer-api-external: resolved host name a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:12:41Z" - latency: 6.34009ms message: 'load-balancer-api-external: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:11:41Z" - latency: 7.132028ms message: 'load-balancer-api-external: resolved host name a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:11:41Z" - latency: 4.910217ms message: 'load-balancer-api-external: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:41Z" - latency: 6.138539ms message: 'load-balancer-api-external: resolved host name a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:10:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:38:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-12-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-12.ec2.internal uid: 2b4643bd-be4b-4b96-86f0-bb402c338dc2 resourceVersion: "55212" uid: 4ce6fb2f-b03e-4842-9c7a-8f9ac2012a9f spec: sourcePod: network-check-source-7d88cb55d8-mznsz targetEndpoint: a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T14:44:41Z" message: 'load-balancer-api-internal: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.490209ms message: 'load-balancer-api-internal: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:14:41Z" - latency: 7.075457ms message: 'load-balancer-api-internal: resolved host name a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:14:41Z" - latency: 5.092521ms message: 'load-balancer-api-internal: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:13:41Z" - latency: 8.345956ms message: 'load-balancer-api-internal: resolved host name a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:13:41Z" - latency: 4.172133ms message: 'load-balancer-api-internal: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:12:41Z" - latency: 7.420857ms message: 'load-balancer-api-internal: resolved host name a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:12:41Z" - latency: 3.933368ms message: 'load-balancer-api-internal: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:11:41Z" - latency: 7.237449ms message: 'load-balancer-api-internal: resolved host name a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:11:41Z" - latency: 6.220535ms message: 'load-balancer-api-internal: tcp connection to a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:41Z" - latency: 6.254879ms message: 'load-balancer-api-internal: resolved host name a217fe49b85b942abaccff571479a173-8ecde4cd0048fa7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:10:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:38:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-12-to-network-check-target-ip-10-0-131-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-12.ec2.internal uid: 2b4643bd-be4b-4b96-86f0-bb402c338dc2 resourceVersion: "54577" uid: 16a41441-a913-4d71-8974-bc3168e5d29c spec: sourcePod: network-check-source-7d88cb55d8-mznsz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T14:45:41Z" message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.693µs message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:13:41Z" - latency: 1.428416ms message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:12:41Z" - latency: 990.065µs message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:11:41Z" - latency: 856.127µs message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:41Z" - latency: 827.006µs message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:41Z" - latency: 891.009µs message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:41Z" - latency: 874.049µs message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:41Z" - latency: 1.205657ms message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:41Z" - latency: 1.020122ms message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:05:41Z" - latency: 932.317µs message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:38:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-12-to-network-check-target-ip-10-0-140-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-12.ec2.internal uid: 2b4643bd-be4b-4b96-86f0-bb402c338dc2 resourceVersion: "54579" uid: d14fecd3-c286-402e-a406-d4c3e9244055 spec: sourcePod: network-check-source-7d88cb55d8-mznsz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T14:45:41Z" message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.811896ms message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:13:41Z" - latency: 1.777976ms message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:12:41Z" - latency: 2.0136ms message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:11:41Z" - latency: 1.594325ms message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:41Z" - latency: 1.913238ms message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:41Z" - latency: 1.996288ms message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:41Z" - latency: 2.045839ms message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:41Z" - latency: 2.178945ms message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:41Z" - latency: 2.034123ms message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:05:41Z" - latency: 1.674379ms message: 'network-check-target-ip-10-0-140-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:38:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-12-to-network-check-target-ip-10-0-141-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-12.ec2.internal uid: 2b4643bd-be4b-4b96-86f0-bb402c338dc2 resourceVersion: "54578" uid: 966f1457-2246-4e48-8e02-19ba4176e892 spec: sourcePod: network-check-source-7d88cb55d8-mznsz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T14:45:41Z" message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.99283ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:13:41Z" - latency: 1.659109ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:12:41Z" - latency: 1.86455ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:11:41Z" - latency: 1.796166ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:41Z" - latency: 1.716156ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:09:41Z" - latency: 2.018493ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:08:41Z" - latency: 2.16035ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:07:41Z" - latency: 2.268476ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:06:41Z" - latency: 1.998627ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:05:41Z" - latency: 2.057632ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T14:38:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-12-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-12.ec2.internal uid: 2b4643bd-be4b-4b96-86f0-bb402c338dc2 resourceVersion: "55210" uid: eaba484a-ff80-4f12-ac17-9b7a92efcbe9 spec: sourcePod: network-check-source-7d88cb55d8-mznsz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T14:44:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 804.199µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:14:41Z" - latency: 1.817953ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:14:41Z" - latency: 1.188727ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:13:41Z" - latency: 1.779719ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:13:41Z" - latency: 896.1µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:12:41Z" - latency: 1.811077ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:12:41Z" - latency: 1.14196ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:11:41Z" - latency: 2.113428ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:11:41Z" - latency: 970.015µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:10:41Z" - latency: 1.559997ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:10:41Z" kind: List metadata: resourceVersion: ""