apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:33:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 7359be4b-e16a-46f2-b273-5fca7157f5ed resourceVersion: "62141" uid: 438a8f1b-eb77-4c3e-bc78-9e2f2f1f5bf8 spec: sourcePod: network-check-source-869dcfcdcd-knxlf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T14:40:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.178436ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:15:59Z" - latency: 1.113602ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:14:59Z" - latency: 1.082931ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:13:59Z" - latency: 1.059604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:12:59Z" - latency: 920.616µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:11:59Z" - latency: 1.227261ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:10:59Z" - latency: 754.724µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:09:59Z" - latency: 857.61µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:08:59Z" - latency: 947.538µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:59Z" - latency: 1.150871ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:33:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 7359be4b-e16a-46f2-b273-5fca7157f5ed resourceVersion: "62142" uid: cc56f89c-4a16-4251-b082-6113e5584fc9 spec: sourcePod: network-check-source-869dcfcdcd-knxlf targetEndpoint: ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T14:39:59Z" message: 'load-balancer-api-external: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.786889ms message: 'load-balancer-api-external: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:15:59Z" - latency: 8.005103ms message: 'load-balancer-api-external: resolved host name ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:15:59Z" - latency: 4.69303ms message: 'load-balancer-api-external: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:14:59Z" - latency: 7.658653ms message: 'load-balancer-api-external: resolved host name ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:14:59Z" - latency: 4.588961ms message: 'load-balancer-api-external: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:13:59Z" - latency: 8.608005ms message: 'load-balancer-api-external: resolved host name ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:13:59Z" - latency: 5.649264ms message: 'load-balancer-api-external: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:12:59Z" - latency: 6.798874ms message: 'load-balancer-api-external: resolved host name ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:12:59Z" - latency: 3.224181ms message: 'load-balancer-api-external: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:11:59Z" - latency: 8.271484ms message: 'load-balancer-api-external: resolved host name ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:11:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:33:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 7359be4b-e16a-46f2-b273-5fca7157f5ed resourceVersion: "62143" uid: a1ed70a3-36c8-4d4d-8550-50634c53c5e9 spec: sourcePod: network-check-source-869dcfcdcd-knxlf targetEndpoint: ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T14:39:59Z" message: 'load-balancer-api-internal: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.551162ms message: 'load-balancer-api-internal: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:15:59Z" - latency: 7.94178ms message: 'load-balancer-api-internal: resolved host name ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:15:59Z" - latency: 4.702716ms message: 'load-balancer-api-internal: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:14:59Z" - latency: 7.563507ms message: 'load-balancer-api-internal: resolved host name ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:14:59Z" - latency: 7.491006ms message: 'load-balancer-api-internal: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:13:59Z" - latency: 8.585711ms message: 'load-balancer-api-internal: resolved host name ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:13:59Z" - latency: 5.636463ms message: 'load-balancer-api-internal: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:12:59Z" - latency: 6.825008ms message: 'load-balancer-api-internal: resolved host name ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:12:59Z" - latency: 4.261606ms message: 'load-balancer-api-internal: tcp connection to ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:11:59Z" - latency: 8.147429ms message: 'load-balancer-api-internal: resolved host name ab82abff9b76044308c73fe0050fd707-c5ddd6774bc57f88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:11:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:33:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-network-check-target-ip-10-0-135-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 7359be4b-e16a-46f2-b273-5fca7157f5ed resourceVersion: "62140" uid: 899256aa-865c-46dd-a0ab-ab2dc6c5ae70 spec: sourcePod: network-check-source-869dcfcdcd-knxlf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T14:40:59Z" message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.179529ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:15:59Z" - latency: 1.769657ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:14:59Z" - latency: 2.214182ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:13:59Z" - latency: 2.119845ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:12:59Z" - latency: 1.90567ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:11:59Z" - latency: 2.165811ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:10:59Z" - latency: 1.772949ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:09:59Z" - latency: 2.395159ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:08:59Z" - latency: 2.168457ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:59Z" - latency: 2.264542ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:33:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-network-check-target-ip-10-0-141-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 7359be4b-e16a-46f2-b273-5fca7157f5ed resourceVersion: "62137" uid: c6aaf940-9ec4-43af-b1c6-8db3634c448f spec: sourcePod: network-check-source-869dcfcdcd-knxlf targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T14:40:59Z" message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 929.469µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:15:59Z" - latency: 972.846µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:14:59Z" - latency: 972.194µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:13:59Z" - latency: 909.812µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:12:59Z" - latency: 868.305µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:11:59Z" - latency: 1.119484ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:10:59Z" - latency: 881.26µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:09:59Z" - latency: 1.047663ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:08:59Z" - latency: 743.71µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:59Z" - latency: 822.364µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:33:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-network-check-target-ip-10-0-141-209 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 7359be4b-e16a-46f2-b273-5fca7157f5ed resourceVersion: "62138" uid: 92621dfc-2297-46ac-9509-55b146bc43f2 spec: sourcePod: network-check-source-869dcfcdcd-knxlf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T14:40:59Z" message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.011311ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:15:59Z" - latency: 1.883745ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:14:59Z" - latency: 2.10565ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:13:59Z" - latency: 2.043164ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:12:59Z" - latency: 1.911959ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:11:59Z" - latency: 2.102796ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:10:59Z" - latency: 1.796184ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:09:59Z" - latency: 2.22042ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:08:59Z" - latency: 2.406258ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:59Z" - latency: 2.028845ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:33:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 7359be4b-e16a-46f2-b273-5fca7157f5ed resourceVersion: "62139" uid: 1ec3103c-5cde-4141-8998-32fafcdaabf5 spec: sourcePod: network-check-source-869dcfcdcd-knxlf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T14:39:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.318µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:15:59Z" - latency: 1.660668ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T15:15:59Z" - latency: 1.069863ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:14:59Z" - latency: 1.869433ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T15:14:59Z" - latency: 1.053494ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:13:59Z" - latency: 1.768032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T15:13:59Z" - latency: 979.93µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:12:59Z" - latency: 1.662173ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T15:12:59Z" - latency: 975.531µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:11:59Z" - latency: 1.603485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T15:11:59Z" kind: List metadata: resourceVersion: ""