apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:43:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-79-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-79.ec2.internal uid: 9dd3a99e-8cdf-47dd-aeb9-e02f3b3f235d resourceVersion: "43877" uid: 11cb450b-f596-44f0-a996-a02cd0d523f8 spec: sourcePod: network-check-source-8894fc9bd-h5z7m targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T20:50:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.014218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:11:42Z" - latency: 915.663µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:10:42Z" - latency: 1.075015ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:09:42Z" - latency: 1.099635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:08:42Z" - latency: 911.302µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:07:42Z" - latency: 899.178µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:06:42Z" - latency: 1.150196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:05:42Z" - latency: 1.251301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:04:42Z" - latency: 967.455µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:03:42Z" - latency: 1.32521ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:02:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:43:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-79-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-79.ec2.internal uid: 9dd3a99e-8cdf-47dd-aeb9-e02f3b3f235d resourceVersion: "45833" uid: a5d6f80d-08cd-4c0a-b1c0-6194a479f3d8 spec: sourcePod: network-check-source-8894fc9bd-h5z7m targetEndpoint: a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T20:49:42Z" message: 'load-balancer-api-external: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.42676ms message: 'load-balancer-api-external: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:13:42Z" - latency: 6.356303ms message: 'load-balancer-api-external: resolved host name a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:13:42Z" - latency: 4.398205ms message: 'load-balancer-api-external: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:12:42Z" - latency: 6.517453ms message: 'load-balancer-api-external: resolved host name a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:12:42Z" - latency: 4.289443ms message: 'load-balancer-api-external: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:11:42Z" - latency: 8.473113ms message: 'load-balancer-api-external: resolved host name a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:11:42Z" - latency: 5.24548ms message: 'load-balancer-api-external: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:10:42Z" - latency: 6.675736ms message: 'load-balancer-api-external: resolved host name a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:10:42Z" - latency: 5.078339ms message: 'load-balancer-api-external: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:09:42Z" - latency: 6.282392ms message: 'load-balancer-api-external: resolved host name a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:09:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:43:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-79-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-79.ec2.internal uid: 9dd3a99e-8cdf-47dd-aeb9-e02f3b3f235d resourceVersion: "45832" uid: 8812d82f-daf2-4e4d-b7da-223fdbbd19c4 spec: sourcePod: network-check-source-8894fc9bd-h5z7m targetEndpoint: a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T20:49:42Z" message: 'load-balancer-api-internal: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.453252ms message: 'load-balancer-api-internal: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:13:42Z" - latency: 6.374908ms message: 'load-balancer-api-internal: resolved host name a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:13:42Z" - latency: 4.357288ms message: 'load-balancer-api-internal: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:12:42Z" - latency: 6.539009ms message: 'load-balancer-api-internal: resolved host name a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:12:42Z" - latency: 4.044463ms message: 'load-balancer-api-internal: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:11:42Z" - latency: 8.51772ms message: 'load-balancer-api-internal: resolved host name a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:11:42Z" - latency: 5.299216ms message: 'load-balancer-api-internal: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:10:42Z" - latency: 6.594445ms message: 'load-balancer-api-internal: resolved host name a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:10:42Z" - latency: 6.535589ms message: 'load-balancer-api-internal: tcp connection to a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:09:42Z" - latency: 6.21051ms message: 'load-balancer-api-internal: resolved host name a9f8655def13849259894355ff04b696-334d7378bf0c76ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T21:09:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:43:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-79-to-network-check-target-ip-10-0-129-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-79.ec2.internal uid: 9dd3a99e-8cdf-47dd-aeb9-e02f3b3f235d resourceVersion: "43876" uid: 62c86009-17fd-46a6-8de8-88aa8ebc7264 spec: sourcePod: network-check-source-8894fc9bd-h5z7m targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:50:42Z" message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.820196ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:11:42Z" - latency: 1.839714ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:10:42Z" - latency: 1.773393ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:09:42Z" - latency: 1.761655ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:08:42Z" - latency: 1.759906ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:07:42Z" - latency: 1.680767ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:06:42Z" - latency: 1.859518ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:05:42Z" - latency: 1.903375ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:04:42Z" - latency: 1.707709ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:03:42Z" - latency: 1.80677ms message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:02:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:43:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-79-to-network-check-target-ip-10-0-134-79 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-79.ec2.internal uid: 9dd3a99e-8cdf-47dd-aeb9-e02f3b3f235d resourceVersion: "43874" uid: b7fd177a-42ae-429d-bb98-5e84cad9fddb spec: sourcePod: network-check-source-8894fc9bd-h5z7m targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:50:42Z" message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 730.571µs message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:11:42Z" - latency: 915.318µs message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:10:42Z" - latency: 784.282µs message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:09:42Z" - latency: 807.289µs message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:08:42Z" - latency: 917.311µs message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:07:42Z" - latency: 1.349566ms message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:06:42Z" - latency: 951.948µs message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:05:42Z" - latency: 1.255505ms message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:04:42Z" - latency: 950.539µs message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:03:42Z" - latency: 1.371556ms message: 'network-check-target-ip-10-0-134-79: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:02:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:43:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-79-to-network-check-target-ip-10-0-142-90 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-79.ec2.internal uid: 9dd3a99e-8cdf-47dd-aeb9-e02f3b3f235d resourceVersion: "43875" uid: 1e017618-0939-4f32-8433-a24ece108aeb spec: sourcePod: network-check-source-8894fc9bd-h5z7m targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:50:42Z" message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.027517ms message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:11:42Z" - latency: 1.903952ms message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:10:42Z" - latency: 1.887899ms message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:09:42Z" - latency: 2.103664ms message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:08:42Z" - latency: 2.050102ms message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:07:42Z" - latency: 1.548867ms message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:06:42Z" - latency: 1.812742ms message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:05:42Z" - latency: 1.815958ms message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:04:42Z" - latency: 1.766469ms message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:03:42Z" - latency: 2.119918ms message: 'network-check-target-ip-10-0-142-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:02:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:43:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-79-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-79.ec2.internal uid: 9dd3a99e-8cdf-47dd-aeb9-e02f3b3f235d resourceVersion: "45831" uid: d2b3483a-fe27-486d-8d5e-75d3d6965339 spec: sourcePod: network-check-source-8894fc9bd-h5z7m targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T20:49:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 778.246µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:13:42Z" - latency: 1.806469ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:13:42Z" - latency: 986.579µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:12:42Z" - latency: 1.80209ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:12:42Z" - latency: 920.457µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:11:42Z" - latency: 2.527423ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:11:42Z" - latency: 841.207µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:10:42Z" - latency: 1.600302ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:10:42Z" - latency: 852.347µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T21:09:42Z" - latency: 1.883888ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T21:09:42Z" kind: List metadata: resourceVersion: ""