apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T10:20:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-180-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-180.ec2.internal uid: 0cbdec3f-1381-45f2-86ce-2008b3b30104 resourceVersion: "23681" uid: 6debe3b2-a207-430f-9ffe-b4acc606697e spec: sourcePod: network-check-source-8894fc9bd-vf6k6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T10:27:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.107238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:55:14Z" - latency: 859.101µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:54:14Z" - latency: 1.013644ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:53:14Z" - latency: 939.006µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:52:14Z" - latency: 1.106678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:51:14Z" - latency: 952.026µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:50:14Z" - latency: 1.126322ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:49:14Z" - latency: 1.147867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:48:14Z" - latency: 1.355201ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:47:14Z" - latency: 888.199µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:46:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T10:20:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-180-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-180.ec2.internal uid: 0cbdec3f-1381-45f2-86ce-2008b3b30104 resourceVersion: "24018" uid: 73123e1a-60ad-4858-8100-9d58ddd9b629 spec: sourcePod: network-check-source-8894fc9bd-vf6k6 targetEndpoint: af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T10:26:14Z" message: 'load-balancer-api-external: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.441379ms message: 'load-balancer-api-external: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:56:14Z" - latency: 8.136753ms message: 'load-balancer-api-external: resolved host name af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T10:56:14Z" - latency: 4.981326ms message: 'load-balancer-api-external: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:55:14Z" - latency: 8.599758ms message: 'load-balancer-api-external: resolved host name af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T10:55:14Z" - latency: 4.777636ms message: 'load-balancer-api-external: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:54:14Z" - latency: 8.361184ms message: 'load-balancer-api-external: resolved host name af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T10:54:14Z" - latency: 4.233726ms message: 'load-balancer-api-external: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:53:14Z" - latency: 8.883211ms message: 'load-balancer-api-external: resolved host name af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T10:53:14Z" - latency: 4.080354ms message: 'load-balancer-api-external: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:52:14Z" - latency: 7.379859ms message: 'load-balancer-api-external: resolved host name af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T10:52:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T10:20:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-180-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-180.ec2.internal uid: 0cbdec3f-1381-45f2-86ce-2008b3b30104 resourceVersion: "24017" uid: b205104f-18c5-4cf7-9677-c3fca9d05286 spec: sourcePod: network-check-source-8894fc9bd-vf6k6 targetEndpoint: af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T10:26:14Z" message: 'load-balancer-api-internal: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.337326ms message: 'load-balancer-api-internal: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:56:14Z" - latency: 8.271227ms message: 'load-balancer-api-internal: resolved host name af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T10:56:14Z" - latency: 4.942373ms message: 'load-balancer-api-internal: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:55:14Z" - latency: 8.6792ms message: 'load-balancer-api-internal: resolved host name af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T10:55:14Z" - latency: 4.876621ms message: 'load-balancer-api-internal: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:54:14Z" - latency: 8.400354ms message: 'load-balancer-api-internal: resolved host name af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T10:54:14Z" - latency: 4.856591ms message: 'load-balancer-api-internal: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:53:14Z" - latency: 8.951562ms message: 'load-balancer-api-internal: resolved host name af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T10:53:14Z" - latency: 4.076037ms message: 'load-balancer-api-internal: tcp connection to af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:52:14Z" - latency: 7.440304ms message: 'load-balancer-api-internal: resolved host name af0407557b0e2412686ea3b364d1adef-605d70785d652877.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T10:52:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T10:20:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-180-to-network-check-target-ip-10-0-128-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-180.ec2.internal uid: 0cbdec3f-1381-45f2-86ce-2008b3b30104 resourceVersion: "23677" uid: b5fc7458-fdee-41bc-a8e3-fe2d33b191cd spec: sourcePod: network-check-source-8894fc9bd-vf6k6 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T10:27:14Z" message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 916.276µs message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:55:14Z" - latency: 1.161103ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:54:14Z" - latency: 687.698µs message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:53:14Z" - latency: 988.823µs message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:52:14Z" - latency: 1.564086ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:51:14Z" - latency: 1.434721ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:50:14Z" - latency: 806.076µs message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:49:14Z" - latency: 953.102µs message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:48:14Z" - latency: 854.52µs message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:47:14Z" - latency: 770.503µs message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:46:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T10:20:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-180-to-network-check-target-ip-10-0-136-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-180.ec2.internal uid: 0cbdec3f-1381-45f2-86ce-2008b3b30104 resourceVersion: "23678" uid: 140d4132-07c3-4eab-b7b0-482a6f715ef6 spec: sourcePod: network-check-source-8894fc9bd-vf6k6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T10:27:14Z" message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.973046ms message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:55:14Z" - latency: 2.218017ms message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:54:14Z" - latency: 1.806431ms message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:53:14Z" - latency: 2.439041ms message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:52:14Z" - latency: 1.983208ms message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:51:14Z" - latency: 2.008471ms message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:50:14Z" - latency: 1.921649ms message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:49:14Z" - latency: 2.04669ms message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:48:14Z" - latency: 2.172589ms message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:47:14Z" - latency: 2.153789ms message: 'network-check-target-ip-10-0-136-48: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:46:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T10:20:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-180-to-network-check-target-ip-10-0-137-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-180.ec2.internal uid: 0cbdec3f-1381-45f2-86ce-2008b3b30104 resourceVersion: "23679" uid: d46baccf-db8e-44ae-b36c-df608ec1248f spec: sourcePod: network-check-source-8894fc9bd-vf6k6 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T10:27:14Z" message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.059086ms message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:55:14Z" - latency: 1.867884ms message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:54:14Z" - latency: 2.107315ms message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:53:14Z" - latency: 1.926156ms message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:52:14Z" - latency: 2.109003ms message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:51:14Z" - latency: 1.972151ms message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:50:14Z" - latency: 1.766085ms message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:49:14Z" - latency: 2.239746ms message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:48:14Z" - latency: 1.806648ms message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:47:14Z" - latency: 1.544511ms message: 'network-check-target-ip-10-0-137-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:46:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T10:20:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-180-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-180.ec2.internal uid: 0cbdec3f-1381-45f2-86ce-2008b3b30104 resourceVersion: "24015" uid: 5bb6484d-4702-4089-8aba-d6cbefff057a spec: sourcePod: network-check-source-8894fc9bd-vf6k6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T10:26:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.274369ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:56:14Z" - latency: 1.76223ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T10:56:14Z" - latency: 902.051µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:55:14Z" - latency: 1.961252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T10:55:14Z" - latency: 1.036402ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:54:14Z" - latency: 1.584813ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T10:54:14Z" - latency: 844.711µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:53:14Z" - latency: 2.237168ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T10:53:14Z" - latency: 741.839µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T10:52:14Z" - latency: 1.762438ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T10:52:14Z" kind: List metadata: resourceVersion: ""