apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:20:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-74-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-74.ec2.internal uid: 851c6b78-bb35-4a4d-b472-2e017c0c6027 resourceVersion: "32249" uid: e1f63abe-6142-4341-8d36-96f798570b14 spec: sourcePod: network-check-source-989f8b8dc-96d87 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T02:27:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.478331ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:02:53Z" - latency: 949.945µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:01:53Z" - latency: 933.377µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:00:53Z" - latency: 933.609µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:59:53Z" - latency: 830.088µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:58:53Z" - latency: 870.756µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:57:53Z" - latency: 1.102085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:53Z" - latency: 1.007015ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:53Z" - latency: 1.01875ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:53Z" - latency: 975.947µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:20:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-74-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-74.ec2.internal uid: 851c6b78-bb35-4a4d-b472-2e017c0c6027 resourceVersion: "32251" uid: d952e715-cb0d-413d-a891-9d49ff948a9a spec: sourcePod: network-check-source-989f8b8dc-96d87 targetEndpoint: a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T02:26:53Z" message: 'load-balancer-api-external: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.786343ms message: 'load-balancer-api-external: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:02:53Z" - latency: 7.550792ms message: 'load-balancer-api-external: resolved host name a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:02:53Z" - latency: 5.018825ms message: 'load-balancer-api-external: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:01:53Z" - latency: 6.9813ms message: 'load-balancer-api-external: resolved host name a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:01:53Z" - latency: 4.847755ms message: 'load-balancer-api-external: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:00:53Z" - latency: 7.24561ms message: 'load-balancer-api-external: resolved host name a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:00:53Z" - latency: 4.12549ms message: 'load-balancer-api-external: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:59:53Z" - latency: 7.116011ms message: 'load-balancer-api-external: resolved host name a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:59:53Z" - latency: 4.4293ms message: 'load-balancer-api-external: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:58:53Z" - latency: 8.056697ms message: 'load-balancer-api-external: resolved host name a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:58:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:20:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-74-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-74.ec2.internal uid: 851c6b78-bb35-4a4d-b472-2e017c0c6027 resourceVersion: "32250" uid: eda441c6-60c6-47bf-b693-d5b1a5f804d3 spec: sourcePod: network-check-source-989f8b8dc-96d87 targetEndpoint: a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T02:26:53Z" message: 'load-balancer-api-internal: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.277942ms message: 'load-balancer-api-internal: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:02:53Z" - latency: 7.499261ms message: 'load-balancer-api-internal: resolved host name a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:02:53Z" - latency: 5.096811ms message: 'load-balancer-api-internal: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:01:53Z" - latency: 6.889739ms message: 'load-balancer-api-internal: resolved host name a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:01:53Z" - latency: 4.897619ms message: 'load-balancer-api-internal: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:00:53Z" - latency: 7.217874ms message: 'load-balancer-api-internal: resolved host name a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:00:53Z" - latency: 4.295696ms message: 'load-balancer-api-internal: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:59:53Z" - latency: 7.080032ms message: 'load-balancer-api-internal: resolved host name a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:59:53Z" - latency: 4.293225ms message: 'load-balancer-api-internal: tcp connection to a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:58:53Z" - latency: 8.114192ms message: 'load-balancer-api-internal: resolved host name a199ed2f638d24d2196b43bc86a33fcb-43076bb2d46fc8ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:58:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:20:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-74-to-network-check-target-ip-10-0-135-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-74.ec2.internal uid: 851c6b78-bb35-4a4d-b472-2e017c0c6027 resourceVersion: "32248" uid: 6cb083ee-9543-4c9a-9281-319abcab63e2 spec: sourcePod: network-check-source-989f8b8dc-96d87 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:27:53Z" message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.396822ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:02:53Z" - latency: 2.097924ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:01:53Z" - latency: 2.200906ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:00:53Z" - latency: 1.981289ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:59:53Z" - latency: 2.095097ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:58:53Z" - latency: 2.104838ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:57:53Z" - latency: 2.159754ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:53Z" - latency: 2.151605ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:53Z" - latency: 2.121382ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:53Z" - latency: 2.072301ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:20:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-74-to-network-check-target-ip-10-0-138-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-74.ec2.internal uid: 851c6b78-bb35-4a4d-b472-2e017c0c6027 resourceVersion: "32245" uid: 3e362167-f9f6-4548-b5cf-e6538532256f spec: sourcePod: network-check-source-989f8b8dc-96d87 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:27:53Z" message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.614612ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:02:53Z" - latency: 1.074733ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:01:53Z" - latency: 798.579µs message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:00:53Z" - latency: 925.566µs message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:59:53Z" - latency: 1.035841ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:58:53Z" - latency: 865.235µs message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:57:53Z" - latency: 1.077637ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:53Z" - latency: 915.19µs message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:53Z" - latency: 777.545µs message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:53Z" - latency: 1.182494ms message: 'network-check-target-ip-10-0-138-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:20:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-74-to-network-check-target-ip-10-0-142-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-74.ec2.internal uid: 851c6b78-bb35-4a4d-b472-2e017c0c6027 resourceVersion: "32246" uid: bace38c1-056c-406a-b58f-1d5c014c4294 spec: sourcePod: network-check-source-989f8b8dc-96d87 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:27:53Z" message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.399928ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:02:53Z" - latency: 2.498281ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:01:53Z" - latency: 2.513868ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:00:53Z" - latency: 2.35079ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:59:53Z" - latency: 2.27815ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:58:53Z" - latency: 1.980718ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:57:53Z" - latency: 2.068932ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:53Z" - latency: 2.21547ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:53Z" - latency: 2.334824ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:53Z" - latency: 2.376836ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:20:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-74-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-74.ec2.internal uid: 851c6b78-bb35-4a4d-b472-2e017c0c6027 resourceVersion: "32247" uid: c29b85bf-e5df-4423-98ff-d8a5e025b02d spec: sourcePod: network-check-source-989f8b8dc-96d87 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T02:26:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 963.71µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:02:53Z" - latency: 1.81548ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T03:02:53Z" - latency: 842.258µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:01:53Z" - latency: 1.896936ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T03:01:53Z" - latency: 916.258µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:00:53Z" - latency: 1.820492ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T03:00:53Z" - latency: 963.401µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:59:53Z" - latency: 1.748416ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:59:53Z" - latency: 1.042913ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:58:53Z" - latency: 1.709231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:58:53Z" kind: List metadata: resourceVersion: ""