apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-146-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-146.ec2.internal uid: 19df8a8f-3db3-4d71-bdda-a4a301608c36 resourceVersion: "71422" uid: 57a6d97b-c719-4d76-bae8-377459fba5fb spec: sourcePod: network-check-source-7d88cb55d8-drh5c targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-26T18:08:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.00662ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:50:47Z" - latency: 1.246817ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:49:47Z" - latency: 1.212272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:48:47Z" - latency: 959.969µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:47:47Z" - latency: 975.14µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:46:47Z" - latency: 998.279µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:45:47Z" - latency: 878.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:44:47Z" - latency: 951.428µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:43:47Z" - latency: 1.083555ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:42:47Z" - latency: 887.499µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:41:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-146-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-146.ec2.internal uid: 19df8a8f-3db3-4d71-bdda-a4a301608c36 resourceVersion: "70566" uid: 07ae8ec9-e06e-4be7-a1e7-9a0be15ed9c5 spec: sourcePod: network-check-source-7d88cb55d8-drh5c targetEndpoint: aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-26T18:07:47Z" message: 'load-balancer-api-external: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.023845ms message: 'load-balancer-api-external: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:49:47Z" - latency: 7.184956ms message: 'load-balancer-api-external: resolved host name aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:49:47Z" - latency: 4.838749ms message: 'load-balancer-api-external: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:48:47Z" - latency: 6.816571ms message: 'load-balancer-api-external: resolved host name aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:48:47Z" - latency: 4.400217ms message: 'load-balancer-api-external: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:47:47Z" - latency: 6.407256ms message: 'load-balancer-api-external: resolved host name aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:47:47Z" - latency: 5.769155ms message: 'load-balancer-api-external: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:46:47Z" - latency: 6.637464ms message: 'load-balancer-api-external: resolved host name aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:46:47Z" - latency: 4.873975ms message: 'load-balancer-api-external: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:45:47Z" - latency: 8.407629ms message: 'load-balancer-api-external: resolved host name aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:45:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-146-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-146.ec2.internal uid: 19df8a8f-3db3-4d71-bdda-a4a301608c36 resourceVersion: "70567" uid: e3b7d347-aeef-4ef1-ac6e-80e1554c49b9 spec: sourcePod: network-check-source-7d88cb55d8-drh5c targetEndpoint: aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-26T18:07:47Z" message: 'load-balancer-api-internal: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.04446ms message: 'load-balancer-api-internal: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:49:47Z" - latency: 7.095207ms message: 'load-balancer-api-internal: resolved host name aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:49:47Z" - latency: 3.97761ms message: 'load-balancer-api-internal: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:48:47Z" - latency: 7.011683ms message: 'load-balancer-api-internal: resolved host name aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:48:47Z" - latency: 3.575943ms message: 'load-balancer-api-internal: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:47:47Z" - latency: 6.285551ms message: 'load-balancer-api-internal: resolved host name aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:47:47Z" - latency: 3.461331ms message: 'load-balancer-api-internal: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:46:47Z" - latency: 6.58194ms message: 'load-balancer-api-internal: resolved host name aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:46:47Z" - latency: 4.676236ms message: 'load-balancer-api-internal: tcp connection to aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:45:47Z" - latency: 8.386848ms message: 'load-balancer-api-internal: resolved host name aeda2ba61ce7b49b5a31cf5c1efe9ffe-52348ebd6d03e330.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:45:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-146-to-network-check-target-ip-10-0-132-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-146.ec2.internal uid: 19df8a8f-3db3-4d71-bdda-a4a301608c36 resourceVersion: "71419" uid: 2fd0be59-8adf-4b88-b86f-045ef782d600 spec: sourcePod: network-check-source-7d88cb55d8-drh5c targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-26T18:08:47Z" message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 813.253µs message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:50:47Z" - latency: 1.765818ms message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:49:47Z" - latency: 1.344839ms message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:48:47Z" - latency: 813.143µs message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:47:47Z" - latency: 894.148µs message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:46:47Z" - latency: 876.662µs message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:45:47Z" - latency: 839.287µs message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:44:47Z" - latency: 936.396µs message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:43:47Z" - latency: 683.785µs message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:42:47Z" - latency: 752.802µs message: 'network-check-target-ip-10-0-132-146: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:41:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-146-to-network-check-target-ip-10-0-133-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-146.ec2.internal uid: 19df8a8f-3db3-4d71-bdda-a4a301608c36 resourceVersion: "71420" uid: dcc59fd7-c07e-48bf-9f49-29150dedd00f spec: sourcePod: network-check-source-7d88cb55d8-drh5c targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-26T18:08:47Z" message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.342919ms message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:50:47Z" - latency: 2.752641ms message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:49:47Z" - latency: 2.282123ms message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:48:47Z" - latency: 2.141676ms message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:47:47Z" - latency: 2.556853ms message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:46:47Z" - latency: 2.43245ms message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:45:47Z" - latency: 1.880781ms message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:44:47Z" - latency: 2.138553ms message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:43:47Z" - latency: 2.109487ms message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:42:47Z" - latency: 2.354821ms message: 'network-check-target-ip-10-0-133-34: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:41:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-146-to-network-check-target-ip-10-0-143-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-146.ec2.internal uid: 19df8a8f-3db3-4d71-bdda-a4a301608c36 resourceVersion: "71421" uid: 2fdc756e-60b2-4f7e-b5fa-048fb040fc49 spec: sourcePod: network-check-source-7d88cb55d8-drh5c targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-26T18:08:47Z" message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.548713ms message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:50:47Z" - latency: 2.435509ms message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:49:47Z" - latency: 2.03982ms message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:48:47Z" - latency: 2.287376ms message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:47:47Z" - latency: 2.342361ms message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:46:47Z" - latency: 2.421021ms message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:45:47Z" - latency: 2.193522ms message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:44:47Z" - latency: 2.196172ms message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:43:47Z" - latency: 2.230392ms message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:42:47Z" - latency: 2.446549ms message: 'network-check-target-ip-10-0-143-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:41:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:01:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-146-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-146.ec2.internal uid: 19df8a8f-3db3-4d71-bdda-a4a301608c36 resourceVersion: "70565" uid: fd7b1758-bc78-4a2d-b163-5c078b509cda spec: sourcePod: network-check-source-7d88cb55d8-drh5c targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-26T18:07:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 952.209µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:49:47Z" - latency: 2.383607ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T18:49:47Z" - latency: 1.041212ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:48:47Z" - latency: 1.715423ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T18:48:47Z" - latency: 880.859µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:47:47Z" - latency: 1.600239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T18:47:47Z" - latency: 801.906µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:46:47Z" - latency: 1.746811ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T18:46:47Z" - latency: 790.509µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:45:47Z" - latency: 1.5909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T18:45:47Z" kind: List metadata: resourceVersion: ""