apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-54-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-54.ec2.internal uid: c7fee93c-547c-4f30-8d9e-eeb250bb0175 resourceVersion: "32117" uid: a8c3f39c-3bbc-41d4-b873-e085b82a8c3a spec: sourcePod: network-check-source-56499946bc-dkj7s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T14:27:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 983.369µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:02:05Z" - latency: 975.409µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:01:05Z" - latency: 1.06303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:00:05Z" - latency: 1.131855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:59:05Z" - latency: 1.051297ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:58:05Z" - latency: 990.548µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:57:05Z" - latency: 973.471µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:56:05Z" - latency: 963.42µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:55:05Z" - latency: 967.947µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:54:05Z" - latency: 983.804µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:53:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-54-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-54.ec2.internal uid: c7fee93c-547c-4f30-8d9e-eeb250bb0175 resourceVersion: "32118" uid: 190a40d8-a61e-43af-ada7-7be81f03fa2b spec: sourcePod: network-check-source-56499946bc-dkj7s targetEndpoint: a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T14:26:05Z" message: 'load-balancer-api-external: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.704214ms message: 'load-balancer-api-external: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:02:05Z" - latency: 16.956085ms message: 'load-balancer-api-external: resolved host name a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T15:02:05Z" - latency: 5.04223ms message: 'load-balancer-api-external: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:01:05Z" - latency: 10.583237ms message: 'load-balancer-api-external: resolved host name a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T15:01:05Z" - latency: 5.0515ms message: 'load-balancer-api-external: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:00:05Z" - latency: 11.045464ms message: 'load-balancer-api-external: resolved host name a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T15:00:05Z" - latency: 5.441204ms message: 'load-balancer-api-external: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:59:05Z" - latency: 12.678347ms message: 'load-balancer-api-external: resolved host name a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:59:05Z" - latency: 6.29387ms message: 'load-balancer-api-external: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:58:05Z" - latency: 14.719841ms message: 'load-balancer-api-external: resolved host name a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:58:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-54-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-54.ec2.internal uid: c7fee93c-547c-4f30-8d9e-eeb250bb0175 resourceVersion: "32119" uid: 3c11f146-dba0-4ed4-919a-3d8d86303bf5 spec: sourcePod: network-check-source-56499946bc-dkj7s targetEndpoint: a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T14:26:05Z" message: 'load-balancer-api-internal: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.708095ms message: 'load-balancer-api-internal: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:02:05Z" - latency: 16.830525ms message: 'load-balancer-api-internal: resolved host name a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T15:02:05Z" - latency: 5.046503ms message: 'load-balancer-api-internal: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:01:05Z" - latency: 10.564234ms message: 'load-balancer-api-internal: resolved host name a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T15:01:05Z" - latency: 5.557055ms message: 'load-balancer-api-internal: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:00:05Z" - latency: 11.01948ms message: 'load-balancer-api-internal: resolved host name a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T15:00:05Z" - latency: 5.316602ms message: 'load-balancer-api-internal: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:59:05Z" - latency: 12.772519ms message: 'load-balancer-api-internal: resolved host name a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:59:05Z" - latency: 6.285417ms message: 'load-balancer-api-internal: tcp connection to a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:58:05Z" - latency: 14.660601ms message: 'load-balancer-api-internal: resolved host name a4adaec090dbf449d857107fd2805d5f-07bd25d8f597509a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:58:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-54-to-network-check-target-ip-10-0-134-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-54.ec2.internal uid: c7fee93c-547c-4f30-8d9e-eeb250bb0175 resourceVersion: "32113" uid: a00dc7b0-09ec-4bc6-a9b8-581c1da27ef6 spec: sourcePod: network-check-source-56499946bc-dkj7s targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T14:27:05Z" message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.304069ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:02:05Z" - latency: 839.117µs message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:01:05Z" - latency: 954.248µs message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:00:05Z" - latency: 1.561071ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:59:05Z" - latency: 1.226265ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:58:05Z" - latency: 914.952µs message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:57:05Z" - latency: 765.43µs message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:56:05Z" - latency: 893.803µs message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:55:05Z" - latency: 846.377µs message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:54:05Z" - latency: 938.168µs message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:53:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-54-to-network-check-target-ip-10-0-143-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-54.ec2.internal uid: c7fee93c-547c-4f30-8d9e-eeb250bb0175 resourceVersion: "32115" uid: cd44b11e-1875-49bd-9a0b-c5152462c0f4 spec: sourcePod: network-check-source-56499946bc-dkj7s targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T14:27:05Z" message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.616399ms message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:02:05Z" - latency: 1.828135ms message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:01:05Z" - latency: 1.723809ms message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:00:05Z" - latency: 1.856487ms message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:59:05Z" - latency: 1.848295ms message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:58:05Z" - latency: 1.842223ms message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:57:05Z" - latency: 1.858183ms message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:56:05Z" - latency: 1.840664ms message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:55:05Z" - latency: 1.674105ms message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:54:05Z" - latency: 1.706506ms message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:53:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-54-to-network-check-target-ip-10-0-143-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-54.ec2.internal uid: c7fee93c-547c-4f30-8d9e-eeb250bb0175 resourceVersion: "32114" uid: 08065491-9c89-462f-9dcd-f1294939f5b2 spec: sourcePod: network-check-source-56499946bc-dkj7s targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T14:27:05Z" message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.189489ms message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:02:05Z" - latency: 2.312571ms message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:01:05Z" - latency: 2.339549ms message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:00:05Z" - latency: 2.261578ms message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:59:05Z" - latency: 2.089749ms message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:58:05Z" - latency: 2.267174ms message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:57:05Z" - latency: 2.421156ms message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:56:05Z" - latency: 2.358669ms message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:55:05Z" - latency: 2.210227ms message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:54:05Z" - latency: 2.130403ms message: 'network-check-target-ip-10-0-143-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:53:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-54-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-54.ec2.internal uid: c7fee93c-547c-4f30-8d9e-eeb250bb0175 resourceVersion: "32116" uid: 8f20d4ab-41d5-4c94-a7a8-a0f752a9f54d spec: sourcePod: network-check-source-56499946bc-dkj7s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T14:26:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 840.955µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:02:05Z" - latency: 2.147861ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T15:02:05Z" - latency: 952.18µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:01:05Z" - latency: 1.940934ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T15:01:05Z" - latency: 933.95µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T15:00:05Z" - latency: 1.815726ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T15:00:05Z" - latency: 1.053934ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:59:05Z" - latency: 1.812679ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:59:05Z" - latency: 897.125µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:58:05Z" - latency: 1.829888ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:58:05Z" kind: List metadata: resourceVersion: ""