apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:49:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-201-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-201.ec2.internal uid: f1db7099-54a0-4b40-9529-673d9cdbb4ff resourceVersion: "17944" uid: dfa5fdcb-8fd5-4f76-978b-3f9167b8d0f1 spec: sourcePod: network-check-source-56d84b9f44-6knfl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T15:56:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 873.328µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:03:25Z" - latency: 1.242781ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:02:25Z" - latency: 795.88µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:01:25Z" - latency: 905.713µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:00:25Z" - latency: 943.891µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:59:25Z" - latency: 911.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:58:25Z" - latency: 753.936µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:57:25Z" - latency: 740.636µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:56:25Z" - latency: 1.06579ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:55:25Z" - latency: 1.004172ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:54:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:49:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-201-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-201.ec2.internal uid: f1db7099-54a0-4b40-9529-673d9cdbb4ff resourceVersion: "20090" uid: a6561f1d-59b0-4228-b6da-19577fcc93a8 spec: sourcePod: network-check-source-56d84b9f44-6knfl targetEndpoint: a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T15:55:25Z" message: 'load-balancer-api-external: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.590871ms message: 'load-balancer-api-external: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:07:25Z" - latency: 6.102685ms message: 'load-balancer-api-external: resolved host name a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:07:25Z" - latency: 4.544413ms message: 'load-balancer-api-external: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:06:25Z" - latency: 7.049998ms message: 'load-balancer-api-external: resolved host name a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:06:25Z" - latency: 4.897704ms message: 'load-balancer-api-external: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:05:25Z" - latency: 6.952216ms message: 'load-balancer-api-external: resolved host name a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:05:25Z" - latency: 4.971829ms message: 'load-balancer-api-external: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:04:25Z" - latency: 7.852415ms message: 'load-balancer-api-external: resolved host name a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:04:25Z" - latency: 4.993085ms message: 'load-balancer-api-external: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:03:25Z" - latency: 6.398864ms message: 'load-balancer-api-external: resolved host name a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:03:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:49:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-201-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-201.ec2.internal uid: f1db7099-54a0-4b40-9529-673d9cdbb4ff resourceVersion: "20091" uid: 67bfa9b3-7814-45b7-8693-3b176ea76785 spec: sourcePod: network-check-source-56d84b9f44-6knfl targetEndpoint: a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T15:55:25Z" message: 'load-balancer-api-internal: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.618076ms message: 'load-balancer-api-internal: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:07:25Z" - latency: 6.236606ms message: 'load-balancer-api-internal: resolved host name a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:07:25Z" - latency: 4.524239ms message: 'load-balancer-api-internal: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:06:25Z" - latency: 6.984446ms message: 'load-balancer-api-internal: resolved host name a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:06:25Z" - latency: 5.029953ms message: 'load-balancer-api-internal: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:05:25Z" - latency: 6.982092ms message: 'load-balancer-api-internal: resolved host name a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:05:25Z" - latency: 5.071715ms message: 'load-balancer-api-internal: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:04:25Z" - latency: 7.778513ms message: 'load-balancer-api-internal: resolved host name a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:04:25Z" - latency: 5.021816ms message: 'load-balancer-api-internal: tcp connection to a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:03:25Z" - latency: 6.3285ms message: 'load-balancer-api-internal: resolved host name a58d9fd2e47c145d9802637077705e15-e278994d9f436010.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T16:03:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:49:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-201-to-network-check-target-ip-10-0-128-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-201.ec2.internal uid: f1db7099-54a0-4b40-9529-673d9cdbb4ff resourceVersion: "17942" uid: 7d2e386c-ffe1-44b7-87bd-aba069ce04d7 spec: sourcePod: network-check-source-56d84b9f44-6knfl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T15:56:25Z" message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.429055ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:03:25Z" - latency: 2.202849ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:02:25Z" - latency: 2.039009ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:01:25Z" - latency: 2.158744ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:00:25Z" - latency: 2.341797ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:59:25Z" - latency: 2.215627ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:58:25Z" - latency: 2.201215ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:57:25Z" - latency: 2.502563ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:56:25Z" - latency: 2.4095ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:55:25Z" - latency: 2.249339ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:54:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:49:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-201-to-network-check-target-ip-10-0-140-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-201.ec2.internal uid: f1db7099-54a0-4b40-9529-673d9cdbb4ff resourceVersion: "17943" uid: 1dd6e099-4491-43be-ab7f-152c2181516a spec: sourcePod: network-check-source-56d84b9f44-6knfl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T15:56:25Z" message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.062957ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:03:25Z" - latency: 2.238562ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:02:25Z" - latency: 2.466932ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:01:25Z" - latency: 2.098364ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:00:25Z" - latency: 2.136515ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:59:25Z" - latency: 2.354571ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:58:25Z" - latency: 2.160331ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:57:25Z" - latency: 2.488654ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:56:25Z" - latency: 2.153186ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:55:25Z" - latency: 2.358854ms message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:54:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:49:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-201-to-network-check-target-ip-10-0-141-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-201.ec2.internal uid: f1db7099-54a0-4b40-9529-673d9cdbb4ff resourceVersion: "17941" uid: eebd4a04-1c8e-452a-b9c6-5c207ecaa485 spec: sourcePod: network-check-source-56d84b9f44-6knfl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T15:56:25Z" message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 795.026µs message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:03:25Z" - latency: 865.571µs message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:02:25Z" - latency: 1.458539ms message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:01:25Z" - latency: 879.685µs message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:00:25Z" - latency: 871.34µs message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:59:25Z" - latency: 824.604µs message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:58:25Z" - latency: 1.06625ms message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:57:25Z" - latency: 1.630528ms message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:56:25Z" - latency: 1.538378ms message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:55:25Z" - latency: 864.019µs message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T15:54:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T15:49:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-201-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-201.ec2.internal uid: f1db7099-54a0-4b40-9529-673d9cdbb4ff resourceVersion: "20089" uid: 122064a9-3df9-4ee8-864a-44ce4f54adee spec: sourcePod: network-check-source-56d84b9f44-6knfl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T15:55:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.035137ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:07:25Z" - latency: 1.593615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:07:25Z" - latency: 875.782µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:06:25Z" - latency: 1.740946ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:06:25Z" - latency: 784.11µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:05:25Z" - latency: 1.595704ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:05:25Z" - latency: 773.963µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:04:25Z" - latency: 1.938977ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:04:25Z" - latency: 965.661µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T16:03:25Z" - latency: 1.55448ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T16:03:25Z" kind: List metadata: resourceVersion: ""