apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-109-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-109.ec2.internal uid: 009d1c6a-7a09-4d15-aa87-55f53adddedf resourceVersion: "22786" uid: ac9abd4c-6823-408a-a31f-6e9c43aa4d5a spec: sourcePod: network-check-source-dbd9cf844-fsn7m targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T15:15:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.489973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:56Z" - latency: 922.56µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:56Z" - latency: 972.022µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:13:56Z" - latency: 899.863µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:12:56Z" - latency: 2.041418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:11:56Z" - latency: 811.807µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:10:56Z" - latency: 1.325295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:09:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-109-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-109.ec2.internal uid: 009d1c6a-7a09-4d15-aa87-55f53adddedf resourceVersion: "27764" uid: a826a866-92d8-487b-9d70-438637d318df spec: sourcePod: network-check-source-dbd9cf844-fsn7m targetEndpoint: abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T15:14:56Z" message: 'load-balancer-api-external: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.467053ms message: 'load-balancer-api-external: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:20:56Z" - latency: 8.066576ms message: 'load-balancer-api-external: resolved host name abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:20:56Z" - latency: 5.54333ms message: 'load-balancer-api-external: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:19:56Z" - latency: 8.878538ms message: 'load-balancer-api-external: resolved host name abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:19:56Z" - latency: 4.415881ms message: 'load-balancer-api-external: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:18:56Z" - latency: 8.623861ms message: 'load-balancer-api-external: resolved host name abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:18:56Z" - latency: 15.280917ms message: 'load-balancer-api-external: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:17:56Z" - latency: 9.45521ms message: 'load-balancer-api-external: resolved host name abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:17:56Z" - latency: 5.528614ms message: 'load-balancer-api-external: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:16:56Z" - latency: 12.231175ms message: 'load-balancer-api-external: resolved host name abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:16:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-109-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-109.ec2.internal uid: 009d1c6a-7a09-4d15-aa87-55f53adddedf resourceVersion: "27763" uid: 8fe21de0-b708-4695-b436-fc10e41c8ab7 spec: sourcePod: network-check-source-dbd9cf844-fsn7m targetEndpoint: abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T15:14:56Z" message: 'load-balancer-api-internal: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.344086ms message: 'load-balancer-api-internal: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:20:56Z" - latency: 8.160573ms message: 'load-balancer-api-internal: resolved host name abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:20:56Z" - latency: 5.403074ms message: 'load-balancer-api-internal: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:19:56Z" - latency: 8.899666ms message: 'load-balancer-api-internal: resolved host name abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:19:56Z" - latency: 4.544302ms message: 'load-balancer-api-internal: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:18:56Z" - latency: 8.747662ms message: 'load-balancer-api-internal: resolved host name abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:18:56Z" - latency: 19.289587ms message: 'load-balancer-api-internal: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:17:56Z" - latency: 9.51617ms message: 'load-balancer-api-internal: resolved host name abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:17:56Z" - latency: 5.062841ms message: 'load-balancer-api-internal: tcp connection to abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:16:56Z" - latency: 12.171563ms message: 'load-balancer-api-internal: resolved host name abf83aa98c4b3490e86265ce449a36e1-2bf90f62d2a26cd9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T15:16:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-109-to-network-check-target-ip-10-0-131-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-109.ec2.internal uid: 009d1c6a-7a09-4d15-aa87-55f53adddedf resourceVersion: "22782" uid: 9383ec8b-045f-42ab-bcce-0264e1930cb3 spec: sourcePod: network-check-source-dbd9cf844-fsn7m targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:15:56Z" message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.40078ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:56Z" - latency: 1.733967ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:56Z" - latency: 2.163515ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:13:56Z" - latency: 2.072166ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:12:56Z" - latency: 2.430513ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:11:56Z" - latency: 2.368144ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:10:56Z" - latency: 2.134786ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:09:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-109-to-network-check-target-ip-10-0-135-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-109.ec2.internal uid: 009d1c6a-7a09-4d15-aa87-55f53adddedf resourceVersion: "22783" uid: fe921f9b-48bb-49da-bbaa-8d0ec4cc069c spec: sourcePod: network-check-source-dbd9cf844-fsn7m targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:15:56Z" message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.810099ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:56Z" - latency: 878.49µs message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:56Z" - latency: 990.679µs message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:13:56Z" - latency: 921.246µs message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:12:56Z" - latency: 2.054091ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:11:56Z" - latency: 1.356714ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:10:56Z" - latency: 2.144333ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:09:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-109-to-network-check-target-ip-10-0-138-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-109.ec2.internal uid: 009d1c6a-7a09-4d15-aa87-55f53adddedf resourceVersion: "22784" uid: e40403ff-2ebb-49d6-8621-76fe059ddb10 spec: sourcePod: network-check-source-dbd9cf844-fsn7m targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:15:56Z" message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.890261ms message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:15:56Z" - latency: 1.916632ms message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:14:56Z" - latency: 1.925675ms message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:13:56Z" - latency: 2.094399ms message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:12:56Z" - latency: 2.735185ms message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:11:56Z" - latency: 2.348232ms message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:10:56Z" - latency: 2.166868ms message: 'network-check-target-ip-10-0-138-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:09:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:08:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-109-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-109.ec2.internal uid: 009d1c6a-7a09-4d15-aa87-55f53adddedf resourceVersion: "27762" uid: 4d6965ed-ecdf-4935-a1eb-4b5f5126f2ca spec: sourcePod: network-check-source-dbd9cf844-fsn7m targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T15:14:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 858.353µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:20:56Z" - latency: 1.967688ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:20:56Z" - latency: 1.148404ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:19:56Z" - latency: 1.744881ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:19:56Z" - latency: 1.044086ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:18:56Z" - latency: 2.049831ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:18:56Z" - latency: 809.876µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:17:56Z" - latency: 2.976716ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:17:56Z" - latency: 963.781µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:16:56Z" - latency: 1.638546ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T15:16:56Z" kind: List metadata: resourceVersion: ""