apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T12:25:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-76-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-76.us-west-2.compute.internal uid: cbf47aaf-9bb0-4e7a-8810-a0e911fcf670 resourceVersion: "101088" uid: 6160fb08-4ac7-442b-82b5-4b93f63825ae spec: sourcePod: network-check-source-6f78d59f99-nwjwn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T12:32:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.391943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:28:14Z" - latency: 1.25155ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:27:14Z" - latency: 1.360107ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:26:14Z" - latency: 1.794958ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:25:14Z" - latency: 1.214253ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:24:14Z" - latency: 5.95901ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:23:14Z" - latency: 4.570781ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:22:14Z" - latency: 1.466361ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:21:14Z" - latency: 1.027679ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:20:14Z" - latency: 1.216013ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:19:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T12:25:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-76-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-76.us-west-2.compute.internal uid: cbf47aaf-9bb0-4e7a-8810-a0e911fcf670 resourceVersion: "98263" uid: 7c95dc09-d081-4849-8392-092ba6657f69 spec: sourcePod: network-check-source-6f78d59f99-nwjwn targetEndpoint: abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T12:31:14Z" message: 'load-balancer-api-external: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.338781ms message: 'load-balancer-api-external: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:25:14Z" - latency: 6.856914ms message: 'load-balancer-api-external: resolved host name abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T13:25:14Z" - latency: 51.559693ms message: 'load-balancer-api-external: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:24:14Z" - latency: 7.010842ms message: 'load-balancer-api-external: resolved host name abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T13:24:14Z" - latency: 51.673522ms message: 'load-balancer-api-external: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:23:14Z" - latency: 13.469425ms message: 'load-balancer-api-external: resolved host name abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T13:23:14Z" - latency: 57.496351ms message: 'load-balancer-api-external: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:22:14Z" - latency: 46.511933ms message: 'load-balancer-api-external: resolved host name abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T13:22:14Z" - latency: 55.30367ms message: 'load-balancer-api-external: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:21:14Z" - latency: 9.167029ms message: 'load-balancer-api-external: resolved host name abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T13:21:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T12:25:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-76-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-76.us-west-2.compute.internal uid: cbf47aaf-9bb0-4e7a-8810-a0e911fcf670 resourceVersion: "98262" uid: e1f2a0d8-9fd0-4a5f-bd7a-1ae4f399da9c spec: sourcePod: network-check-source-6f78d59f99-nwjwn targetEndpoint: abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T12:31:14Z" message: 'load-balancer-api-internal: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.323959ms message: 'load-balancer-api-internal: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:25:14Z" - latency: 6.965755ms message: 'load-balancer-api-internal: resolved host name abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T13:25:14Z" - latency: 54.759022ms message: 'load-balancer-api-internal: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:24:14Z" - latency: 7.122397ms message: 'load-balancer-api-internal: resolved host name abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T13:24:14Z" - latency: 51.12578ms message: 'load-balancer-api-internal: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:23:14Z" - latency: 18.08231ms message: 'load-balancer-api-internal: resolved host name abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T13:23:14Z" - latency: 53.389403ms message: 'load-balancer-api-internal: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:22:14Z" - latency: 46.972796ms message: 'load-balancer-api-internal: resolved host name abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T13:22:14Z" - latency: 55.106169ms message: 'load-balancer-api-internal: tcp connection to abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:21:14Z" - latency: 9.259949ms message: 'load-balancer-api-internal: resolved host name abc0a0f33396342028b8d407fe49f7f2-4917c070ca97fa5c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T13:21:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T12:25:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-76-to-network-check-target-ip-10-0-138-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-76.us-west-2.compute.internal uid: cbf47aaf-9bb0-4e7a-8810-a0e911fcf670 resourceVersion: "101083" uid: e587d4fb-1aef-4921-a5bb-8fc24bcd6b77 spec: sourcePod: network-check-source-6f78d59f99-nwjwn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T12:32:14Z" message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.151182ms message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:28:14Z" - latency: 1.100645ms message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:27:14Z" - latency: 1.117612ms message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:26:14Z" - latency: 1.893067ms message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:25:14Z" - latency: 1.477678ms message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:24:14Z" - latency: 5.219139ms message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:23:14Z" - latency: 4.347598ms message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:22:14Z" - latency: 1.7256ms message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:21:14Z" - latency: 1.176413ms message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:20:14Z" - latency: 1.2746ms message: 'network-check-target-ip-10-0-138-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:19:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T12:25:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-76-to-network-check-target-ip-10-0-140-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-76.us-west-2.compute.internal uid: cbf47aaf-9bb0-4e7a-8810-a0e911fcf670 resourceVersion: "101084" uid: af498419-40f7-47cb-815b-cdaed6131d55 spec: sourcePod: network-check-source-6f78d59f99-nwjwn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T12:32:14Z" message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.108437ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:28:14Z" - latency: 2.224728ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:27:14Z" - latency: 2.240321ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:26:14Z" - latency: 2.135124ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:25:14Z" - latency: 1.938648ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:24:14Z" - latency: 4.563427ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:23:14Z" - latency: 4.988614ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:22:14Z" - latency: 2.182586ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:21:14Z" - latency: 2.091231ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:20:14Z" - latency: 2.17733ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:19:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T12:25:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-76-to-network-check-target-ip-10-0-140-174 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-76.us-west-2.compute.internal uid: cbf47aaf-9bb0-4e7a-8810-a0e911fcf670 resourceVersion: "101085" uid: e24c84c8-d9e2-45cd-afbe-e1cfaf57506d spec: sourcePod: network-check-source-6f78d59f99-nwjwn targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T12:32:14Z" message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.534136ms message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:28:14Z" - latency: 2.315194ms message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:27:14Z" - latency: 2.685126ms message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:26:14Z" - latency: 2.712043ms message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:25:14Z" - latency: 2.575252ms message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:24:14Z" - latency: 7.350682ms message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:23:14Z" - latency: 13.418109ms message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:22:14Z" - latency: 2.673214ms message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:21:14Z" - latency: 2.591192ms message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:20:14Z" - latency: 2.708315ms message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:19:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T12:25:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-76-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-76.us-west-2.compute.internal uid: cbf47aaf-9bb0-4e7a-8810-a0e911fcf670 resourceVersion: "98260" uid: 5424bab6-5445-4318-8ac1-731fe7ed2877 spec: sourcePod: network-check-source-6f78d59f99-nwjwn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T12:31:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.110909ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:25:14Z" - latency: 2.386288ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T13:25:14Z" - latency: 891.517µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:24:14Z" - latency: 1.994858ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T13:24:14Z" - latency: 2.771385ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:23:14Z" - latency: 10.076408ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T13:23:14Z" - latency: 4.263793ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:22:14Z" - latency: 13.635904ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T13:22:14Z" - latency: 1.152515ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T13:21:14Z" - latency: 1.9414ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T13:21:14Z" kind: List metadata: resourceVersion: ""