apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:05:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-193-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-193.ec2.internal uid: 1d6c3f29-2652-47e4-af31-58f916dbfc3d resourceVersion: "21709" uid: 69db18ce-b58c-47d2-a0e7-33ef8b23755d spec: sourcePod: network-check-source-7d88cb55d8-8nlbq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T12:12:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.116992ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:33:57Z" - latency: 3.675657ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:32:57Z" - latency: 930.479µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:31:57Z" - latency: 924.587µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:30:57Z" - latency: 928.12µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:29:57Z" - latency: 1.131749ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:28:57Z" - latency: 973.041µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:27:57Z" - latency: 912.162µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:57Z" - latency: 1.352078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:57Z" - latency: 878.326µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:05:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-193-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-193.ec2.internal uid: 1d6c3f29-2652-47e4-af31-58f916dbfc3d resourceVersion: "22460" uid: 448afc67-03e5-45ea-995e-83ae3e0cdf9a spec: sourcePod: network-check-source-7d88cb55d8-8nlbq targetEndpoint: aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T12:11:57Z" message: 'load-balancer-api-external: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.115937ms message: 'load-balancer-api-external: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:35:57Z" - latency: 9.766451ms message: 'load-balancer-api-external: resolved host name aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:35:57Z" - latency: 5.249567ms message: 'load-balancer-api-external: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:34:57Z" - latency: 8.149613ms message: 'load-balancer-api-external: resolved host name aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:34:57Z" - latency: 5.319294ms message: 'load-balancer-api-external: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:33:57Z" - latency: 6.760869ms message: 'load-balancer-api-external: resolved host name aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:33:57Z" - latency: 5.230364ms message: 'load-balancer-api-external: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:32:57Z" - latency: 13.785142ms message: 'load-balancer-api-external: resolved host name aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:32:57Z" - latency: 5.805238ms message: 'load-balancer-api-external: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:31:57Z" - latency: 9.556734ms message: 'load-balancer-api-external: resolved host name aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:31:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:05:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-193-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-193.ec2.internal uid: 1d6c3f29-2652-47e4-af31-58f916dbfc3d resourceVersion: "22461" uid: 6399dbf7-c10a-4e18-b253-fdb1878aacef spec: sourcePod: network-check-source-7d88cb55d8-8nlbq targetEndpoint: aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T12:11:57Z" message: 'load-balancer-api-internal: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.076626ms message: 'load-balancer-api-internal: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:35:57Z" - latency: 9.844059ms message: 'load-balancer-api-internal: resolved host name aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:35:57Z" - latency: 5.220827ms message: 'load-balancer-api-internal: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:34:57Z" - latency: 8.235042ms message: 'load-balancer-api-internal: resolved host name aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:34:57Z" - latency: 5.283884ms message: 'load-balancer-api-internal: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:33:57Z" - latency: 6.827282ms message: 'load-balancer-api-internal: resolved host name aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:33:57Z" - latency: 6.410183ms message: 'load-balancer-api-internal: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:32:57Z" - latency: 13.843802ms message: 'load-balancer-api-internal: resolved host name aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:32:57Z" - latency: 5.79452ms message: 'load-balancer-api-internal: tcp connection to aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:31:57Z" - latency: 9.621716ms message: 'load-balancer-api-internal: resolved host name aed3685c2d11a41bc84796d0a8ece5b3-5b610ef4738baac5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:31:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:05:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-193-to-network-check-target-ip-10-0-130-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-193.ec2.internal uid: 1d6c3f29-2652-47e4-af31-58f916dbfc3d resourceVersion: "21706" uid: 2ba13233-10ad-4993-9dc6-681c5802450c spec: sourcePod: network-check-source-7d88cb55d8-8nlbq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T12:12:57Z" message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 920.97µs message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:33:57Z" - latency: 4.764923ms message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:32:57Z" - latency: 862.588µs message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:31:57Z" - latency: 829.437µs message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:30:57Z" - latency: 997.456µs message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:29:57Z" - latency: 998.865µs message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:28:57Z" - latency: 936.13µs message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:27:57Z" - latency: 1.398041ms message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:57Z" - latency: 883.007µs message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:57Z" - latency: 1.203577ms message: 'network-check-target-ip-10-0-130-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:05:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-193-to-network-check-target-ip-10-0-131-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-193.ec2.internal uid: 1d6c3f29-2652-47e4-af31-58f916dbfc3d resourceVersion: "21708" uid: bab6ac78-c1ba-490a-b293-2abaf4d6149a spec: sourcePod: network-check-source-7d88cb55d8-8nlbq targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T12:12:57Z" message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.383743ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:33:57Z" - latency: 5.235711ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:32:57Z" - latency: 2.255145ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:31:57Z" - latency: 2.128052ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:30:57Z" - latency: 2.184719ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:29:57Z" - latency: 2.113939ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:28:57Z" - latency: 1.918164ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:27:57Z" - latency: 2.360242ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:57Z" - latency: 2.063488ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:57Z" - latency: 2.435323ms message: 'network-check-target-ip-10-0-131-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:05:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-193-to-network-check-target-ip-10-0-134-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-193.ec2.internal uid: 1d6c3f29-2652-47e4-af31-58f916dbfc3d resourceVersion: "21707" uid: b83b21b2-4274-43ca-ac7f-4220a69c1a55 spec: sourcePod: network-check-source-7d88cb55d8-8nlbq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T12:12:57Z" message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.938981ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:33:57Z" - latency: 2.001332ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:32:57Z" - latency: 1.636279ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:31:57Z" - latency: 1.770603ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:30:57Z" - latency: 1.842889ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:29:57Z" - latency: 1.868651ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:28:57Z" - latency: 1.845303ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:27:57Z" - latency: 2.13388ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:57Z" - latency: 1.844434ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:57Z" - latency: 1.935709ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:05:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-193-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-193.ec2.internal uid: 1d6c3f29-2652-47e4-af31-58f916dbfc3d resourceVersion: "22459" uid: fc845fdc-fd4d-4472-a995-4be9f83a771e spec: sourcePod: network-check-source-7d88cb55d8-8nlbq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T12:11:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 626.11µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:35:57Z" - latency: 1.79232ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T12:35:57Z" - latency: 930.599µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:34:57Z" - latency: 1.725146ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T12:34:57Z" - latency: 1.149408ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:33:57Z" - latency: 1.728318ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T12:33:57Z" - latency: 815.869µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:32:57Z" - latency: 5.253721ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T12:32:57Z" - latency: 758.253µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:31:57Z" - latency: 1.722505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T12:31:57Z" kind: List metadata: resourceVersion: ""