apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:06:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-28-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-28.ec2.internal uid: e209ee52-da83-4024-a66f-6895608c6f13 resourceVersion: "55333" uid: c42d3989-be71-4f14-bb67-5662f3b47621 spec: sourcePod: network-check-source-869dcfcdcd-7d8g4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T11:13:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.025742ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:49Z" - latency: 1.070711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:49Z" - latency: 1.179591ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:49Z" - latency: 1.178314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:49Z" - latency: 988.106µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:37:49Z" - latency: 1.155901ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:36:49Z" - latency: 1.464123ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:35:49Z" - latency: 1.010588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:34:49Z" - latency: 1.496469ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:33:49Z" - latency: 961.012µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:32:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:06:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-28-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-28.ec2.internal uid: e209ee52-da83-4024-a66f-6895608c6f13 resourceVersion: "56476" uid: 61b3389f-4ca3-4e32-8bed-73e6b553122a spec: sourcePod: network-check-source-869dcfcdcd-7d8g4 targetEndpoint: a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T11:12:49Z" message: 'load-balancer-api-external: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.787275ms message: 'load-balancer-api-external: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:42:49Z" - latency: 10.197735ms message: 'load-balancer-api-external: resolved host name a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:42:49Z" - latency: 3.653464ms message: 'load-balancer-api-external: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:49Z" - latency: 6.93225ms message: 'load-balancer-api-external: resolved host name a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:41:49Z" - latency: 4.810848ms message: 'load-balancer-api-external: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:49Z" - latency: 8.483184ms message: 'load-balancer-api-external: resolved host name a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:40:49Z" - latency: 5.931238ms message: 'load-balancer-api-external: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:49Z" - latency: 11.375971ms message: 'load-balancer-api-external: resolved host name a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:39:49Z" - latency: 3.87548ms message: 'load-balancer-api-external: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:49Z" - latency: 6.963492ms message: 'load-balancer-api-external: resolved host name a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:38:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:06:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-28-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-28.ec2.internal uid: e209ee52-da83-4024-a66f-6895608c6f13 resourceVersion: "56477" uid: 8ea6e3bd-dde8-45fa-afed-24dc874adcf3 spec: sourcePod: network-check-source-869dcfcdcd-7d8g4 targetEndpoint: a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T11:12:49Z" message: 'load-balancer-api-internal: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.610702ms message: 'load-balancer-api-internal: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:42:49Z" - latency: 10.167741ms message: 'load-balancer-api-internal: resolved host name a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:42:49Z" - latency: 4.953607ms message: 'load-balancer-api-internal: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:49Z" - latency: 6.988095ms message: 'load-balancer-api-internal: resolved host name a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:41:49Z" - latency: 4.844039ms message: 'load-balancer-api-internal: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:49Z" - latency: 8.508934ms message: 'load-balancer-api-internal: resolved host name a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:40:49Z" - latency: 5.907971ms message: 'load-balancer-api-internal: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:49Z" - latency: 11.478234ms message: 'load-balancer-api-internal: resolved host name a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:39:49Z" - latency: 3.930137ms message: 'load-balancer-api-internal: tcp connection to a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:49Z" - latency: 6.88153ms message: 'load-balancer-api-internal: resolved host name a29e2c47e6dce40d58bfcfffecc1cce3-b33f661723ae5215.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:38:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:06:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-28-to-network-check-target-ip-10-0-129-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-28.ec2.internal uid: e209ee52-da83-4024-a66f-6895608c6f13 resourceVersion: "55330" uid: a4660295-63b8-41bb-b723-56f415b2e430 spec: sourcePod: network-check-source-869dcfcdcd-7d8g4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T11:13:49Z" message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.366339ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:49Z" - latency: 1.61255ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:49Z" - latency: 997.775µs message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:49Z" - latency: 1.677728ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:49Z" - latency: 735.632µs message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:37:49Z" - latency: 1.305858ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:36:49Z" - latency: 2.406151ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:35:49Z" - latency: 895.782µs message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:34:49Z" - latency: 997.298µs message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:33:49Z" - latency: 977.063µs message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:32:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:06:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-28-to-network-check-target-ip-10-0-132-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-28.ec2.internal uid: e209ee52-da83-4024-a66f-6895608c6f13 resourceVersion: "55331" uid: 47db6b89-2d55-42d4-8990-3c39df237ea6 spec: sourcePod: network-check-source-869dcfcdcd-7d8g4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T11:13:49Z" message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.793887ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:49Z" - latency: 2.587864ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:49Z" - latency: 2.453909ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:49Z" - latency: 2.488674ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:49Z" - latency: 1.994872ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:37:49Z" - latency: 2.866957ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:36:49Z" - latency: 2.757232ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:35:49Z" - latency: 2.298392ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:34:49Z" - latency: 2.901738ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:33:49Z" - latency: 2.632803ms message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:32:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:06:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-28-to-network-check-target-ip-10-0-142-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-28.ec2.internal uid: e209ee52-da83-4024-a66f-6895608c6f13 resourceVersion: "55332" uid: 8c6177af-f2bf-4d36-be3a-2c29a016cb16 spec: sourcePod: network-check-source-869dcfcdcd-7d8g4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T11:13:49Z" message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.350838ms message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:49Z" - latency: 2.272807ms message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:49Z" - latency: 2.256382ms message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:49Z" - latency: 2.242343ms message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:49Z" - latency: 2.270897ms message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:37:49Z" - latency: 2.10907ms message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:36:49Z" - latency: 2.315491ms message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:35:49Z" - latency: 2.228112ms message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:34:49Z" - latency: 2.445838ms message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:33:49Z" - latency: 2.211311ms message: 'network-check-target-ip-10-0-142-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:32:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:06:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-28-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-28.ec2.internal uid: e209ee52-da83-4024-a66f-6895608c6f13 resourceVersion: "56475" uid: 0d55c16c-5d59-439e-a105-4a347125f575 spec: sourcePod: network-check-source-869dcfcdcd-7d8g4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T11:12:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 736.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:42:49Z" - latency: 2.466484ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T11:42:49Z" - latency: 1.100911ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:49Z" - latency: 1.740949ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T11:41:49Z" - latency: 932.181µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:49Z" - latency: 1.720421ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T11:40:49Z" - latency: 878.088µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:49Z" - latency: 1.781495ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T11:39:49Z" - latency: 1.209665ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:49Z" - latency: 1.875303ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T11:38:49Z" kind: List metadata: resourceVersion: ""