apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: 57d7a012-739e-4f0e-90ac-d18414934fb5 resourceVersion: "55828" uid: ef0becf7-e389-4cb2-a825-2c6c3865a223 spec: sourcePod: network-check-source-869dcfcdcd-5nbcv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T17:05:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 947.855µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:33:35Z" - latency: 913.14µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:32:35Z" - latency: 855.266µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:31:35Z" - latency: 1.10541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:30:35Z" - latency: 883.38µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:29:35Z" - latency: 997.367µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:28:35Z" - latency: 1.118924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:27:35Z" - latency: 1.117353ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:26:35Z" - latency: 963.433µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:25:35Z" - latency: 1.084509ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: 57d7a012-739e-4f0e-90ac-d18414934fb5 resourceVersion: "56779" uid: 101a162f-b053-4269-8359-7966459debe2 spec: sourcePod: network-check-source-869dcfcdcd-5nbcv targetEndpoint: a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T17:04:35Z" message: 'load-balancer-api-external: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.348143ms message: 'load-balancer-api-external: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:34:35Z" - latency: 8.88124ms message: 'load-balancer-api-external: resolved host name a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:34:35Z" - latency: 4.001502ms message: 'load-balancer-api-external: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:33:35Z" - latency: 9.714152ms message: 'load-balancer-api-external: resolved host name a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:33:35Z" - latency: 5.290488ms message: 'load-balancer-api-external: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:32:35Z" - latency: 9.51358ms message: 'load-balancer-api-external: resolved host name a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:32:35Z" - latency: 4.013016ms message: 'load-balancer-api-external: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:31:35Z" - latency: 13.683409ms message: 'load-balancer-api-external: resolved host name a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:31:35Z" - latency: 6.201212ms message: 'load-balancer-api-external: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:30:35Z" - latency: 7.124377ms message: 'load-balancer-api-external: resolved host name a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:30:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: 57d7a012-739e-4f0e-90ac-d18414934fb5 resourceVersion: "56780" uid: 1a825e80-7a55-4cbc-9ab3-f7c6790677e5 spec: sourcePod: network-check-source-869dcfcdcd-5nbcv targetEndpoint: a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T17:04:35Z" message: 'load-balancer-api-internal: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.282282ms message: 'load-balancer-api-internal: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:34:35Z" - latency: 8.841528ms message: 'load-balancer-api-internal: resolved host name a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:34:35Z" - latency: 3.951859ms message: 'load-balancer-api-internal: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:33:35Z" - latency: 9.68323ms message: 'load-balancer-api-internal: resolved host name a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:33:35Z" - latency: 5.263759ms message: 'load-balancer-api-internal: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:32:35Z" - latency: 9.3924ms message: 'load-balancer-api-internal: resolved host name a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:32:35Z" - latency: 3.717717ms message: 'load-balancer-api-internal: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:31:35Z" - latency: 13.708521ms message: 'load-balancer-api-internal: resolved host name a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:31:35Z" - latency: 6.241172ms message: 'load-balancer-api-internal: tcp connection to a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:30:35Z" - latency: 7.004579ms message: 'load-balancer-api-internal: resolved host name a2573aee9e37249a38e6816f692bf9ab-1732960ffa1061c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T17:30:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-network-check-target-ip-10-0-131-207 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: 57d7a012-739e-4f0e-90ac-d18414934fb5 resourceVersion: "55826" uid: d065f07d-46b2-4a90-aec1-a212ebbbf9eb spec: sourcePod: network-check-source-869dcfcdcd-5nbcv targetEndpoint: 10.135.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T17:05:35Z" message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.307043ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:33:35Z" - latency: 2.680676ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:32:35Z" - latency: 2.347842ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:31:35Z" - latency: 2.660955ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:30:35Z" - latency: 2.392341ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:29:35Z" - latency: 2.293458ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:28:35Z" - latency: 2.592763ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:27:35Z" - latency: 2.408531ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:26:35Z" - latency: 2.348397ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:25:35Z" - latency: 2.583002ms message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.135.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-network-check-target-ip-10-0-136-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: 57d7a012-739e-4f0e-90ac-d18414934fb5 resourceVersion: "55825" uid: 3e194c9a-4e98-4a30-92eb-b7bae1d01057 spec: sourcePod: network-check-source-869dcfcdcd-5nbcv targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T17:05:35Z" message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.158821ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:33:35Z" - latency: 1.858906ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:32:35Z" - latency: 1.054982ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:31:35Z" - latency: 1.342545ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:30:35Z" - latency: 1.160456ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:29:35Z" - latency: 932.933µs message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:28:35Z" - latency: 777.488µs message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:27:35Z" - latency: 948.3µs message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:26:35Z" - latency: 1.021617ms message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:25:35Z" - latency: 909.326µs message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-network-check-target-ip-10-0-141-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: 57d7a012-739e-4f0e-90ac-d18414934fb5 resourceVersion: "55827" uid: e9d5a78f-e018-425c-bf2d-b8dd2bbb31fe spec: sourcePod: network-check-source-869dcfcdcd-5nbcv targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T17:05:35Z" message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.562941ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:33:35Z" - latency: 2.639559ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:32:35Z" - latency: 2.270508ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:31:35Z" - latency: 2.727588ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:30:35Z" - latency: 3.407892ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:29:35Z" - latency: 2.369625ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:28:35Z" - latency: 2.012263ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:27:35Z" - latency: 2.502041ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:26:35Z" - latency: 1.95368ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:25:35Z" - latency: 2.015563ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:24:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T16:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-7-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-7.ec2.internal uid: 57d7a012-739e-4f0e-90ac-d18414934fb5 resourceVersion: "56778" uid: 9771e461-3298-4ab6-8f91-27854933921f spec: sourcePod: network-check-source-869dcfcdcd-5nbcv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T17:04:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.259071ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:34:35Z" - latency: 1.826163ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:34:35Z" - latency: 1.180032ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:33:35Z" - latency: 2.38585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:33:35Z" - latency: 813.253µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:32:35Z" - latency: 2.23968ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:32:35Z" - latency: 1.078469ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:31:35Z" - latency: 1.906734ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:31:35Z" - latency: 1.476819ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T17:30:35Z" - latency: 2.260654ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T17:30:35Z" kind: List metadata: resourceVersion: ""