apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:32:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-235-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-235.ec2.internal uid: 7e98904b-6652-4cff-bd7b-68e0549d7998 resourceVersion: "32017" uid: 3418230c-9514-4c03-9178-b74e5d0c5f97 spec: sourcePod: network-check-source-7d88cb55d8-bg78h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T17:39:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.096396ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:14:17Z" - latency: 1.254697ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:13:17Z" - latency: 1.321196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:17Z" - latency: 792.413µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:17Z" - latency: 845.72µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:17Z" - latency: 1.048072ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:09:17Z" - latency: 994.824µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:08:17Z" - latency: 1.408249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:07:17Z" - latency: 1.388854ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:06:17Z" - latency: 1.169881ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:05:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:32:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-235-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-235.ec2.internal uid: 7e98904b-6652-4cff-bd7b-68e0549d7998 resourceVersion: "32018" uid: 49887c45-5d70-4f8a-a6a0-2a0b4c64eb8f spec: sourcePod: network-check-source-7d88cb55d8-bg78h targetEndpoint: a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:38:17Z" message: 'load-balancer-api-external: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.203672ms message: 'load-balancer-api-external: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:14:17Z" - latency: 9.203005ms message: 'load-balancer-api-external: resolved host name a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:14:17Z" - latency: 16.432546ms message: 'load-balancer-api-external: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:13:17Z" - latency: 8.621099ms message: 'load-balancer-api-external: resolved host name a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:13:17Z" - latency: 6.247163ms message: 'load-balancer-api-external: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:17Z" - latency: 9.226534ms message: 'load-balancer-api-external: resolved host name a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:12:17Z" - latency: 5.564515ms message: 'load-balancer-api-external: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:17Z" - latency: 9.15849ms message: 'load-balancer-api-external: resolved host name a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:11:17Z" - latency: 6.331482ms message: 'load-balancer-api-external: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:17Z" - latency: 8.611551ms message: 'load-balancer-api-external: resolved host name a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:10:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:32:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-235-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-235.ec2.internal uid: 7e98904b-6652-4cff-bd7b-68e0549d7998 resourceVersion: "32019" uid: dcf18fb8-e56c-42db-bf65-d7b4d1c544ac spec: sourcePod: network-check-source-7d88cb55d8-bg78h targetEndpoint: a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:38:17Z" message: 'load-balancer-api-internal: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.240836ms message: 'load-balancer-api-internal: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:14:17Z" - latency: 9.239058ms message: 'load-balancer-api-internal: resolved host name a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:14:17Z" - latency: 16.433495ms message: 'load-balancer-api-internal: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:13:17Z" - latency: 8.692066ms message: 'load-balancer-api-internal: resolved host name a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:13:17Z" - latency: 5.286658ms message: 'load-balancer-api-internal: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:17Z" - latency: 9.26113ms message: 'load-balancer-api-internal: resolved host name a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:12:17Z" - latency: 5.611183ms message: 'load-balancer-api-internal: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:17Z" - latency: 9.103227ms message: 'load-balancer-api-internal: resolved host name a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:11:17Z" - latency: 6.303231ms message: 'load-balancer-api-internal: tcp connection to a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:17Z" - latency: 8.550404ms message: 'load-balancer-api-internal: resolved host name a9f9d5130118c48b493262f2d0fb0cd0-67ed39f33209230c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T18:10:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:32:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-235-to-network-check-target-ip-10-0-131-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-235.ec2.internal uid: 7e98904b-6652-4cff-bd7b-68e0549d7998 resourceVersion: "32014" uid: 922fa710-257e-48aa-8146-d6052ac8349b spec: sourcePod: network-check-source-7d88cb55d8-bg78h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:39:17Z" message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.785458ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:14:17Z" - latency: 1.831792ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:13:17Z" - latency: 1.914358ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:17Z" - latency: 1.885659ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:17Z" - latency: 1.879091ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:17Z" - latency: 1.762354ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:09:17Z" - latency: 1.94541ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:08:17Z" - latency: 2.711573ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:07:17Z" - latency: 1.963308ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:06:17Z" - latency: 2.055192ms message: 'network-check-target-ip-10-0-131-71: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:05:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:32:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-235-to-network-check-target-ip-10-0-132-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-235.ec2.internal uid: 7e98904b-6652-4cff-bd7b-68e0549d7998 resourceVersion: "32013" uid: cca17e0a-7f52-4233-a37f-824b37457b2c spec: sourcePod: network-check-source-7d88cb55d8-bg78h targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:39:17Z" message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 936.139µs message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:14:17Z" - latency: 980.117µs message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:13:17Z" - latency: 1.023736ms message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:17Z" - latency: 1.137413ms message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:17Z" - latency: 1.111228ms message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:17Z" - latency: 996.132µs message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:09:17Z" - latency: 1.176503ms message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:08:17Z" - latency: 848.253µs message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:07:17Z" - latency: 865.896µs message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:06:17Z" - latency: 873.421µs message: 'network-check-target-ip-10-0-132-235: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:05:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:32:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-235-to-network-check-target-ip-10-0-140-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-235.ec2.internal uid: 7e98904b-6652-4cff-bd7b-68e0549d7998 resourceVersion: "32016" uid: 0f12f00e-fde8-48ce-9cc7-4b0c3676a280 spec: sourcePod: network-check-source-7d88cb55d8-bg78h targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:39:17Z" message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.077163ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:14:17Z" - latency: 2.076195ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:13:17Z" - latency: 2.394947ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:17Z" - latency: 2.110449ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:17Z" - latency: 2.148455ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:17Z" - latency: 2.004214ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:09:17Z" - latency: 2.068304ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:08:17Z" - latency: 2.486207ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:07:17Z" - latency: 2.157772ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:06:17Z" - latency: 2.086377ms message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:05:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:32:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-235-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-235.ec2.internal uid: 7e98904b-6652-4cff-bd7b-68e0549d7998 resourceVersion: "32015" uid: 35bf44ee-8b97-490c-a806-15e0d005ce9e spec: sourcePod: network-check-source-7d88cb55d8-bg78h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T17:38:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 924.176µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:14:17Z" - latency: 1.871899ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:14:17Z" - latency: 863.976µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:13:17Z" - latency: 2.059385ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:13:17Z" - latency: 1.047828ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:12:17Z" - latency: 2.507078ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:12:17Z" - latency: 870.014µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:11:17Z" - latency: 1.911523ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:11:17Z" - latency: 938.468µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T18:10:17Z" - latency: 1.848689ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T18:10:17Z" kind: List metadata: resourceVersion: ""