apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:51:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-192-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-192.ec2.internal uid: 5a06319d-349f-4e09-b7d2-ceaef9e3a940 resourceVersion: "38799" uid: 679dfc26-5846-4ea1-a0d4-aa882f92d123 spec: sourcePod: network-check-source-65bdbbff45-88r5l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-31T14:58:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.307585ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:40:43Z" - latency: 1.06114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:39:43Z" - latency: 1.167827ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:38:43Z" - latency: 1.172221ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:37:43Z" - latency: 1.37058ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:36:43Z" - latency: 929.683µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:35:43Z" - latency: 916.441µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:34:43Z" - latency: 1.574446ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:33:43Z" - latency: 1.042406ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:32:43Z" - latency: 947.49µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:31:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:51:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-192-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-192.ec2.internal uid: 5a06319d-349f-4e09-b7d2-ceaef9e3a940 resourceVersion: "38275" uid: 60317562-e1e7-418e-a530-65687e889630 spec: sourcePod: network-check-source-65bdbbff45-88r5l targetEndpoint: a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T14:57:43Z" message: 'load-balancer-api-external: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.083711ms message: 'load-balancer-api-external: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:39:43Z" - latency: 6.717543ms message: 'load-balancer-api-external: resolved host name a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:39:43Z" - latency: 5.245085ms message: 'load-balancer-api-external: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:38:43Z" - latency: 6.256572ms message: 'load-balancer-api-external: resolved host name a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:38:43Z" - latency: 3.24266ms message: 'load-balancer-api-external: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:37:43Z" - latency: 7.327282ms message: 'load-balancer-api-external: resolved host name a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:37:43Z" - latency: 7.415856ms message: 'load-balancer-api-external: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:36:43Z" - latency: 6.667393ms message: 'load-balancer-api-external: resolved host name a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:36:43Z" - latency: 4.639684ms message: 'load-balancer-api-external: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:35:43Z" - latency: 7.19922ms message: 'load-balancer-api-external: resolved host name a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:35:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:51:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-192-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-192.ec2.internal uid: 5a06319d-349f-4e09-b7d2-ceaef9e3a940 resourceVersion: "38274" uid: a7534b93-62ff-4b45-b3af-6fdc6002c24d spec: sourcePod: network-check-source-65bdbbff45-88r5l targetEndpoint: a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T14:57:43Z" message: 'load-balancer-api-internal: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.028569ms message: 'load-balancer-api-internal: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:39:43Z" - latency: 6.832931ms message: 'load-balancer-api-internal: resolved host name a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:39:43Z" - latency: 5.042179ms message: 'load-balancer-api-internal: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:38:43Z" - latency: 6.190996ms message: 'load-balancer-api-internal: resolved host name a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:38:43Z" - latency: 5.073519ms message: 'load-balancer-api-internal: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:37:43Z" - latency: 7.579604ms message: 'load-balancer-api-internal: resolved host name a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:37:43Z" - latency: 7.402433ms message: 'load-balancer-api-internal: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:36:43Z" - latency: 6.701642ms message: 'load-balancer-api-internal: resolved host name a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:36:43Z" - latency: 4.612138ms message: 'load-balancer-api-internal: tcp connection to a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:35:43Z" - latency: 7.271163ms message: 'load-balancer-api-internal: resolved host name a00f9b00ac7804625a7c8fe3b5f29b18-0520773980785504.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T15:35:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:51:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-192-to-network-check-target-ip-10-0-129-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-192.ec2.internal uid: 5a06319d-349f-4e09-b7d2-ceaef9e3a940 resourceVersion: "38796" uid: f55b9e1c-8b04-452c-8ceb-10dffc04fcd8 spec: sourcePod: network-check-source-65bdbbff45-88r5l targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-31T14:58:43Z" message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.44323ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:40:43Z" - latency: 895.048µs message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:39:43Z" - latency: 963.692µs message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:38:43Z" - latency: 901.953µs message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:37:43Z" - latency: 1.574777ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:36:43Z" - latency: 1.378602ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:35:43Z" - latency: 950.331µs message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:34:43Z" - latency: 951.349µs message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:33:43Z" - latency: 969.762µs message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:32:43Z" - latency: 1.012965ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:31:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:51:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-192-to-network-check-target-ip-10-0-130-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-192.ec2.internal uid: 5a06319d-349f-4e09-b7d2-ceaef9e3a940 resourceVersion: "38798" uid: 41f4e97f-e788-41bf-a3e6-fbbfa92f6ad5 spec: sourcePod: network-check-source-65bdbbff45-88r5l targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-31T14:58:43Z" message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.662344ms message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:40:43Z" - latency: 2.55804ms message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:39:43Z" - latency: 2.303568ms message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:38:43Z" - latency: 2.1578ms message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:37:43Z" - latency: 2.537915ms message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:36:43Z" - latency: 2.422242ms message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:35:43Z" - latency: 2.458809ms message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:34:43Z" - latency: 2.561579ms message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:33:43Z" - latency: 2.643467ms message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:32:43Z" - latency: 2.284278ms message: 'network-check-target-ip-10-0-130-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:31:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:51:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-192-to-network-check-target-ip-10-0-142-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-192.ec2.internal uid: 5a06319d-349f-4e09-b7d2-ceaef9e3a940 resourceVersion: "38797" uid: 58fd3509-7339-4972-845f-e66199890980 spec: sourcePod: network-check-source-65bdbbff45-88r5l targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-31T14:58:43Z" message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.661893ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:40:43Z" - latency: 2.423797ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:39:43Z" - latency: 2.083746ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:38:43Z" - latency: 2.098476ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:37:43Z" - latency: 2.476512ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:36:43Z" - latency: 2.226166ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:35:43Z" - latency: 1.987197ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:34:43Z" - latency: 2.145169ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:33:43Z" - latency: 2.686888ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:32:43Z" - latency: 2.269393ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:31:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T14:51:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-192-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-192.ec2.internal uid: 5a06319d-349f-4e09-b7d2-ceaef9e3a940 resourceVersion: "38273" uid: bdd094c5-c5df-463d-bcef-2b74fc4baf25 spec: sourcePod: network-check-source-65bdbbff45-88r5l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-31T14:57:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 953.149µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:39:43Z" - latency: 1.86702ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T15:39:43Z" - latency: 872.747µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:38:43Z" - latency: 1.676982ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T15:38:43Z" - latency: 1.073786ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:37:43Z" - latency: 2.015249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T15:37:43Z" - latency: 924.019µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:36:43Z" - latency: 1.949443ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T15:36:43Z" - latency: 1.305396ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T15:35:43Z" - latency: 1.795496ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T15:35:43Z" kind: List metadata: resourceVersion: ""