apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.ec2.internal uid: 0ba09683-a4fb-4d8c-9480-605e6d17490a resourceVersion: "54976" uid: cfacf0c7-2dc9-48bf-9019-7de38862fc90 spec: sourcePod: network-check-source-989f8b8dc-mmdlr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T19:20:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.417771ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:06Z" - latency: 954.675µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:06Z" - latency: 839.692µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:06Z" - latency: 1.075747ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:06Z" - latency: 1.057494ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:44:06Z" - latency: 1.088541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:43:06Z" - latency: 923.444µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:42:06Z" - latency: 1.010413ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:41:06Z" - latency: 968.034µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:40:06Z" - latency: 1.168882ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.ec2.internal uid: 0ba09683-a4fb-4d8c-9480-605e6d17490a resourceVersion: "55952" uid: 62ec9132-4229-4ab1-8e9e-8fbe3a2af192 spec: sourcePod: network-check-source-989f8b8dc-mmdlr targetEndpoint: a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T19:19:06Z" message: 'load-balancer-api-external: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.201532ms message: 'load-balancer-api-external: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:49:06Z" - latency: 10.006159ms message: 'load-balancer-api-external: resolved host name a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:49:06Z" - latency: 4.481594ms message: 'load-balancer-api-external: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:06Z" - latency: 8.238636ms message: 'load-balancer-api-external: resolved host name a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:48:06Z" - latency: 4.643782ms message: 'load-balancer-api-external: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:06Z" - latency: 6.599046ms message: 'load-balancer-api-external: resolved host name a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:47:06Z" - latency: 3.751744ms message: 'load-balancer-api-external: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:06Z" - latency: 8.247811ms message: 'load-balancer-api-external: resolved host name a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:46:06Z" - latency: 3.841961ms message: 'load-balancer-api-external: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:06Z" - latency: 8.076807ms message: 'load-balancer-api-external: resolved host name a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:45:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.ec2.internal uid: 0ba09683-a4fb-4d8c-9480-605e6d17490a resourceVersion: "55951" uid: 6d4e8612-e4f3-46af-adbf-8c95158cfd61 spec: sourcePod: network-check-source-989f8b8dc-mmdlr targetEndpoint: a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T19:19:06Z" message: 'load-balancer-api-internal: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.231228ms message: 'load-balancer-api-internal: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:49:06Z" - latency: 9.941096ms message: 'load-balancer-api-internal: resolved host name a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:49:06Z" - latency: 4.584519ms message: 'load-balancer-api-internal: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:06Z" - latency: 8.15412ms message: 'load-balancer-api-internal: resolved host name a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:48:06Z" - latency: 4.57511ms message: 'load-balancer-api-internal: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:06Z" - latency: 6.91098ms message: 'load-balancer-api-internal: resolved host name a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:47:06Z" - latency: 4.739508ms message: 'load-balancer-api-internal: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:06Z" - latency: 8.296293ms message: 'load-balancer-api-internal: resolved host name a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:46:06Z" - latency: 3.778637ms message: 'load-balancer-api-internal: tcp connection to a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:06Z" - latency: 8.173092ms message: 'load-balancer-api-internal: resolved host name a16ac2d520aea43f5b27a1203c1ac49e-41e39ee888411818.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:45:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-network-check-target-ip-10-0-129-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.ec2.internal uid: 0ba09683-a4fb-4d8c-9480-605e6d17490a resourceVersion: "54973" uid: de2d3d35-c770-4a20-8049-85e76d08d0a1 spec: sourcePod: network-check-source-989f8b8dc-mmdlr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:20:06Z" message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.184789ms message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:06Z" - latency: 1.389293ms message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:06Z" - latency: 997.012µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:06Z" - latency: 1.096358ms message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:06Z" - latency: 748.137µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:44:06Z" - latency: 797.113µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:43:06Z" - latency: 1.07319ms message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:42:06Z" - latency: 807.463µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:41:06Z" - latency: 837.036µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:40:06Z" - latency: 992.603µs message: 'network-check-target-ip-10-0-129-72: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-network-check-target-ip-10-0-138-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.ec2.internal uid: 0ba09683-a4fb-4d8c-9480-605e6d17490a resourceVersion: "54974" uid: 275471df-39de-4465-bda2-5fadee2034ec spec: sourcePod: network-check-source-989f8b8dc-mmdlr targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:20:06Z" message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.411647ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:06Z" - latency: 2.395295ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:06Z" - latency: 2.478617ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:06Z" - latency: 2.14424ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:06Z" - latency: 2.22855ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:44:06Z" - latency: 2.296522ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:43:06Z" - latency: 1.942715ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:42:06Z" - latency: 1.970472ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:41:06Z" - latency: 2.457638ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:40:06Z" - latency: 2.337215ms message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-network-check-target-ip-10-0-142-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.ec2.internal uid: 0ba09683-a4fb-4d8c-9480-605e6d17490a resourceVersion: "54975" uid: cff91096-1a2c-4e63-b7db-74640d9233d4 spec: sourcePod: network-check-source-989f8b8dc-mmdlr targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:20:06Z" message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.464845ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:06Z" - latency: 2.216226ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:06Z" - latency: 1.772423ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:06Z" - latency: 1.897984ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:06Z" - latency: 2.045102ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:44:06Z" - latency: 1.842516ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:43:06Z" - latency: 1.97987ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:42:06Z" - latency: 1.747574ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:41:06Z" - latency: 2.034365ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:40:06Z" - latency: 1.912161ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:13:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-72-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-72.ec2.internal uid: 0ba09683-a4fb-4d8c-9480-605e6d17490a resourceVersion: "55950" uid: e929bff2-233a-4e91-8bc3-0a0e57f462ff spec: sourcePod: network-check-source-989f8b8dc-mmdlr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T19:19:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 867.244µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:49:06Z" - latency: 1.871311ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:49:06Z" - latency: 893.78µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:06Z" - latency: 1.745641ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:48:06Z" - latency: 796.715µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:06Z" - latency: 1.802408ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:47:06Z" - latency: 867.457µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:06Z" - latency: 1.79943ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:46:06Z" - latency: 1.010352ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:06Z" - latency: 1.788473ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:45:06Z" kind: List metadata: resourceVersion: ""