apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:55:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-247-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-247.ec2.internal uid: 53c79e0e-5e6c-4a9a-9770-b85a743c3bc0 resourceVersion: "46789" uid: cae5c7e7-d29a-46aa-8ed1-fdecc796b5b2 spec: sourcePod: network-check-source-dbd9cf844-8nrhl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-06T21:02:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.38µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:23:49Z" - latency: 825.371µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:22:49Z" - latency: 863.581µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:21:49Z" - latency: 990.884µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:20:49Z" - latency: 917.741µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:19:49Z" - latency: 1.330227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:18:49Z" - latency: 781.302µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:17:49Z" - latency: 1.465629ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:16:49Z" - latency: 1.065065ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:15:49Z" - latency: 893.467µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:14:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:55:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-247-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-247.ec2.internal uid: 53c79e0e-5e6c-4a9a-9770-b85a743c3bc0 resourceVersion: "48865" uid: 1c902557-3edd-4fed-b5b1-6ce5766bd1d2 spec: sourcePod: network-check-source-dbd9cf844-8nrhl targetEndpoint: afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T21:01:49Z" message: 'load-balancer-api-external: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.23998ms message: 'load-balancer-api-external: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:25:49Z" - latency: 6.914605ms message: 'load-balancer-api-external: resolved host name afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T21:25:49Z" - latency: 5.617806ms message: 'load-balancer-api-external: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:24:49Z" - latency: 7.940419ms message: 'load-balancer-api-external: resolved host name afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T21:24:49Z" - latency: 4.291366ms message: 'load-balancer-api-external: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:23:49Z" - latency: 8.084455ms message: 'load-balancer-api-external: resolved host name afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T21:23:49Z" - latency: 3.368186ms message: 'load-balancer-api-external: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:22:49Z" - latency: 8.087976ms message: 'load-balancer-api-external: resolved host name afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T21:22:49Z" - latency: 4.339779ms message: 'load-balancer-api-external: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:21:49Z" - latency: 8.07259ms message: 'load-balancer-api-external: resolved host name afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T21:21:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:55:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-247-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-247.ec2.internal uid: 53c79e0e-5e6c-4a9a-9770-b85a743c3bc0 resourceVersion: "48866" uid: e860aa37-8357-4249-8f49-e1943e355f70 spec: sourcePod: network-check-source-dbd9cf844-8nrhl targetEndpoint: afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T21:01:49Z" message: 'load-balancer-api-internal: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.246958ms message: 'load-balancer-api-internal: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:25:49Z" - latency: 6.844982ms message: 'load-balancer-api-internal: resolved host name afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T21:25:49Z" - latency: 5.55561ms message: 'load-balancer-api-internal: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:24:49Z" - latency: 7.980258ms message: 'load-balancer-api-internal: resolved host name afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T21:24:49Z" - latency: 4.279896ms message: 'load-balancer-api-internal: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:23:49Z" - latency: 7.991352ms message: 'load-balancer-api-internal: resolved host name afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T21:23:49Z" - latency: 3.33584ms message: 'load-balancer-api-internal: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:22:49Z" - latency: 8.156562ms message: 'load-balancer-api-internal: resolved host name afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T21:22:49Z" - latency: 4.324841ms message: 'load-balancer-api-internal: tcp connection to afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:21:49Z" - latency: 7.926803ms message: 'load-balancer-api-internal: resolved host name afcb0c01dd3164924a4df678bf673997-94fc4a1fc0b95b20.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T21:21:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:55:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-247-to-network-check-target-ip-10-0-129-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-247.ec2.internal uid: 53c79e0e-5e6c-4a9a-9770-b85a743c3bc0 resourceVersion: "46788" uid: 1b252118-42e6-40e5-bce2-6ba8ea69fe2d spec: sourcePod: network-check-source-dbd9cf844-8nrhl targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-06T21:02:49Z" message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.543036ms message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:23:49Z" - latency: 2.057625ms message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:22:49Z" - latency: 2.214232ms message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:21:49Z" - latency: 2.277948ms message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:20:49Z" - latency: 2.382963ms message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:19:49Z" - latency: 2.209996ms message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:18:49Z" - latency: 2.104402ms message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:17:49Z" - latency: 2.294305ms message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:16:49Z" - latency: 2.296865ms message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:15:49Z" - latency: 2.393686ms message: 'network-check-target-ip-10-0-129-66: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:14:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:55:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-247-to-network-check-target-ip-10-0-132-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-247.ec2.internal uid: 53c79e0e-5e6c-4a9a-9770-b85a743c3bc0 resourceVersion: "46787" uid: e710b634-318b-4093-8e39-56f7a748e052 spec: sourcePod: network-check-source-dbd9cf844-8nrhl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-06T21:02:49Z" message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.594914ms message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:23:49Z" - latency: 1.719134ms message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:22:49Z" - latency: 1.767423ms message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:21:49Z" - latency: 1.811468ms message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:20:49Z" - latency: 1.967051ms message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:19:49Z" - latency: 1.691449ms message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:18:49Z" - latency: 1.503923ms message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:17:49Z" - latency: 1.884135ms message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:16:49Z" - latency: 1.869129ms message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:15:49Z" - latency: 1.854084ms message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:14:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:55:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-247-to-network-check-target-ip-10-0-133-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-247.ec2.internal uid: 53c79e0e-5e6c-4a9a-9770-b85a743c3bc0 resourceVersion: "46786" uid: 58fc8549-53a8-4bf1-85a5-2bc5a4151830 spec: sourcePod: network-check-source-dbd9cf844-8nrhl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-06T21:02:49Z" message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 994.016µs message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:23:49Z" - latency: 830.266µs message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:22:49Z" - latency: 938.83µs message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:21:49Z" - latency: 824.331µs message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:20:49Z" - latency: 825.174µs message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:19:49Z" - latency: 672.231µs message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:18:49Z" - latency: 707.707µs message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:17:49Z" - latency: 1.207951ms message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:16:49Z" - latency: 818.06µs message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:15:49Z" - latency: 772.872µs message: 'network-check-target-ip-10-0-133-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:14:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T20:55:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-247-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-247.ec2.internal uid: 53c79e0e-5e6c-4a9a-9770-b85a743c3bc0 resourceVersion: "48864" uid: 7161feb9-9cb5-4c3d-826d-d2e5fb7ef1e0 spec: sourcePod: network-check-source-dbd9cf844-8nrhl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-06T21:01:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.189854ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:25:49Z" - latency: 1.762795ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T21:25:49Z" - latency: 867.409µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:24:49Z" - latency: 1.888312ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T21:24:49Z" - latency: 1.248515ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:23:49Z" - latency: 1.603796ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T21:23:49Z" - latency: 716.72µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:22:49Z" - latency: 2.139718ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T21:22:49Z" - latency: 777.027µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T21:21:49Z" - latency: 1.600328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T21:21:49Z" kind: List metadata: resourceVersion: ""