apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T23:30:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-239-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-239.us-east-2.compute.internal uid: 486e0c0e-6e31-4016-b58b-9527b11ceb80 resourceVersion: "231280" uid: b69c7af5-c9a1-4a00-89cb-21f652682ab5 spec: sourcePod: network-check-source-6f78d59f99-xr79v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T23:37:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.035197ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:01:16Z" - latency: 1.01536ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:00:16Z" - latency: 1.304574ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:59:16Z" - latency: 1.241886ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:58:16Z" - latency: 986.104µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:57:16Z" - latency: 1.32796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:56:16Z" - latency: 1.443015ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:55:16Z" - latency: 1.105638ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:54:16Z" - latency: 1.336227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:53:16Z" - latency: 1.397824ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:52:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T23:30:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-239-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-239.us-east-2.compute.internal uid: 486e0c0e-6e31-4016-b58b-9527b11ceb80 resourceVersion: "235280" uid: c04c79dd-ffd9-43a9-bdb5-4810175831bf spec: sourcePod: network-check-source-6f78d59f99-xr79v targetEndpoint: aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T23:36:16Z" message: 'load-balancer-api-external: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.602167ms message: 'load-balancer-api-external: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:06:16Z" - latency: 7.091464ms message: 'load-balancer-api-external: resolved host name aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:06:16Z" - latency: 4.654809ms message: 'load-balancer-api-external: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:05:16Z" - latency: 8.048333ms message: 'load-balancer-api-external: resolved host name aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:05:16Z" - latency: 5.372117ms message: 'load-balancer-api-external: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:04:16Z" - latency: 55.060296ms message: 'load-balancer-api-external: resolved host name aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:04:16Z" - latency: 4.450135ms message: 'load-balancer-api-external: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:03:16Z" - latency: 6.719264ms message: 'load-balancer-api-external: resolved host name aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:03:16Z" - latency: 5.329847ms message: 'load-balancer-api-external: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:02:16Z" - latency: 7.435614ms message: 'load-balancer-api-external: resolved host name aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:02:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T23:30:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-239-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-239.us-east-2.compute.internal uid: 486e0c0e-6e31-4016-b58b-9527b11ceb80 resourceVersion: "235281" uid: 7523529f-0502-46bb-94e0-68dd3b0a688d spec: sourcePod: network-check-source-6f78d59f99-xr79v targetEndpoint: aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T23:36:16Z" message: 'load-balancer-api-internal: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.613017ms message: 'load-balancer-api-internal: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:06:16Z" - latency: 7.040089ms message: 'load-balancer-api-internal: resolved host name aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:06:16Z" - latency: 4.66949ms message: 'load-balancer-api-internal: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:05:16Z" - latency: 8.163148ms message: 'load-balancer-api-internal: resolved host name aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:05:16Z" - latency: 6.056309ms message: 'load-balancer-api-internal: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:04:16Z" - latency: 55.854287ms message: 'load-balancer-api-internal: resolved host name aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:04:16Z" - latency: 4.956586ms message: 'load-balancer-api-internal: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:03:16Z" - latency: 6.788881ms message: 'load-balancer-api-internal: resolved host name aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:03:16Z" - latency: 4.559665ms message: 'load-balancer-api-internal: tcp connection to aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:02:16Z" - latency: 7.523305ms message: 'load-balancer-api-internal: resolved host name aebc58e3c82194faf95246fa16098fa7-4885fe49feab1b49.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T01:02:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T23:30:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-239-to-network-check-target-ip-10-0-138-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-239.us-east-2.compute.internal uid: 486e0c0e-6e31-4016-b58b-9527b11ceb80 resourceVersion: "231278" uid: c82e22b6-eeaa-4733-88a5-f01caf78a6e5 spec: sourcePod: network-check-source-6f78d59f99-xr79v targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T23:37:16Z" message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.570759ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:01:16Z" - latency: 1.920562ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:00:16Z" - latency: 2.317779ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:59:16Z" - latency: 2.166427ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:58:16Z" - latency: 1.787128ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:57:16Z" - latency: 1.984558ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:56:16Z" - latency: 2.10454ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:55:16Z" - latency: 2.255178ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:54:16Z" - latency: 1.61823ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:53:16Z" - latency: 2.094733ms message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:52:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T23:30:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-239-to-network-check-target-ip-10-0-138-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-239.us-east-2.compute.internal uid: 486e0c0e-6e31-4016-b58b-9527b11ceb80 resourceVersion: "231277" uid: a1605347-be1d-40a1-af93-6c99b21d5efb spec: sourcePod: network-check-source-6f78d59f99-xr79v targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T23:37:16Z" message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.129875ms message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:01:16Z" - latency: 1.235668ms message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:00:16Z" - latency: 1.694667ms message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:59:16Z" - latency: 946.855µs message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:58:16Z" - latency: 970.99µs message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:57:16Z" - latency: 987.998µs message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:56:16Z" - latency: 1.788155ms message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:55:16Z" - latency: 1.37079ms message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:54:16Z" - latency: 918.621µs message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:53:16Z" - latency: 1.225389ms message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:52:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T23:30:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-239-to-network-check-target-ip-10-0-143-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-239.us-east-2.compute.internal uid: 486e0c0e-6e31-4016-b58b-9527b11ceb80 resourceVersion: "231386" uid: 3489c76d-bbc9-47f4-9da5-ceaaf53d9cdc spec: sourcePod: network-check-source-6f78d59f99-xr79v targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T23:37:25Z" message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.93965ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:01:25Z" - latency: 2.525315ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:00:25Z" - latency: 2.311997ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:59:25Z" - latency: 2.310399ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:58:25Z" - latency: 1.935865ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:57:25Z" - latency: 2.465915ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:56:25Z" - latency: 2.409528ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:55:25Z" - latency: 791.914µs message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:54:25Z" - latency: 960.004µs message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:53:25Z" - latency: 5.979508ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T00:52:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T23:30:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-239-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-239.us-east-2.compute.internal uid: 486e0c0e-6e31-4016-b58b-9527b11ceb80 resourceVersion: "235279" uid: beb261fe-0ccb-4179-bff5-423aad44b47d spec: sourcePod: network-check-source-6f78d59f99-xr79v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T23:36:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.056489ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:06:16Z" - latency: 1.78231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:06:16Z" - latency: 1.947512ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:05:16Z" - latency: 1.957001ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:05:16Z" - latency: 10.866021ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:04:16Z" - latency: 38.684334ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:04:16Z" - latency: 806.869µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:03:16Z" - latency: 1.703087ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:03:16Z" - latency: 908.293µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T01:02:16Z" - latency: 2.315898ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T01:02:16Z" kind: List metadata: resourceVersion: ""