apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T23:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-63-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-63.ec2.internal uid: 2e63c75c-4d88-488b-9a9d-d952d95032b3 resourceVersion: "87445" uid: ef05d614-36a5-4659-b6c9-2f9d3d8c294f spec: sourcePod: network-check-source-7d88cb55d8-hwpg9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T23:39:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.146392ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:21:03Z" - latency: 1.189567ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:20:03Z" - latency: 981.634µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:19:03Z" - latency: 2.031242ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:18:03Z" - latency: 1.50537ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:17:03Z" - latency: 1.381563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:16:03Z" - latency: 1.214609ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:15:03Z" - latency: 966.93µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:14:03Z" - latency: 1.320771ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:13:03Z" - latency: 1.244787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:12:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T23:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-63-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-63.ec2.internal uid: 2e63c75c-4d88-488b-9a9d-d952d95032b3 resourceVersion: "85246" uid: 8030787e-3401-400d-b3dd-d90f3f9e9e47 spec: sourcePod: network-check-source-7d88cb55d8-hwpg9 targetEndpoint: aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T23:38:03Z" message: 'load-balancer-api-external: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.194667ms message: 'load-balancer-api-external: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:20:03Z" - latency: 6.861181ms message: 'load-balancer-api-external: resolved host name aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T00:20:03Z" - latency: 4.882909ms message: 'load-balancer-api-external: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:19:03Z" - latency: 6.247964ms message: 'load-balancer-api-external: resolved host name aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T00:19:03Z" - latency: 4.255355ms message: 'load-balancer-api-external: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:18:03Z" - latency: 9.153668ms message: 'load-balancer-api-external: resolved host name aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T00:18:03Z" - latency: 4.248036ms message: 'load-balancer-api-external: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:17:03Z" - latency: 7.552276ms message: 'load-balancer-api-external: resolved host name aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T00:17:03Z" - latency: 4.286241ms message: 'load-balancer-api-external: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:16:03Z" - latency: 7.190588ms message: 'load-balancer-api-external: resolved host name aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T00:16:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T23:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-63-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-63.ec2.internal uid: 2e63c75c-4d88-488b-9a9d-d952d95032b3 resourceVersion: "85247" uid: 94f6fcde-b596-41f0-a267-6e96f6ff49dc spec: sourcePod: network-check-source-7d88cb55d8-hwpg9 targetEndpoint: aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T23:38:03Z" message: 'load-balancer-api-internal: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.121804ms message: 'load-balancer-api-internal: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:20:03Z" - latency: 6.839412ms message: 'load-balancer-api-internal: resolved host name aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T00:20:03Z" - latency: 4.904875ms message: 'load-balancer-api-internal: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:19:03Z" - latency: 6.221119ms message: 'load-balancer-api-internal: resolved host name aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T00:19:03Z" - latency: 4.252929ms message: 'load-balancer-api-internal: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:18:03Z" - latency: 9.124036ms message: 'load-balancer-api-internal: resolved host name aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T00:18:03Z" - latency: 6.060191ms message: 'load-balancer-api-internal: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:17:03Z" - latency: 7.516852ms message: 'load-balancer-api-internal: resolved host name aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T00:17:03Z" - latency: 4.294396ms message: 'load-balancer-api-internal: tcp connection to aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:16:03Z" - latency: 7.114584ms message: 'load-balancer-api-internal: resolved host name aa3864ef1c6764beba30cba1e2b4f32c-7643424f55938575.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T00:16:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T23:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-63-to-network-check-target-ip-10-0-131-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-63.ec2.internal uid: 2e63c75c-4d88-488b-9a9d-d952d95032b3 resourceVersion: "87442" uid: be8f4614-67e2-4230-a0c3-7445a2938f44 spec: sourcePod: network-check-source-7d88cb55d8-hwpg9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T23:39:03Z" message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 913.781µs message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:21:03Z" - latency: 987.631µs message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:20:03Z" - latency: 898.951µs message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:19:03Z" - latency: 1.069145ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:18:03Z" - latency: 1.468909ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:17:03Z" - latency: 1.435153ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:16:03Z" - latency: 888.799µs message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:15:03Z" - latency: 1.495896ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:14:03Z" - latency: 1.212191ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:13:03Z" - latency: 918.357µs message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:12:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T23:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-63-to-network-check-target-ip-10-0-141-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-63.ec2.internal uid: 2e63c75c-4d88-488b-9a9d-d952d95032b3 resourceVersion: "87444" uid: 1cd61548-5de8-4e72-8238-7e4747335acf spec: sourcePod: network-check-source-7d88cb55d8-hwpg9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T23:39:03Z" message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.365305ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:21:03Z" - latency: 2.631303ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:20:03Z" - latency: 2.373799ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:19:03Z" - latency: 3.055331ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:18:03Z" - latency: 2.508364ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:17:03Z" - latency: 2.470441ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:16:03Z" - latency: 2.480623ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:15:03Z" - latency: 2.323145ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:14:03Z" - latency: 2.660856ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:13:03Z" - latency: 2.257458ms message: 'network-check-target-ip-10-0-141-134: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:12:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T23:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-63-to-network-check-target-ip-10-0-142-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-63.ec2.internal uid: 2e63c75c-4d88-488b-9a9d-d952d95032b3 resourceVersion: "87443" uid: c611b110-d132-420e-a4dd-c0f9e9759690 spec: sourcePod: network-check-source-7d88cb55d8-hwpg9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T23:39:03Z" message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.37542ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:21:03Z" - latency: 2.435029ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:20:03Z" - latency: 2.7145ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:19:03Z" - latency: 2.377833ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:18:03Z" - latency: 2.462173ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:17:03Z" - latency: 2.729357ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:16:03Z" - latency: 2.383338ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:15:03Z" - latency: 2.291241ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:14:03Z" - latency: 2.611358ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:13:03Z" - latency: 2.382189ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:12:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T23:32:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-63-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-63.ec2.internal uid: 2e63c75c-4d88-488b-9a9d-d952d95032b3 resourceVersion: "85245" uid: c9636162-3279-45bd-a9ba-7998de1a045b spec: sourcePod: network-check-source-7d88cb55d8-hwpg9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T23:38:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.077559ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:20:03Z" - latency: 1.88503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T00:20:03Z" - latency: 936.905µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:19:03Z" - latency: 1.880686ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T00:19:03Z" - latency: 830.556µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:18:03Z" - latency: 2.553022ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T00:18:03Z" - latency: 1.001649ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:17:03Z" - latency: 2.001743ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T00:17:03Z" - latency: 990.287µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T00:16:03Z" - latency: 1.914558ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T00:16:03Z" kind: List metadata: resourceVersion: ""