apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T18:20:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 83c34929-d396-4d93-ad15-4135f1046e7d resourceVersion: "60399" uid: 925491b8-ecb3-4ba2-af5d-50dd2120caba spec: sourcePod: network-check-source-869dcfcdcd-b44fh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T18:27:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 868.695µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:02:03Z" - latency: 1.551994ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:01:03Z" - latency: 927.167µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:00:03Z" - latency: 1.207383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:59:03Z" - latency: 1.071461ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:58:03Z" - latency: 2.435372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:57:03Z" - latency: 770.151µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:56:03Z" - latency: 863.837µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:55:03Z" - latency: 1.254173ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:54:03Z" - latency: 991.53µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:53:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T18:20:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 83c34929-d396-4d93-ad15-4135f1046e7d resourceVersion: "60400" uid: 7cee0c76-71ff-4e3f-bbd3-54cdb6058dc4 spec: sourcePod: network-check-source-869dcfcdcd-b44fh targetEndpoint: adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T18:26:03Z" message: 'load-balancer-api-external: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.217184ms message: 'load-balancer-api-external: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:02:03Z" - latency: 7.556576ms message: 'load-balancer-api-external: resolved host name adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:02:03Z" - latency: 4.559175ms message: 'load-balancer-api-external: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:01:03Z" - latency: 7.808438ms message: 'load-balancer-api-external: resolved host name adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:01:03Z" - latency: 4.625439ms message: 'load-balancer-api-external: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:00:03Z" - latency: 6.734898ms message: 'load-balancer-api-external: resolved host name adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:00:03Z" - latency: 8.600548ms message: 'load-balancer-api-external: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:59:03Z" - latency: 7.084725ms message: 'load-balancer-api-external: resolved host name adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T18:59:03Z" - latency: 5.041801ms message: 'load-balancer-api-external: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:58:03Z" - latency: 6.698531ms message: 'load-balancer-api-external: resolved host name adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T18:58:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T18:20:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 83c34929-d396-4d93-ad15-4135f1046e7d resourceVersion: "60401" uid: 681df7b8-bd73-4b95-ab0c-bb0dab5a74f1 spec: sourcePod: network-check-source-869dcfcdcd-b44fh targetEndpoint: adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T18:26:03Z" message: 'load-balancer-api-internal: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.276178ms message: 'load-balancer-api-internal: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:02:03Z" - latency: 7.517117ms message: 'load-balancer-api-internal: resolved host name adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:02:03Z" - latency: 4.592277ms message: 'load-balancer-api-internal: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:01:03Z" - latency: 7.725778ms message: 'load-balancer-api-internal: resolved host name adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:01:03Z" - latency: 4.142787ms message: 'load-balancer-api-internal: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:00:03Z" - latency: 6.807436ms message: 'load-balancer-api-internal: resolved host name adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T19:00:03Z" - latency: 3.933152ms message: 'load-balancer-api-internal: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:59:03Z" - latency: 7.000078ms message: 'load-balancer-api-internal: resolved host name adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T18:59:03Z" - latency: 5.180755ms message: 'load-balancer-api-internal: tcp connection to adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:58:03Z" - latency: 6.623959ms message: 'load-balancer-api-internal: resolved host name adf94b175d2874ca2b08af2e8f1679dd-391e2ff9722f43fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T18:58:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T18:20:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-network-check-target-ip-10-0-130-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 83c34929-d396-4d93-ad15-4135f1046e7d resourceVersion: "60397" uid: ddde5433-6f72-4e23-b30a-de44577fdd43 spec: sourcePod: network-check-source-869dcfcdcd-b44fh targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T18:27:03Z" message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.404615ms message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:02:03Z" - latency: 2.446767ms message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:01:03Z" - latency: 2.212173ms message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:00:03Z" - latency: 2.330399ms message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:59:03Z" - latency: 1.80998ms message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:58:03Z" - latency: 2.537603ms message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:57:03Z" - latency: 2.129716ms message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:56:03Z" - latency: 2.44249ms message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:55:03Z" - latency: 2.211975ms message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:54:03Z" - latency: 2.603278ms message: 'network-check-target-ip-10-0-130-233: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:53:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T18:20:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-network-check-target-ip-10-0-135-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 83c34929-d396-4d93-ad15-4135f1046e7d resourceVersion: "60395" uid: ae69d8cd-2c39-4e05-abe0-3f977ce39f1c spec: sourcePod: network-check-source-869dcfcdcd-b44fh targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T18:27:03Z" message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.938µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:02:03Z" - latency: 1.079333ms message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:01:03Z" - latency: 773.684µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:00:03Z" - latency: 958.38µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:59:03Z" - latency: 965.201µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:58:03Z" - latency: 2.570928ms message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:57:03Z" - latency: 846.433µs message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:56:03Z" - latency: 1.102534ms message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:55:03Z" - latency: 1.482343ms message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:54:03Z" - latency: 1.908058ms message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:53:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T18:20:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-network-check-target-ip-10-0-141-171 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 83c34929-d396-4d93-ad15-4135f1046e7d resourceVersion: "60396" uid: 5500d4ba-ed81-4b3d-b9d4-db04f7ea58b4 spec: sourcePod: network-check-source-869dcfcdcd-b44fh targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T18:27:03Z" message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.777768ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:02:03Z" - latency: 2.131964ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:01:03Z" - latency: 1.75266ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:00:03Z" - latency: 2.005955ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:59:03Z" - latency: 1.811276ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:58:03Z" - latency: 1.912033ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:57:03Z" - latency: 1.71099ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:56:03Z" - latency: 2.058833ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:55:03Z" - latency: 1.900235ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:54:03Z" - latency: 1.964388ms message: 'network-check-target-ip-10-0-141-171: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:53:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T18:20:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-84-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-84.ec2.internal uid: 83c34929-d396-4d93-ad15-4135f1046e7d resourceVersion: "60398" uid: d02b7269-86e4-469f-8e62-a6716505216e spec: sourcePod: network-check-source-869dcfcdcd-b44fh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T18:26:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.06479ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:02:03Z" - latency: 1.980348ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T19:02:03Z" - latency: 891.209µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:01:03Z" - latency: 2.409455ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T19:01:03Z" - latency: 884.247µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T19:00:03Z" - latency: 2.104922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T19:00:03Z" - latency: 1.108905ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:59:03Z" - latency: 1.752867ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T18:59:03Z" - latency: 827.395µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T18:58:03Z" - latency: 1.523186ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T18:58:03Z" kind: List metadata: resourceVersion: ""