apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T19:46:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-240-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-240.ec2.internal uid: 8dfa513f-e09c-49d1-8cb6-ef0011a7380a resourceVersion: "69938" uid: bdf04df5-73c8-488c-9acb-1a2a636b03ff spec: sourcePod: network-check-source-7cbc45fddc-7s7sk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-18T19:53:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.084132ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:21:03Z" - latency: 846.356µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:20:03Z" - latency: 724.767µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:19:03Z" - latency: 1.517336ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:18:03Z" - latency: 847.016µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:17:03Z" - latency: 1.007362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:16:03Z" - latency: 2.386122ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:15:03Z" - latency: 1.940194ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:14:03Z" - latency: 956.509µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:13:03Z" - latency: 1.138023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:12:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T19:46:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-240-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-240.ec2.internal uid: 8dfa513f-e09c-49d1-8cb6-ef0011a7380a resourceVersion: "70929" uid: efcc4936-321d-433a-ab98-a23adf24f459 spec: sourcePod: network-check-source-7cbc45fddc-7s7sk targetEndpoint: a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T19:52:03Z" message: 'load-balancer-api-external: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.813231ms message: 'load-balancer-api-external: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:22:03Z" - latency: 8.586041ms message: 'load-balancer-api-external: resolved host name a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T20:22:03Z" - latency: 5.762649ms message: 'load-balancer-api-external: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:21:03Z" - latency: 8.069063ms message: 'load-balancer-api-external: resolved host name a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T20:21:03Z" - latency: 4.098559ms message: 'load-balancer-api-external: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:20:03Z" - latency: 8.163901ms message: 'load-balancer-api-external: resolved host name a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T20:20:03Z" - latency: 3.636575ms message: 'load-balancer-api-external: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:19:03Z" - latency: 8.456613ms message: 'load-balancer-api-external: resolved host name a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T20:19:03Z" - latency: 5.388456ms message: 'load-balancer-api-external: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:18:03Z" - latency: 7.748698ms message: 'load-balancer-api-external: resolved host name a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T20:18:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T19:46:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-240-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-240.ec2.internal uid: 8dfa513f-e09c-49d1-8cb6-ef0011a7380a resourceVersion: "70930" uid: cbb816ed-dafd-4af5-8ce3-b8155e933758 spec: sourcePod: network-check-source-7cbc45fddc-7s7sk targetEndpoint: a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T19:52:03Z" message: 'load-balancer-api-internal: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.797528ms message: 'load-balancer-api-internal: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:22:03Z" - latency: 8.669646ms message: 'load-balancer-api-internal: resolved host name a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T20:22:03Z" - latency: 5.748394ms message: 'load-balancer-api-internal: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:21:03Z" - latency: 8.120727ms message: 'load-balancer-api-internal: resolved host name a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T20:21:03Z" - latency: 3.807003ms message: 'load-balancer-api-internal: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:20:03Z" - latency: 8.202822ms message: 'load-balancer-api-internal: resolved host name a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T20:20:03Z" - latency: 3.672192ms message: 'load-balancer-api-internal: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:19:03Z" - latency: 8.506011ms message: 'load-balancer-api-internal: resolved host name a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T20:19:03Z" - latency: 4.807895ms message: 'load-balancer-api-internal: tcp connection to a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:18:03Z" - latency: 7.776626ms message: 'load-balancer-api-internal: resolved host name a8106458f498845dc8c2ea97b97d4951-c279d871b936f215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T20:18:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T19:46:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-240-to-network-check-target-ip-10-0-135-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-240.ec2.internal uid: 8dfa513f-e09c-49d1-8cb6-ef0011a7380a resourceVersion: "69935" uid: 117d9655-b5e5-402b-bd50-67736bf951b0 spec: sourcePod: network-check-source-7cbc45fddc-7s7sk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-18T19:53:03Z" message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.124µs message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:21:03Z" - latency: 762.188µs message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:20:03Z" - latency: 1.246746ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:19:03Z" - latency: 1.16173ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:18:03Z" - latency: 1.375487ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:17:03Z" - latency: 866.763µs message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:16:03Z" - latency: 3.229135ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:15:03Z" - latency: 1.012916ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:14:03Z" - latency: 1.643089ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:13:03Z" - latency: 876.52µs message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:12:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T19:46:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-240-to-network-check-target-ip-10-0-136-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-240.ec2.internal uid: 8dfa513f-e09c-49d1-8cb6-ef0011a7380a resourceVersion: "69936" uid: 3777e1ee-f1c6-4a89-b9f3-f60e2b9e1160 spec: sourcePod: network-check-source-7cbc45fddc-7s7sk targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-18T19:53:03Z" message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.041669ms message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:21:03Z" - latency: 1.903779ms message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:20:03Z" - latency: 1.939669ms message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:19:03Z" - latency: 2.059219ms message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:18:03Z" - latency: 1.988004ms message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:17:03Z" - latency: 2.006889ms message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:16:03Z" - latency: 2.843608ms message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:15:03Z" - latency: 2.688141ms message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:14:03Z" - latency: 2.443375ms message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:13:03Z" - latency: 2.111082ms message: 'network-check-target-ip-10-0-136-185: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:12:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T19:46:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-240-to-network-check-target-ip-10-0-143-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-240.ec2.internal uid: 8dfa513f-e09c-49d1-8cb6-ef0011a7380a resourceVersion: "69937" uid: fe470a05-e954-42cb-beb4-80a850d2a477 spec: sourcePod: network-check-source-7cbc45fddc-7s7sk targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-18T19:53:03Z" message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.263267ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:21:03Z" - latency: 2.294851ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:20:03Z" - latency: 2.118888ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:19:03Z" - latency: 1.813647ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:18:03Z" - latency: 2.289183ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:17:03Z" - latency: 2.470181ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:16:03Z" - latency: 3.011647ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:15:03Z" - latency: 2.374015ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:14:03Z" - latency: 2.345059ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:13:03Z" - latency: 2.128868ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:12:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T19:46:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-240-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-240.ec2.internal uid: 8dfa513f-e09c-49d1-8cb6-ef0011a7380a resourceVersion: "70927" uid: 8a289a5f-83b6-4dca-be1c-6f7f3e18c042 spec: sourcePod: network-check-source-7cbc45fddc-7s7sk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-18T19:52:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 695.543µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:22:03Z" - latency: 1.865548ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T20:22:03Z" - latency: 880.817µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:21:03Z" - latency: 1.591483ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T20:21:03Z" - latency: 747.47µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:20:03Z" - latency: 2.515451ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T20:20:03Z" - latency: 1.027936ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:19:03Z" - latency: 1.500104ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T20:19:03Z" - latency: 683.413µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T20:18:03Z" - latency: 1.986466ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T20:18:03Z" kind: List metadata: resourceVersion: ""