apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T06:11:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-54-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-54.us-west-1.compute.internal uid: a65553c8-3856-460e-bad3-348de71cf255 resourceVersion: "136087" uid: 03c36486-9cf9-466a-bcd7-2b8dca959241 spec: sourcePod: network-check-source-6f78d59f99-bskfd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T06:18:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.974392ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:42:43Z" - latency: 839.556µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:41:43Z" - latency: 2.255325ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:40:43Z" - latency: 1.124951ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:39:43Z" - latency: 833.284µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:38:43Z" - latency: 1.237714ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:37:43Z" - latency: 1.095511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:36:43Z" - latency: 1.37805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:35:43Z" - latency: 876.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:34:43Z" - latency: 893.706µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:33:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T06:11:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-54-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-54.us-west-1.compute.internal uid: a65553c8-3856-460e-bad3-348de71cf255 resourceVersion: "135419" uid: 9a21ba33-cdde-4bff-9ce9-1368e5176509 spec: sourcePod: network-check-source-6f78d59f99-bskfd targetEndpoint: ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T06:17:43Z" message: 'load-balancer-api-external: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.775759ms message: 'load-balancer-api-external: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:41:43Z" - latency: 6.831015ms message: 'load-balancer-api-external: resolved host name ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:41:43Z" - latency: 58.625915ms message: 'load-balancer-api-external: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:40:43Z" - latency: 8.807186ms message: 'load-balancer-api-external: resolved host name ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:40:43Z" - latency: 54.613331ms message: 'load-balancer-api-external: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:39:43Z" - latency: 5.642902ms message: 'load-balancer-api-external: resolved host name ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:39:43Z" - latency: 56.192547ms message: 'load-balancer-api-external: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:38:43Z" - latency: 7.025621ms message: 'load-balancer-api-external: resolved host name ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:38:43Z" - latency: 54.504587ms message: 'load-balancer-api-external: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:37:43Z" - latency: 6.517543ms message: 'load-balancer-api-external: resolved host name ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:37:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T06:11:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-54-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-54.us-west-1.compute.internal uid: a65553c8-3856-460e-bad3-348de71cf255 resourceVersion: "135423" uid: a724817f-9510-4ea4-85d8-979315d1df83 spec: sourcePod: network-check-source-6f78d59f99-bskfd targetEndpoint: ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T06:17:43Z" message: 'load-balancer-api-internal: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 50.757768ms message: 'load-balancer-api-internal: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:41:43Z" - latency: 2.351105ms message: 'load-balancer-api-internal: resolved host name ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:41:43Z" - latency: 65.710689ms message: 'load-balancer-api-internal: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:40:43Z" - latency: 15.292692ms message: 'load-balancer-api-internal: resolved host name ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:40:43Z" - latency: 53.59385ms message: 'load-balancer-api-internal: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:39:43Z" - latency: 3.859002ms message: 'load-balancer-api-internal: resolved host name ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:39:43Z" - latency: 52.831904ms message: 'load-balancer-api-internal: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:38:43Z" - latency: 2.209203ms message: 'load-balancer-api-internal: resolved host name ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:38:43Z" - latency: 52.298112ms message: 'load-balancer-api-internal: tcp connection to ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:37:43Z" - latency: 2.350903ms message: 'load-balancer-api-internal: resolved host name ae23e5d867b4645df8e862367584a87b-ec09ebbe119c1d65.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:37:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T06:11:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-54-to-network-check-target-ip-10-0-130-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-54.us-west-1.compute.internal uid: a65553c8-3856-460e-bad3-348de71cf255 resourceVersion: "136085" uid: 5d57562b-8f8c-423e-8ab2-40bcd414db42 spec: sourcePod: network-check-source-6f78d59f99-bskfd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T06:18:43Z" message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.756586ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:42:43Z" - latency: 1.061713ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:41:43Z" - latency: 2.917605ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:40:43Z" - latency: 1.166241ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:39:43Z" - latency: 1.111414ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:38:43Z" - latency: 1.430999ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:37:43Z" - latency: 1.040653ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:36:43Z" - latency: 2.719608ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:35:43Z" - latency: 1.058642ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:34:43Z" - latency: 1.334704ms message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:33:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T06:11:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-54-to-network-check-target-ip-10-0-138-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-54.us-west-1.compute.internal uid: a65553c8-3856-460e-bad3-348de71cf255 resourceVersion: "136086" uid: 0cbfb726-0ff8-4ab9-9753-adcfeca753eb spec: sourcePod: network-check-source-6f78d59f99-bskfd targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T06:18:43Z" message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.640103ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:42:43Z" - latency: 1.845728ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:41:43Z" - latency: 3.674923ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:40:43Z" - latency: 1.839476ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:39:43Z" - latency: 1.961897ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:38:43Z" - latency: 2.074974ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:37:43Z" - latency: 2.207256ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:36:43Z" - latency: 2.529141ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:35:43Z" - latency: 2.204024ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:34:43Z" - latency: 1.772237ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:33:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T06:11:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-54-to-network-check-target-ip-10-0-140-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-54.us-west-1.compute.internal uid: a65553c8-3856-460e-bad3-348de71cf255 resourceVersion: "136084" uid: 758484bb-665b-488b-8cea-2d799ae97047 spec: sourcePod: network-check-source-6f78d59f99-bskfd targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T06:18:43Z" message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.487705ms message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:42:43Z" - latency: 1.924142ms message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:41:43Z" - latency: 3.324467ms message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:40:43Z" - latency: 2.036991ms message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:39:43Z" - latency: 1.987322ms message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:38:43Z" - latency: 2.178126ms message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:37:43Z" - latency: 2.168284ms message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:36:43Z" - latency: 2.447641ms message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:35:43Z" - latency: 2.077627ms message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:34:43Z" - latency: 2.320087ms message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:33:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T06:11:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-54-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-54.us-west-1.compute.internal uid: a65553c8-3856-460e-bad3-348de71cf255 resourceVersion: "135427" uid: 106e654e-758a-4b0a-a3ae-e3ebb5161ab5 spec: sourcePod: network-check-source-6f78d59f99-bskfd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T06:17:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.025555ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:41:43Z" - latency: 551.483µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T07:41:43Z" - latency: 4.95755ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:40:43Z" - latency: 8.742892ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T07:40:43Z" - latency: 794.289µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:39:43Z" - latency: 510.189µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T07:39:43Z" - latency: 858.635µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:38:43Z" - latency: 556.968µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T07:38:43Z" - latency: 767.651µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:37:43Z" - latency: 669.501µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T07:37:43Z" kind: List metadata: resourceVersion: ""