apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T09:49:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-110-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-110.ec2.internal uid: 242efd0a-4a25-4eab-9726-00e7f1a8ddf2 resourceVersion: "54588" uid: 84b124e0-2cae-4c48-b88d-22e89019a3b7 spec: sourcePod: network-check-source-989f8b8dc-5lgcj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-03T09:56:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.17884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:24:52Z" - latency: 1.166434ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:23:52Z" - latency: 1.001344ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:22:52Z" - latency: 916.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:21:52Z" - latency: 1.781494ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:20:52Z" - latency: 940.247µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:19:52Z" - latency: 875.747µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:18:52Z" - latency: 1.215054ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:17:52Z" - latency: 949.806µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:16:52Z" - latency: 1.282909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:15:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T09:49:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-110-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-110.ec2.internal uid: 242efd0a-4a25-4eab-9726-00e7f1a8ddf2 resourceVersion: "55623" uid: 4aae4efb-e6d0-4aef-93b9-589d58c8b820 spec: sourcePod: network-check-source-989f8b8dc-5lgcj targetEndpoint: a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-03T09:55:52Z" message: 'load-balancer-api-external: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.196405ms message: 'load-balancer-api-external: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:25:52Z" - latency: 9.690724ms message: 'load-balancer-api-external: resolved host name a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T10:25:52Z" - latency: 5.31873ms message: 'load-balancer-api-external: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:24:52Z" - latency: 9.208281ms message: 'load-balancer-api-external: resolved host name a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T10:24:52Z" - latency: 3.705701ms message: 'load-balancer-api-external: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:23:52Z" - latency: 6.91412ms message: 'load-balancer-api-external: resolved host name a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T10:23:52Z" - latency: 4.236705ms message: 'load-balancer-api-external: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:22:52Z" - latency: 7.315975ms message: 'load-balancer-api-external: resolved host name a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T10:22:52Z" - latency: 4.774117ms message: 'load-balancer-api-external: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:21:52Z" - latency: 6.807824ms message: 'load-balancer-api-external: resolved host name a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T10:21:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T09:49:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-110-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-110.ec2.internal uid: 242efd0a-4a25-4eab-9726-00e7f1a8ddf2 resourceVersion: "55622" uid: 18d2f467-75c7-4394-a91b-5783a0c4355d spec: sourcePod: network-check-source-989f8b8dc-5lgcj targetEndpoint: a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-03T09:55:52Z" message: 'load-balancer-api-internal: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.076484ms message: 'load-balancer-api-internal: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:25:52Z" - latency: 9.752345ms message: 'load-balancer-api-internal: resolved host name a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T10:25:52Z" - latency: 5.329041ms message: 'load-balancer-api-internal: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:24:52Z" - latency: 9.179905ms message: 'load-balancer-api-internal: resolved host name a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T10:24:52Z" - latency: 3.701029ms message: 'load-balancer-api-internal: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:23:52Z" - latency: 6.883136ms message: 'load-balancer-api-internal: resolved host name a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T10:23:52Z" - latency: 4.245404ms message: 'load-balancer-api-internal: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:22:52Z" - latency: 7.421783ms message: 'load-balancer-api-internal: resolved host name a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T10:22:52Z" - latency: 4.782038ms message: 'load-balancer-api-internal: tcp connection to a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:21:52Z" - latency: 6.856298ms message: 'load-balancer-api-internal: resolved host name a47d8769295fa412a8db6b924820a6f6-736b7a5fd0f46e16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T10:21:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T09:49:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-110-to-network-check-target-ip-10-0-131-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-110.ec2.internal uid: 242efd0a-4a25-4eab-9726-00e7f1a8ddf2 resourceVersion: "54586" uid: 2ca3fe8d-e495-468c-ace7-a39f00d5387d spec: sourcePod: network-check-source-989f8b8dc-5lgcj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-03T09:56:52Z" message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.990362ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:24:52Z" - latency: 1.818373ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:23:52Z" - latency: 1.843483ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:22:52Z" - latency: 1.662244ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:21:52Z" - latency: 1.571877ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:20:52Z" - latency: 1.944655ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:19:52Z" - latency: 1.595317ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:18:52Z" - latency: 1.87489ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:17:52Z" - latency: 1.925074ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:16:52Z" - latency: 1.609149ms message: 'network-check-target-ip-10-0-131-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:15:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T09:49:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-110-to-network-check-target-ip-10-0-138-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-110.ec2.internal uid: 242efd0a-4a25-4eab-9726-00e7f1a8ddf2 resourceVersion: "54585" uid: f4ef05b6-14a9-4049-99f9-e9a04c9a4ea6 spec: sourcePod: network-check-source-989f8b8dc-5lgcj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-03T09:56:52Z" message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.328578ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:24:52Z" - latency: 724.113µs message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:23:52Z" - latency: 854.085µs message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:22:52Z" - latency: 1.011516ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:21:52Z" - latency: 762.34µs message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:20:52Z" - latency: 1.110515ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:19:52Z" - latency: 1.535643ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:18:52Z" - latency: 776.792µs message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:17:52Z" - latency: 784.388µs message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:16:52Z" - latency: 1.34023ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:15:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T09:49:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-110-to-network-check-target-ip-10-0-138-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-110.ec2.internal uid: 242efd0a-4a25-4eab-9726-00e7f1a8ddf2 resourceVersion: "54587" uid: c81e2399-11b1-400e-be6f-80583f1c754d spec: sourcePod: network-check-source-989f8b8dc-5lgcj targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-03T09:56:52Z" message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.187123ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:24:52Z" - latency: 1.977074ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:23:52Z" - latency: 2.158037ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:22:52Z" - latency: 1.936252ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:21:52Z" - latency: 1.924522ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:20:52Z" - latency: 2.017875ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:19:52Z" - latency: 2.173501ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:18:52Z" - latency: 2.478223ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:17:52Z" - latency: 2.204787ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:16:52Z" - latency: 2.086752ms message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:15:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-03T09:49:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-110-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-110.ec2.internal uid: 242efd0a-4a25-4eab-9726-00e7f1a8ddf2 resourceVersion: "55621" uid: c3b53e9c-7e3a-4250-84e6-e62369ff0414 spec: sourcePod: network-check-source-989f8b8dc-5lgcj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-03T09:55:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 897.921µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:25:52Z" - latency: 1.738145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T10:25:52Z" - latency: 1.221561ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:24:52Z" - latency: 1.681155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T10:24:52Z" - latency: 953.309µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:23:52Z" - latency: 1.740963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T10:23:52Z" - latency: 958.996µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:22:52Z" - latency: 1.865696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T10:22:52Z" - latency: 793.337µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T10:21:52Z" - latency: 1.807696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T10:21:52Z" kind: List metadata: resourceVersion: ""