apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T08:43:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-8-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-8.ec2.internal uid: da22ee87-c878-4573-b2c0-493aafdf11ef resourceVersion: "37198" uid: 6b687053-42fa-4dba-aec6-960738a27a61 spec: sourcePod: network-check-source-7b678d77c7-mxc5t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T08:50:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.282µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:04:23Z" - latency: 995.151µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:03:23Z" - latency: 1.200562ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:02:23Z" - latency: 948.302µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:01:23Z" - latency: 971.57µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:00:23Z" - latency: 1.17133ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:59:23Z" - latency: 1.051702ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:58:23Z" - latency: 1.040191ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:57:23Z" - latency: 908.932µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:56:23Z" - latency: 1.325346ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:55:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T08:43:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-8-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-8.ec2.internal uid: da22ee87-c878-4573-b2c0-493aafdf11ef resourceVersion: "40406" uid: 94357385-dfa4-40ef-9fe3-5338b999d968 spec: sourcePod: network-check-source-7b678d77c7-mxc5t targetEndpoint: a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T08:49:23Z" message: 'load-balancer-api-external: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.251054ms message: 'load-balancer-api-external: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:07:23Z" - latency: 12.190702ms message: 'load-balancer-api-external: resolved host name a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T09:07:23Z" - latency: 3.993423ms message: 'load-balancer-api-external: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:06:23Z" - latency: 11.671096ms message: 'load-balancer-api-external: resolved host name a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T09:06:23Z" - latency: 5.158146ms message: 'load-balancer-api-external: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:05:23Z" - latency: 7.460751ms message: 'load-balancer-api-external: resolved host name a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T09:05:23Z" - latency: 4.140693ms message: 'load-balancer-api-external: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:04:23Z" - latency: 7.955965ms message: 'load-balancer-api-external: resolved host name a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T09:04:23Z" - latency: 5.955684ms message: 'load-balancer-api-external: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:03:23Z" - latency: 6.128717ms message: 'load-balancer-api-external: resolved host name a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T09:03:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T08:43:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-8-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-8.ec2.internal uid: da22ee87-c878-4573-b2c0-493aafdf11ef resourceVersion: "40407" uid: 1d84060d-e5bb-4f64-9a6c-65889007d265 spec: sourcePod: network-check-source-7b678d77c7-mxc5t targetEndpoint: a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T08:49:23Z" message: 'load-balancer-api-internal: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.49405ms message: 'load-balancer-api-internal: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:07:23Z" - latency: 12.094994ms message: 'load-balancer-api-internal: resolved host name a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T09:07:23Z" - latency: 4.021192ms message: 'load-balancer-api-internal: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:06:23Z" - latency: 11.638026ms message: 'load-balancer-api-internal: resolved host name a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T09:06:23Z" - latency: 5.147373ms message: 'load-balancer-api-internal: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:05:23Z" - latency: 7.413475ms message: 'load-balancer-api-internal: resolved host name a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T09:05:23Z" - latency: 4.165813ms message: 'load-balancer-api-internal: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:04:23Z" - latency: 7.884741ms message: 'load-balancer-api-internal: resolved host name a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T09:04:23Z" - latency: 5.965036ms message: 'load-balancer-api-internal: tcp connection to a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:03:23Z" - latency: 6.036432ms message: 'load-balancer-api-internal: resolved host name a42113db109f14a8e9374986d39fdf4a-07572db0bb88cbb9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T09:03:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T08:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-8-to-network-check-target-ip-10-0-137-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-8.ec2.internal uid: da22ee87-c878-4573-b2c0-493aafdf11ef resourceVersion: "37196" uid: 4a973d2b-73e1-445d-866f-92f3f8ea1648 spec: sourcePod: network-check-source-7b678d77c7-mxc5t targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T08:50:23Z" message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.980401ms message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:04:23Z" - latency: 2.321372ms message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:03:23Z" - latency: 2.393422ms message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:02:23Z" - latency: 2.726172ms message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:01:23Z" - latency: 2.373ms message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:00:23Z" - latency: 2.144374ms message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:59:23Z" - latency: 2.209358ms message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:58:23Z" - latency: 2.236931ms message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:57:23Z" - latency: 2.36135ms message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:56:23Z" - latency: 2.135341ms message: 'network-check-target-ip-10-0-137-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:55:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T08:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-8-to-network-check-target-ip-10-0-139-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-8.ec2.internal uid: da22ee87-c878-4573-b2c0-493aafdf11ef resourceVersion: "37194" uid: 94c96a37-de81-44ea-aad1-ea3fd6ecd7f5 spec: sourcePod: network-check-source-7b678d77c7-mxc5t targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T08:50:23Z" message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.819µs message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:04:23Z" - latency: 875.352µs message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:03:23Z" - latency: 966.39µs message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:02:23Z" - latency: 1.356296ms message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:01:23Z" - latency: 983.944µs message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:00:23Z" - latency: 920.93µs message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:59:23Z" - latency: 902.927µs message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:58:23Z" - latency: 939.48µs message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:57:23Z" - latency: 966.143µs message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:56:23Z" - latency: 866.618µs message: 'network-check-target-ip-10-0-139-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:55:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T08:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-8-to-network-check-target-ip-10-0-139-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-8.ec2.internal uid: da22ee87-c878-4573-b2c0-493aafdf11ef resourceVersion: "37195" uid: 8ce2156f-ef35-495f-bc28-82b7b4da6adb spec: sourcePod: network-check-source-7b678d77c7-mxc5t targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T08:50:23Z" message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.178264ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:04:23Z" - latency: 2.36368ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:03:23Z" - latency: 2.319299ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:02:23Z" - latency: 2.382175ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:01:23Z" - latency: 2.312726ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:00:23Z" - latency: 2.380533ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:59:23Z" - latency: 2.210685ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:58:23Z" - latency: 2.299339ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:57:23Z" - latency: 1.948378ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:56:23Z" - latency: 2.036181ms message: 'network-check-target-ip-10-0-139-84: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T08:55:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T08:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-8-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-8.ec2.internal uid: da22ee87-c878-4573-b2c0-493aafdf11ef resourceVersion: "40405" uid: 53f3eabf-5ee8-432b-a52a-961c259b6dbc spec: sourcePod: network-check-source-7b678d77c7-mxc5t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T08:49:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 681.484µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:07:23Z" - latency: 2.253829ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T09:07:23Z" - latency: 966.305µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:06:23Z" - latency: 2.110916ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T09:06:23Z" - latency: 1.126898ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:05:23Z" - latency: 1.885163ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T09:05:23Z" - latency: 794.228µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:04:23Z" - latency: 1.739894ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T09:04:23Z" - latency: 917.952µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T09:03:23Z" - latency: 1.641731ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T09:03:23Z" kind: List metadata: resourceVersion: ""