apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-195-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-195.us-east-2.compute.internal uid: 11223cec-c9cf-421c-87a9-060ca0af4dd9 resourceVersion: "107020" uid: 761b6477-2edf-432d-a854-8fbc10dd46f3 spec: sourcePod: network-check-source-6f78d59f99-tdmc8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:36:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.200011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:16Z" - latency: 1.468499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:16Z" - latency: 1.168321ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:16Z" - latency: 1.643193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:16Z" - latency: 1.208406ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:16Z" - latency: 1.401236ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:06:16Z" - latency: 1.336922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:05:16Z" - latency: 5.023729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:04:16Z" - latency: 1.612068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:03:16Z" - latency: 1.203157ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:02:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-195-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-195.us-east-2.compute.internal uid: 11223cec-c9cf-421c-87a9-060ca0af4dd9 resourceVersion: "107022" uid: ea704134-aa89-4ba1-9725-4afc018faaca spec: sourcePod: network-check-source-6f78d59f99-tdmc8 targetEndpoint: a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:35:16Z" message: 'load-balancer-api-external: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.97491ms message: 'load-balancer-api-external: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:16Z" - latency: 7.319022ms message: 'load-balancer-api-external: resolved host name a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:11:16Z" - latency: 5.617502ms message: 'load-balancer-api-external: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:16Z" - latency: 7.115234ms message: 'load-balancer-api-external: resolved host name a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:10:16Z" - latency: 5.491596ms message: 'load-balancer-api-external: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:16Z" - latency: 6.664185ms message: 'load-balancer-api-external: resolved host name a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:09:16Z" - latency: 7.469081ms message: 'load-balancer-api-external: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:16Z" - latency: 9.367263ms message: 'load-balancer-api-external: resolved host name a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:08:16Z" - latency: 6.018733ms message: 'load-balancer-api-external: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:16Z" - latency: 7.210912ms message: 'load-balancer-api-external: resolved host name a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:07:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-195-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-195.us-east-2.compute.internal uid: 11223cec-c9cf-421c-87a9-060ca0af4dd9 resourceVersion: "107021" uid: 44623230-49a6-4fde-93fa-a75c5a13220d spec: sourcePod: network-check-source-6f78d59f99-tdmc8 targetEndpoint: a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:35:16Z" message: 'load-balancer-api-internal: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.934881ms message: 'load-balancer-api-internal: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:16Z" - latency: 7.267244ms message: 'load-balancer-api-internal: resolved host name a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:11:16Z" - latency: 4.781987ms message: 'load-balancer-api-internal: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:16Z" - latency: 7.156623ms message: 'load-balancer-api-internal: resolved host name a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:10:16Z" - latency: 25.571717ms message: 'load-balancer-api-internal: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:16Z" - latency: 6.743787ms message: 'load-balancer-api-internal: resolved host name a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:09:16Z" - latency: 7.480288ms message: 'load-balancer-api-internal: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:16Z" - latency: 9.354449ms message: 'load-balancer-api-internal: resolved host name a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:08:16Z" - latency: 5.353569ms message: 'load-balancer-api-internal: tcp connection to a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:16Z" - latency: 7.255146ms message: 'load-balancer-api-internal: resolved host name a3f405372e77a444d988d55861b24e9d-1ba35f027eee96bc.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:07:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-195-to-network-check-target-ip-10-0-129-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-195.us-east-2.compute.internal uid: 11223cec-c9cf-421c-87a9-060ca0af4dd9 resourceVersion: "107018" uid: 3eb3f743-1a20-4009-b2a4-fa92025655ac spec: sourcePod: network-check-source-6f78d59f99-tdmc8 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:36:16Z" message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.43035ms message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:16Z" - latency: 1.361346ms message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:16Z" - latency: 1.272675ms message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:16Z" - latency: 1.997934ms message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:16Z" - latency: 1.079477ms message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:16Z" - latency: 1.73188ms message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:06:16Z" - latency: 1.44448ms message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:05:16Z" - latency: 20.503158ms message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:04:16Z" - latency: 1.518353ms message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:03:16Z" - latency: 1.023104ms message: 'network-check-target-ip-10-0-129-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:02:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:29:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-195-to-network-check-target-ip-10-0-137-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-195.us-east-2.compute.internal uid: 11223cec-c9cf-421c-87a9-060ca0af4dd9 resourceVersion: "107591" uid: 9104967e-b126-4eb1-b87c-f94fd6589f79 spec: sourcePod: network-check-source-6f78d59f99-tdmc8 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:36:32Z" message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.498088ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:32Z" - latency: 2.523348ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:32Z" - latency: 2.447189ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:32Z" - latency: 4.336934ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:32Z" - latency: 3.287342ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:32Z" - latency: 2.641538ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:06:32Z" - latency: 2.504273ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:05:32Z" - latency: 2.138121ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:04:32Z" - latency: 1.899048ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:03:32Z" - latency: 12.975822ms message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:02:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:29:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-195-to-network-check-target-ip-10-0-140-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-195.us-east-2.compute.internal uid: 11223cec-c9cf-421c-87a9-060ca0af4dd9 resourceVersion: "107416" uid: 5929de56-c1d7-4282-b074-1ea9078dd35a spec: sourcePod: network-check-source-6f78d59f99-tdmc8 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:36:27Z" message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.701822ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:27Z" - latency: 2.492265ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:27Z" - latency: 2.591652ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:27Z" - latency: 2.476154ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:27Z" - latency: 2.255205ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:27Z" - latency: 2.122393ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:06:27Z" - latency: 2.279262ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:05:27Z" - latency: 2.244512ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:04:27Z" - latency: 2.359807ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:03:27Z" - latency: 2.468578ms message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:02:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:29:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-195-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-195.us-east-2.compute.internal uid: 11223cec-c9cf-421c-87a9-060ca0af4dd9 resourceVersion: "107019" uid: 1072c1f9-c98e-4f4d-974a-b8ba6b5ba1d0 spec: sourcePod: network-check-source-6f78d59f99-tdmc8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:35:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.978218ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:16Z" - latency: 1.827465ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:11:16Z" - latency: 2.457028ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:16Z" - latency: 1.785676ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:10:16Z" - latency: 2.234368ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:16Z" - latency: 1.902912ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:09:16Z" - latency: 2.312795ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:16Z" - latency: 2.516726ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:08:16Z" - latency: 817.29µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:16Z" - latency: 2.065421ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:07:16Z" kind: List metadata: resourceVersion: ""