apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T13:14:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-41-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-41.ec2.internal uid: 0bedd09a-2c66-4709-94e0-457483196b5f resourceVersion: "44004" uid: 32498b0d-fcdf-4f9f-8a72-04cd7f4ce7dd spec: sourcePod: network-check-source-dbd9cf844-fsxf2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T13:21:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.213551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:42:07Z" - latency: 920.079µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:41:07Z" - latency: 959.43µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:40:07Z" - latency: 1.176414ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:39:07Z" - latency: 1.103859ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:38:07Z" - latency: 1.168894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:37:07Z" - latency: 935.814µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:36:07Z" - latency: 1.077283ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:35:07Z" - latency: 955.603µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:34:07Z" - latency: 991.785µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:33:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T13:14:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-41-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-41.ec2.internal uid: 0bedd09a-2c66-4709-94e0-457483196b5f resourceVersion: "46038" uid: 50105040-d6df-4c06-aab1-ab591549b40b spec: sourcePod: network-check-source-dbd9cf844-fsxf2 targetEndpoint: a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T13:20:07Z" message: 'load-balancer-api-external: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.486809ms message: 'load-balancer-api-external: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:44:07Z" - latency: 6.179888ms message: 'load-balancer-api-external: resolved host name a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:44:07Z" - latency: 4.875379ms message: 'load-balancer-api-external: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:43:07Z" - latency: 6.519074ms message: 'load-balancer-api-external: resolved host name a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:43:07Z" - latency: 4.982446ms message: 'load-balancer-api-external: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:42:07Z" - latency: 7.26995ms message: 'load-balancer-api-external: resolved host name a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:42:07Z" - latency: 7.377966ms message: 'load-balancer-api-external: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:41:07Z" - latency: 7.435084ms message: 'load-balancer-api-external: resolved host name a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:41:07Z" - latency: 4.729121ms message: 'load-balancer-api-external: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:40:07Z" - latency: 6.483578ms message: 'load-balancer-api-external: resolved host name a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:40:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T13:14:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-41-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-41.ec2.internal uid: 0bedd09a-2c66-4709-94e0-457483196b5f resourceVersion: "46039" uid: 857a5c1d-e411-4cee-aead-94b2625342b9 spec: sourcePod: network-check-source-dbd9cf844-fsxf2 targetEndpoint: a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T13:20:07Z" message: 'load-balancer-api-internal: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.603852ms message: 'load-balancer-api-internal: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:44:07Z" - latency: 6.104193ms message: 'load-balancer-api-internal: resolved host name a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:44:07Z" - latency: 4.917758ms message: 'load-balancer-api-internal: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:43:07Z" - latency: 6.567012ms message: 'load-balancer-api-internal: resolved host name a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:43:07Z" - latency: 4.969401ms message: 'load-balancer-api-internal: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:42:07Z" - latency: 7.183099ms message: 'load-balancer-api-internal: resolved host name a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:42:07Z" - latency: 3.792296ms message: 'load-balancer-api-internal: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:41:07Z" - latency: 7.36429ms message: 'load-balancer-api-internal: resolved host name a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:41:07Z" - latency: 3.831989ms message: 'load-balancer-api-internal: tcp connection to a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:40:07Z" - latency: 6.41324ms message: 'load-balancer-api-internal: resolved host name a23b07104e8064d6cbff59bcc46f9caa-5710fa39c5977a30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T13:40:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T13:14:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-41-to-network-check-target-ip-10-0-140-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-41.ec2.internal uid: 0bedd09a-2c66-4709-94e0-457483196b5f resourceVersion: "44001" uid: bafeea9a-4fa7-4027-87f2-d5533e365446 spec: sourcePod: network-check-source-dbd9cf844-fsxf2 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T13:21:07Z" message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.091042ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:42:07Z" - latency: 850.659µs message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:41:07Z" - latency: 992.485µs message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:40:07Z" - latency: 1.350396ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:39:07Z" - latency: 947.115µs message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:38:07Z" - latency: 900.098µs message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:37:07Z" - latency: 943.388µs message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:36:07Z" - latency: 861.408µs message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:35:07Z" - latency: 1.05449ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:34:07Z" - latency: 1.163226ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:33:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T13:14:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-41-to-network-check-target-ip-10-0-141-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-41.ec2.internal uid: 0bedd09a-2c66-4709-94e0-457483196b5f resourceVersion: "44002" uid: 0c5281e6-c643-4cd2-a477-b42869db520c spec: sourcePod: network-check-source-dbd9cf844-fsxf2 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T13:21:07Z" message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.39048ms message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:42:07Z" - latency: 2.23396ms message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:41:07Z" - latency: 2.13108ms message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:40:07Z" - latency: 2.351721ms message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:39:07Z" - latency: 2.217264ms message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:38:07Z" - latency: 2.340632ms message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:37:07Z" - latency: 2.296436ms message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:36:07Z" - latency: 2.093899ms message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:35:07Z" - latency: 2.649028ms message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:34:07Z" - latency: 2.411597ms message: 'network-check-target-ip-10-0-141-252: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:33:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T13:14:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-41-to-network-check-target-ip-10-0-143-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-41.ec2.internal uid: 0bedd09a-2c66-4709-94e0-457483196b5f resourceVersion: "44003" uid: 6ecd8353-4383-48f2-ae41-ac124592dd03 spec: sourcePod: network-check-source-dbd9cf844-fsxf2 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T13:21:07Z" message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.356674ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:42:07Z" - latency: 1.952334ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:41:07Z" - latency: 2.203739ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:40:07Z" - latency: 2.419874ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:39:07Z" - latency: 2.211662ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:38:07Z" - latency: 2.312706ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:37:07Z" - latency: 2.198678ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:36:07Z" - latency: 2.336734ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:35:07Z" - latency: 2.375961ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:34:07Z" - latency: 2.434ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:33:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T13:14:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-41-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-41.ec2.internal uid: 0bedd09a-2c66-4709-94e0-457483196b5f resourceVersion: "46037" uid: 18cc6743-4259-4de5-a1ff-f8813f7d2aa5 spec: sourcePod: network-check-source-dbd9cf844-fsxf2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T13:20:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 691.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:44:07Z" - latency: 1.767679ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T13:44:07Z" - latency: 828.633µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:43:07Z" - latency: 1.681898ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T13:43:07Z" - latency: 1.095841ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:42:07Z" - latency: 1.816008ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T13:42:07Z" - latency: 1.06041ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:41:07Z" - latency: 2.195337ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T13:41:07Z" - latency: 1.022638ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T13:40:07Z" - latency: 1.920074ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T13:40:07Z" kind: List metadata: resourceVersion: ""