apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T13:39:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-48-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-48.ec2.internal uid: af379ef5-3bb7-49e6-b403-551b39ef86b4 resourceVersion: "30321" uid: 2c99a1f9-5a03-421b-a072-e62dbb808232 spec: sourcePod: network-check-source-6947749cfc-fdz7k targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-14T13:46:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 974.018µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:53:24Z" - latency: 980.386µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:52:24Z" - latency: 970.701µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:51:24Z" - latency: 1.639809ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:50:24Z" - latency: 984.668µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:49:24Z" - latency: 1.133983ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:48:24Z" - latency: 985.642µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:47:24Z" - latency: 1.129205ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:46:24Z" - latency: 1.146927ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:45:24Z" - latency: 1.099683ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:44:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T13:39:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-48-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-48.ec2.internal uid: af379ef5-3bb7-49e6-b403-551b39ef86b4 resourceVersion: "29058" uid: b25b68ca-2299-4d6c-bb3f-bb3afe07b463 spec: sourcePod: network-check-source-6947749cfc-fdz7k targetEndpoint: a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T13:45:24Z" message: 'load-balancer-api-external: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.54372ms message: 'load-balancer-api-external: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:51:24Z" - latency: 8.536296ms message: 'load-balancer-api-external: resolved host name a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T13:51:24Z" - latency: 4.603506ms message: 'load-balancer-api-external: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:50:24Z" - latency: 10.665896ms message: 'load-balancer-api-external: resolved host name a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T13:50:24Z" - latency: 4.978143ms message: 'load-balancer-api-external: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:49:24Z" - latency: 9.296905ms message: 'load-balancer-api-external: resolved host name a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T13:49:24Z" - latency: 4.741092ms message: 'load-balancer-api-external: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:48:24Z" - latency: 9.288682ms message: 'load-balancer-api-external: resolved host name a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T13:48:24Z" - latency: 5.14432ms message: 'load-balancer-api-external: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:47:24Z" - latency: 10.132424ms message: 'load-balancer-api-external: resolved host name a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T13:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T13:39:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-48-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-48.ec2.internal uid: af379ef5-3bb7-49e6-b403-551b39ef86b4 resourceVersion: "29059" uid: 8a476e6f-ae5e-4ca4-86d2-8260da00d60d spec: sourcePod: network-check-source-6947749cfc-fdz7k targetEndpoint: a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T13:45:24Z" message: 'load-balancer-api-internal: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.525641ms message: 'load-balancer-api-internal: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:51:24Z" - latency: 8.601031ms message: 'load-balancer-api-internal: resolved host name a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T13:51:24Z" - latency: 4.583218ms message: 'load-balancer-api-internal: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:50:24Z" - latency: 10.626887ms message: 'load-balancer-api-internal: resolved host name a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T13:50:24Z" - latency: 4.934315ms message: 'load-balancer-api-internal: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:49:24Z" - latency: 9.265619ms message: 'load-balancer-api-internal: resolved host name a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T13:49:24Z" - latency: 5.270107ms message: 'load-balancer-api-internal: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:48:24Z" - latency: 9.311993ms message: 'load-balancer-api-internal: resolved host name a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T13:48:24Z" - latency: 5.129476ms message: 'load-balancer-api-internal: tcp connection to a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:47:24Z" - latency: 10.092008ms message: 'load-balancer-api-internal: resolved host name a00ba599884d24fcd93798bb4b562107-1a9fcbeb6afee672.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T13:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T13:39:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-48-to-network-check-target-ip-10-0-131-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-48.ec2.internal uid: af379ef5-3bb7-49e6-b403-551b39ef86b4 resourceVersion: "30318" uid: 326da153-80db-4da2-b6f3-8e736b8aac3b spec: sourcePod: network-check-source-6947749cfc-fdz7k targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-14T13:46:24Z" message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.27133ms message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:53:24Z" - latency: 868.915µs message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:52:24Z" - latency: 937.046µs message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:51:24Z" - latency: 962.435µs message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:50:24Z" - latency: 913.253µs message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:49:24Z" - latency: 849.074µs message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:48:24Z" - latency: 939.442µs message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:47:24Z" - latency: 1.347242ms message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:46:24Z" - latency: 961.272µs message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:45:24Z" - latency: 7.138315ms message: 'network-check-target-ip-10-0-131-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:44:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T13:39:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-48-to-network-check-target-ip-10-0-132-154 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-48.ec2.internal uid: af379ef5-3bb7-49e6-b403-551b39ef86b4 resourceVersion: "30320" uid: 39b7598d-d41d-4318-aa6d-f9a5b87b07d5 spec: sourcePod: network-check-source-6947749cfc-fdz7k targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-14T13:46:24Z" message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.895908ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:53:24Z" - latency: 1.883601ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:52:24Z" - latency: 2.374964ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:51:24Z" - latency: 2.55866ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:50:24Z" - latency: 2.285718ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:49:24Z" - latency: 1.732745ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:48:24Z" - latency: 1.798646ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:47:24Z" - latency: 2.282617ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:46:24Z" - latency: 2.053756ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:45:24Z" - latency: 1.983721ms message: 'network-check-target-ip-10-0-132-154: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:44:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T13:39:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-48-to-network-check-target-ip-10-0-139-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-48.ec2.internal uid: af379ef5-3bb7-49e6-b403-551b39ef86b4 resourceVersion: "30319" uid: 13b4856e-63f2-46b1-9da9-6791200b2eb9 spec: sourcePod: network-check-source-6947749cfc-fdz7k targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-14T13:46:24Z" message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.921679ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:53:24Z" - latency: 1.808148ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:52:24Z" - latency: 1.984175ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:51:24Z" - latency: 1.880411ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:50:24Z" - latency: 1.807258ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:49:24Z" - latency: 1.963104ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:48:24Z" - latency: 1.795223ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:47:24Z" - latency: 1.630933ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:46:24Z" - latency: 2.019242ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:45:24Z" - latency: 1.841836ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:44:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T13:39:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-48-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-48.ec2.internal uid: af379ef5-3bb7-49e6-b403-551b39ef86b4 resourceVersion: "29057" uid: 0301799c-caab-4567-88a0-570d005bc63a spec: sourcePod: network-check-source-6947749cfc-fdz7k targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-14T13:45:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.89µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:51:24Z" - latency: 1.715752ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T13:51:24Z" - latency: 1.103322ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:50:24Z" - latency: 1.799537ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T13:50:24Z" - latency: 1.380705ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:49:24Z" - latency: 1.810343ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T13:49:24Z" - latency: 940.129µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:48:24Z" - latency: 1.78516ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T13:48:24Z" - latency: 1.03241ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T13:47:24Z" - latency: 1.762733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T13:47:24Z" kind: List metadata: resourceVersion: ""