apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T01:08:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-91-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-91.ec2.internal uid: 2a2771cf-42ae-4e20-a67d-6114f03490b1 resourceVersion: "30416" uid: 71d4df0e-cfde-4693-acb0-846e95ef1774 spec: sourcePod: network-check-source-56d84b9f44-m8mgs targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T01:15:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.270204ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:22:51Z" - latency: 899.561µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:21:50Z" - latency: 974.757µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:20:51Z" - latency: 729.456µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:19:51Z" - latency: 1.361853ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:18:51Z" - latency: 976.373µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:17:50Z" - latency: 870.342µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:16:51Z" - latency: 1.242887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:15:50Z" - latency: 851.236µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:14:51Z" - latency: 865.367µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T01:08:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-91-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-91.ec2.internal uid: 2a2771cf-42ae-4e20-a67d-6114f03490b1 resourceVersion: "28866" uid: 7f716e4a-4d9c-4a18-9770-df7de62889fa spec: sourcePod: network-check-source-56d84b9f44-m8mgs targetEndpoint: a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T01:14:51Z" message: 'load-balancer-api-external: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.392273ms message: 'load-balancer-api-external: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:20:51Z" - latency: 6.917323ms message: 'load-balancer-api-external: resolved host name a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T01:20:51Z" - latency: 4.467138ms message: 'load-balancer-api-external: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:19:51Z" - latency: 6.940456ms message: 'load-balancer-api-external: resolved host name a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T01:19:51Z" - latency: 5.829276ms message: 'load-balancer-api-external: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:18:51Z" - latency: 6.86051ms message: 'load-balancer-api-external: resolved host name a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T01:18:51Z" - latency: 5.563038ms message: 'load-balancer-api-external: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:17:51Z" - latency: 7.752348ms message: 'load-balancer-api-external: resolved host name a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T01:17:50Z" - latency: 4.526967ms message: 'load-balancer-api-external: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:16:51Z" - latency: 6.697417ms message: 'load-balancer-api-external: resolved host name a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T01:16:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T01:08:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-91-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-91.ec2.internal uid: 2a2771cf-42ae-4e20-a67d-6114f03490b1 resourceVersion: "28867" uid: 781b2f66-ba74-4072-84d0-bb802ba0336a spec: sourcePod: network-check-source-56d84b9f44-m8mgs targetEndpoint: a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T01:14:51Z" message: 'load-balancer-api-internal: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.409597ms message: 'load-balancer-api-internal: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:20:51Z" - latency: 6.848043ms message: 'load-balancer-api-internal: resolved host name a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T01:20:51Z" - latency: 5.331891ms message: 'load-balancer-api-internal: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:19:51Z" - latency: 6.98381ms message: 'load-balancer-api-internal: resolved host name a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T01:19:51Z" - latency: 5.353994ms message: 'load-balancer-api-internal: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:18:51Z" - latency: 7.034446ms message: 'load-balancer-api-internal: resolved host name a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T01:18:51Z" - latency: 5.514204ms message: 'load-balancer-api-internal: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:17:51Z" - latency: 7.64214ms message: 'load-balancer-api-internal: resolved host name a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T01:17:50Z" - latency: 4.464682ms message: 'load-balancer-api-internal: tcp connection to a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:16:51Z" - latency: 6.713895ms message: 'load-balancer-api-internal: resolved host name a68f1d8dca58d4b89b2aeeb6ff68d931-3a79b4131d8ecc19.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T01:16:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T01:08:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-91-to-network-check-target-ip-10-0-132-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-91.ec2.internal uid: 2a2771cf-42ae-4e20-a67d-6114f03490b1 resourceVersion: "30414" uid: d2543dc6-57e7-4fb9-87a0-2c9b57fb8fdc spec: sourcePod: network-check-source-56d84b9f44-m8mgs targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T01:15:51Z" message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.09286ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:22:51Z" - latency: 2.569363ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:21:50Z" - latency: 2.174667ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:20:51Z" - latency: 2.09103ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:19:51Z" - latency: 2.168103ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:18:51Z" - latency: 2.107321ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:17:50Z" - latency: 2.603023ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:16:51Z" - latency: 2.16675ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:15:50Z" - latency: 2.143759ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:14:51Z" - latency: 2.814287ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T01:08:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-91-to-network-check-target-ip-10-0-138-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-91.ec2.internal uid: 2a2771cf-42ae-4e20-a67d-6114f03490b1 resourceVersion: "30415" uid: 60c7df28-5139-4458-ba3d-87bf7bff289b spec: sourcePod: network-check-source-56d84b9f44-m8mgs targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T01:15:51Z" message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.382644ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:22:51Z" - latency: 2.408686ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:21:50Z" - latency: 2.397213ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:20:51Z" - latency: 2.144004ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:19:51Z" - latency: 2.399247ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:18:51Z" - latency: 2.492143ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:17:50Z" - latency: 2.403474ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:16:51Z" - latency: 2.843298ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:15:50Z" - latency: 2.1115ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:14:51Z" - latency: 2.712586ms message: 'network-check-target-ip-10-0-138-55: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T01:08:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-91-to-network-check-target-ip-10-0-142-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-91.ec2.internal uid: 2a2771cf-42ae-4e20-a67d-6114f03490b1 resourceVersion: "30413" uid: e6b2e924-afc9-44f0-b831-5865b180c6db spec: sourcePod: network-check-source-56d84b9f44-m8mgs targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T01:15:51Z" message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.583µs message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:22:51Z" - latency: 834.227µs message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:21:50Z" - latency: 998.312µs message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:20:51Z" - latency: 731.37µs message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:19:51Z" - latency: 880.866µs message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:18:51Z" - latency: 745.685µs message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:17:51Z" - latency: 866.455µs message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:16:51Z" - latency: 915.715µs message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:15:50Z" - latency: 816.702µs message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:14:51Z" - latency: 1.340554ms message: 'network-check-target-ip-10-0-142-91: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T01:08:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-91-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-91.ec2.internal uid: 2a2771cf-42ae-4e20-a67d-6114f03490b1 resourceVersion: "28865" uid: d9cdd91b-89b8-4c86-b4e4-235c3265d4c4 spec: sourcePod: network-check-source-56d84b9f44-m8mgs targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T01:14:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 798.066µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:20:51Z" - latency: 1.626382ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T01:20:51Z" - latency: 864.285µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:19:51Z" - latency: 1.533232ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T01:19:51Z" - latency: 765.866µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:18:51Z" - latency: 1.764728ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T01:18:51Z" - latency: 1.451367ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:17:51Z" - latency: 1.770546ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T01:17:50Z" - latency: 832.415µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T01:16:51Z" - latency: 1.669664ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T01:16:51Z" kind: List metadata: resourceVersion: ""