apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:04:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-64-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-64.ec2.internal uid: 223343fd-e37d-4afb-a9bc-97813613ebd7 resourceVersion: "62598" uid: 2ac4f06f-e3da-4c86-9daa-7ae6c3884454 spec: sourcePod: network-check-source-7bc5b6bf85-wmkqw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T17:11:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.065727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:53Z" - latency: 886.964µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:53Z" - latency: 950.248µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:53Z" - latency: 1.529201ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:53Z" - latency: 1.053619ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:53Z" - latency: 965.567µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:41:53Z" - latency: 1.281321ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:40:53Z" - latency: 1.122964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:39:53Z" - latency: 1.31552ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:38:53Z" - latency: 1.095536ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:37:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:04:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-64-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-64.ec2.internal uid: 223343fd-e37d-4afb-a9bc-97813613ebd7 resourceVersion: "62599" uid: fa2e6339-71ca-404f-812c-348a7ec06f4e spec: sourcePod: network-check-source-7bc5b6bf85-wmkqw targetEndpoint: a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T17:10:53Z" message: 'load-balancer-api-external: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.018502ms message: 'load-balancer-api-external: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:53Z" - latency: 8.839737ms message: 'load-balancer-api-external: resolved host name a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:46:53Z" - latency: 5.626283ms message: 'load-balancer-api-external: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:53Z" - latency: 8.432404ms message: 'load-balancer-api-external: resolved host name a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:45:53Z" - latency: 5.600112ms message: 'load-balancer-api-external: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:53Z" - latency: 7.35467ms message: 'load-balancer-api-external: resolved host name a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:44:53Z" - latency: 4.239886ms message: 'load-balancer-api-external: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:53Z" - latency: 8.773855ms message: 'load-balancer-api-external: resolved host name a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:43:53Z" - latency: 5.544514ms message: 'load-balancer-api-external: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:53Z" - latency: 8.083316ms message: 'load-balancer-api-external: resolved host name a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:42:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:04:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-64-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-64.ec2.internal uid: 223343fd-e37d-4afb-a9bc-97813613ebd7 resourceVersion: "62600" uid: f2070394-c399-4578-b0a4-ab67997f7188 spec: sourcePod: network-check-source-7bc5b6bf85-wmkqw targetEndpoint: a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T17:10:53Z" message: 'load-balancer-api-internal: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.189259ms message: 'load-balancer-api-internal: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:53Z" - latency: 8.941381ms message: 'load-balancer-api-internal: resolved host name a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:46:53Z" - latency: 5.680942ms message: 'load-balancer-api-internal: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:53Z" - latency: 8.394437ms message: 'load-balancer-api-internal: resolved host name a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:45:53Z" - latency: 5.565477ms message: 'load-balancer-api-internal: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:53Z" - latency: 7.500039ms message: 'load-balancer-api-internal: resolved host name a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:44:53Z" - latency: 4.232859ms message: 'load-balancer-api-internal: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:53Z" - latency: 8.962916ms message: 'load-balancer-api-internal: resolved host name a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:43:53Z" - latency: 5.475093ms message: 'load-balancer-api-internal: tcp connection to a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:53Z" - latency: 8.170093ms message: 'load-balancer-api-internal: resolved host name a62ee4391e63348b098353c1598d76f2-2debf554bdc52090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T17:42:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:04:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-64-to-network-check-target-ip-10-0-134-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-64.ec2.internal uid: 223343fd-e37d-4afb-a9bc-97813613ebd7 resourceVersion: "62595" uid: 673b3aa6-20a3-4ff3-91f9-980b6ce5c131 spec: sourcePod: network-check-source-7bc5b6bf85-wmkqw targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:11:53Z" message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.923676ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:53Z" - latency: 1.875584ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:53Z" - latency: 1.838729ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:53Z" - latency: 1.857481ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:53Z" - latency: 1.737991ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:53Z" - latency: 2.998202ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:41:53Z" - latency: 1.998686ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:40:53Z" - latency: 1.613635ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:39:53Z" - latency: 1.960758ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:38:53Z" - latency: 3.054907ms message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:37:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:04:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-64-to-network-check-target-ip-10-0-136-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-64.ec2.internal uid: 223343fd-e37d-4afb-a9bc-97813613ebd7 resourceVersion: "62594" uid: f23568ef-e334-4274-ab3d-b3257bfa766e spec: sourcePod: network-check-source-7bc5b6bf85-wmkqw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:11:53Z" message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 828.939µs message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:53Z" - latency: 946.945µs message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:53Z" - latency: 954.715µs message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:53Z" - latency: 789.361µs message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:53Z" - latency: 997.212µs message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:53Z" - latency: 1.074065ms message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:41:53Z" - latency: 1.010686ms message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:40:53Z" - latency: 1.266574ms message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:39:53Z" - latency: 1.679105ms message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:38:53Z" - latency: 4.48513ms message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:37:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:04:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-64-to-network-check-target-ip-10-0-140-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-64.ec2.internal uid: 223343fd-e37d-4afb-a9bc-97813613ebd7 resourceVersion: "62596" uid: 33a306d9-4cd4-44fe-8c56-37a4b5c9becf spec: sourcePod: network-check-source-7bc5b6bf85-wmkqw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-21T17:11:53Z" message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.270319ms message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:53Z" - latency: 2.545845ms message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:53Z" - latency: 2.250571ms message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:53Z" - latency: 2.00646ms message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:53Z" - latency: 2.170115ms message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:53Z" - latency: 5.811938ms message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:41:53Z" - latency: 2.138565ms message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:40:53Z" - latency: 2.373552ms message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:39:53Z" - latency: 2.459139ms message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:38:53Z" - latency: 3.975181ms message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:37:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T17:04:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-64-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-64.ec2.internal uid: 223343fd-e37d-4afb-a9bc-97813613ebd7 resourceVersion: "62597" uid: 2e526c05-bf2d-4d2b-95fc-f740beb92139 spec: sourcePod: network-check-source-7bc5b6bf85-wmkqw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T17:10:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.145106ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:46:53Z" - latency: 1.683263ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:46:53Z" - latency: 1.312634ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:45:53Z" - latency: 1.685276ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:45:53Z" - latency: 1.045418ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:44:53Z" - latency: 1.864315ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:44:53Z" - latency: 1.088166ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:43:53Z" - latency: 1.946718ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:43:53Z" - latency: 1.183654ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T17:42:53Z" - latency: 1.769552ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T17:42:53Z" kind: List metadata: resourceVersion: ""