apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:48:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-45-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-45.us-west-1.compute.internal uid: 0dfcd854-b314-437f-b990-0942964ecb47 resourceVersion: "41812" uid: 80289d1d-f387-4c1d-a822-8fd569d05e52 spec: sourcePod: network-check-source-6f78d59f99-dl259 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T04:55:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.191544ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:09:38Z" - latency: 1.155985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:08:38Z" - latency: 1.251908ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:07:38Z" - latency: 1.269681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:06:38Z" - latency: 1.302417ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:05:38Z" - latency: 1.221277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:04:38Z" - latency: 1.395227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:03:38Z" - latency: 1.398593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:02:38Z" - latency: 1.704701ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:01:38Z" - latency: 2.535674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:00:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:48:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-45-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-45.us-west-1.compute.internal uid: 0dfcd854-b314-437f-b990-0942964ecb47 resourceVersion: "40099" uid: a5f18f1b-71a3-4527-ac0b-362e007381a6 spec: sourcePod: network-check-source-6f78d59f99-dl259 targetEndpoint: ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T04:54:38Z" message: 'load-balancer-api-external: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.157387ms message: 'load-balancer-api-external: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:06:38Z" - latency: 6.655177ms message: 'load-balancer-api-external: resolved host name ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:06:38Z" - latency: 53.611385ms message: 'load-balancer-api-external: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:05:38Z" - latency: 6.383466ms message: 'load-balancer-api-external: resolved host name ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:05:38Z" - latency: 52.945615ms message: 'load-balancer-api-external: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:04:38Z" - latency: 7.27249ms message: 'load-balancer-api-external: resolved host name ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:04:38Z" - latency: 54.871428ms message: 'load-balancer-api-external: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:03:38Z" - latency: 6.345044ms message: 'load-balancer-api-external: resolved host name ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:03:38Z" - latency: 53.69487ms message: 'load-balancer-api-external: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:02:38Z" - latency: 6.713904ms message: 'load-balancer-api-external: resolved host name ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:02:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:48:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-45-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-45.us-west-1.compute.internal uid: 0dfcd854-b314-437f-b990-0942964ecb47 resourceVersion: "40100" uid: 6ccf97a8-d037-4416-b201-0f64fce4db05 spec: sourcePod: network-check-source-6f78d59f99-dl259 targetEndpoint: ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T04:54:38Z" message: 'load-balancer-api-internal: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.086426ms message: 'load-balancer-api-internal: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:06:38Z" - latency: 6.55096ms message: 'load-balancer-api-internal: resolved host name ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:06:38Z" - latency: 53.575489ms message: 'load-balancer-api-internal: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:05:38Z" - latency: 6.475609ms message: 'load-balancer-api-internal: resolved host name ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:05:38Z" - latency: 52.847343ms message: 'load-balancer-api-internal: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:04:38Z" - latency: 7.178912ms message: 'load-balancer-api-internal: resolved host name ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:04:38Z" - latency: 54.952053ms message: 'load-balancer-api-internal: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:03:38Z" - latency: 6.362579ms message: 'load-balancer-api-internal: resolved host name ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:03:38Z" - latency: 53.749259ms message: 'load-balancer-api-internal: tcp connection to ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:02:38Z" - latency: 6.541642ms message: 'load-balancer-api-internal: resolved host name ad7f0a69d1aeb4fbea22a6fe43d5cdd1-3a8265abc582d153.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:02:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:48:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-45-to-network-check-target-ip-10-0-133-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-45.us-west-1.compute.internal uid: 0dfcd854-b314-437f-b990-0942964ecb47 resourceVersion: "41811" uid: 0e83aac3-2e43-4c67-ae09-e947aca0c87c spec: sourcePod: network-check-source-6f78d59f99-dl259 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T04:55:38Z" message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.414797ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:09:38Z" - latency: 2.536924ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:08:38Z" - latency: 2.333193ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:07:38Z" - latency: 2.632427ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:06:38Z" - latency: 3.232783ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:05:38Z" - latency: 2.52407ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:04:38Z" - latency: 2.828404ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:03:38Z" - latency: 2.627061ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:02:38Z" - latency: 2.199032ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:01:38Z" - latency: 3.631304ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:00:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:48:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-45-to-network-check-target-ip-10-0-135-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-45.us-west-1.compute.internal uid: 0dfcd854-b314-437f-b990-0942964ecb47 resourceVersion: "41808" uid: 0f461fcf-d69a-4c50-9a9a-6c80a14bde60 spec: sourcePod: network-check-source-6f78d59f99-dl259 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T04:55:38Z" message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.514275ms message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:09:38Z" - latency: 1.069781ms message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:08:38Z" - latency: 1.616217ms message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:07:38Z" - latency: 1.037289ms message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:06:38Z" - latency: 1.28541ms message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:05:38Z" - latency: 1.073885ms message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:04:38Z" - latency: 888.938µs message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:03:38Z" - latency: 1.547032ms message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:02:38Z" - latency: 970.143µs message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:01:38Z" - latency: 1.547415ms message: 'network-check-target-ip-10-0-135-45: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:00:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:48:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-45-to-network-check-target-ip-10-0-141-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-45.us-west-1.compute.internal uid: 0dfcd854-b314-437f-b990-0942964ecb47 resourceVersion: "41809" uid: b53f6336-2a1a-47cd-9227-605273217092 spec: sourcePod: network-check-source-6f78d59f99-dl259 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T04:55:38Z" message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.234383ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:09:38Z" - latency: 2.473601ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:08:38Z" - latency: 2.732475ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:07:38Z" - latency: 2.151077ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:06:38Z" - latency: 2.023314ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:05:38Z" - latency: 2.469105ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:04:38Z" - latency: 2.314615ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:03:38Z" - latency: 2.776945ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:02:38Z" - latency: 2.615503ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:01:38Z" - latency: 3.347127ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:00:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:48:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-45-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-45.us-west-1.compute.internal uid: 0dfcd854-b314-437f-b990-0942964ecb47 resourceVersion: "40095" uid: 9d8947d8-0e61-482c-98a3-b08d650144eb spec: sourcePod: network-check-source-6f78d59f99-dl259 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T04:54:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 943.913µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:06:38Z" - latency: 1.905954ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:06:38Z" - latency: 1.425504ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:05:38Z" - latency: 2.188549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:05:38Z" - latency: 1.188709ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:04:38Z" - latency: 2.740607ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:04:38Z" - latency: 901.424µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:03:38Z" - latency: 2.035606ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:03:38Z" - latency: 1.111095ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:02:38Z" - latency: 1.821628ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:02:38Z" kind: List metadata: resourceVersion: ""