apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:36:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-14-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-14.ec2.internal uid: 0b80283f-99bc-48b6-b06a-03acff422ac9 resourceVersion: "25326" uid: fc1f7234-54a4-4ac5-9ee1-f86cdebcf353 spec: sourcePod: network-check-source-7d88cb55d8-rtpzf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T15:43:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.252762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:04:46Z" - latency: 1.109226ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:03:46Z" - latency: 875.764µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:02:46Z" - latency: 1.011425ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:01:46Z" - latency: 1.178595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:00:46Z" - latency: 1.337194ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:59:46Z" - latency: 1.362046ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:58:46Z" - latency: 1.370788ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:57:46Z" - latency: 959.35µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:56:46Z" - latency: 1.511381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:55:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:36:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-14-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-14.ec2.internal uid: 0b80283f-99bc-48b6-b06a-03acff422ac9 resourceVersion: "26437" uid: 5a78a864-240f-449f-93ba-086692a87846 spec: sourcePod: network-check-source-7d88cb55d8-rtpzf targetEndpoint: aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T15:42:46Z" message: 'load-balancer-api-external: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.065201ms message: 'load-balancer-api-external: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:06:46Z" - latency: 8.727168ms message: 'load-balancer-api-external: resolved host name aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:06:46Z" - latency: 4.367735ms message: 'load-balancer-api-external: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:05:46Z" - latency: 9.424808ms message: 'load-balancer-api-external: resolved host name aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:05:46Z" - latency: 5.382462ms message: 'load-balancer-api-external: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:04:46Z" - latency: 9.401336ms message: 'load-balancer-api-external: resolved host name aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:04:46Z" - latency: 4.656421ms message: 'load-balancer-api-external: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:03:46Z" - latency: 8.495069ms message: 'load-balancer-api-external: resolved host name aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:03:46Z" - latency: 6.492805ms message: 'load-balancer-api-external: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:02:46Z" - latency: 8.725383ms message: 'load-balancer-api-external: resolved host name aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:02:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:36:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-14-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-14.ec2.internal uid: 0b80283f-99bc-48b6-b06a-03acff422ac9 resourceVersion: "26438" uid: 8711d64b-a29a-43af-a6b0-cc9da219dfe1 spec: sourcePod: network-check-source-7d88cb55d8-rtpzf targetEndpoint: aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T15:42:46Z" message: 'load-balancer-api-internal: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.050877ms message: 'load-balancer-api-internal: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:06:46Z" - latency: 8.701723ms message: 'load-balancer-api-internal: resolved host name aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:06:46Z" - latency: 4.731492ms message: 'load-balancer-api-internal: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:05:46Z" - latency: 9.349435ms message: 'load-balancer-api-internal: resolved host name aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:05:46Z" - latency: 5.402837ms message: 'load-balancer-api-internal: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:04:46Z" - latency: 9.477315ms message: 'load-balancer-api-internal: resolved host name aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:04:46Z" - latency: 4.58759ms message: 'load-balancer-api-internal: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:03:46Z" - latency: 8.45465ms message: 'load-balancer-api-internal: resolved host name aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:03:46Z" - latency: 6.498711ms message: 'load-balancer-api-internal: tcp connection to aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:02:46Z" - latency: 8.694341ms message: 'load-balancer-api-internal: resolved host name aedd9570c5e584d9eba628ac59ea80f4-466768cf0c31db62.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:02:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:36:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-14-to-network-check-target-ip-10-0-131-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-14.ec2.internal uid: 0b80283f-99bc-48b6-b06a-03acff422ac9 resourceVersion: "25324" uid: a7958766-2767-40ac-a4d1-b96bcfc04de2 spec: sourcePod: network-check-source-7d88cb55d8-rtpzf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T15:43:46Z" message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.620128ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:04:46Z" - latency: 2.780983ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:03:46Z" - latency: 2.218311ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:02:46Z" - latency: 2.767626ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:01:46Z" - latency: 2.426609ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:00:46Z" - latency: 2.388757ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:59:46Z" - latency: 2.418943ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:58:46Z" - latency: 2.267552ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:57:46Z" - latency: 2.380783ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:56:46Z" - latency: 2.171784ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:55:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:36:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-14-to-network-check-target-ip-10-0-133-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-14.ec2.internal uid: 0b80283f-99bc-48b6-b06a-03acff422ac9 resourceVersion: "25325" uid: f22fd768-789d-4fab-be6e-c86625541d1d spec: sourcePod: network-check-source-7d88cb55d8-rtpzf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T15:43:46Z" message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.693628ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:04:46Z" - latency: 2.212001ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:03:46Z" - latency: 2.412753ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:02:46Z" - latency: 2.357602ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:01:46Z" - latency: 2.305117ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:00:46Z" - latency: 2.33561ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:59:46Z" - latency: 2.37861ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:58:46Z" - latency: 2.307365ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:57:46Z" - latency: 2.245669ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:56:46Z" - latency: 2.088609ms message: 'network-check-target-ip-10-0-133-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:55:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:36:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-14-to-network-check-target-ip-10-0-137-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-14.ec2.internal uid: 0b80283f-99bc-48b6-b06a-03acff422ac9 resourceVersion: "25323" uid: 0a771dc2-feb7-498c-bd14-8c8b59e37bf0 spec: sourcePod: network-check-source-7d88cb55d8-rtpzf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T15:43:46Z" message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.526914ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:04:46Z" - latency: 1.374599ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:03:46Z" - latency: 874.15µs message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:02:46Z" - latency: 1.676294ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:01:46Z" - latency: 989.258µs message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:00:46Z" - latency: 1.557705ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:59:46Z" - latency: 1.684814ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:58:46Z" - latency: 870.716µs message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:57:46Z" - latency: 1.011593ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:56:46Z" - latency: 993.393µs message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:55:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:36:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-14-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-14.ec2.internal uid: 0b80283f-99bc-48b6-b06a-03acff422ac9 resourceVersion: "26436" uid: a4ce051e-d3a7-464c-9b77-3596cda7dc82 spec: sourcePod: network-check-source-7d88cb55d8-rtpzf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T15:42:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 916.765µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:06:46Z" - latency: 1.883693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:06:46Z" - latency: 917.335µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:05:46Z" - latency: 2.170926ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:05:46Z" - latency: 1.051378ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:04:46Z" - latency: 1.847694ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:04:46Z" - latency: 1.002699ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:03:46Z" - latency: 1.629403ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:03:46Z" - latency: 1.08799ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:02:46Z" - latency: 2.006608ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:02:46Z" kind: List metadata: resourceVersion: ""