apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:31:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 6bb076ac-7485-4678-86a4-8bb1ba601b8c resourceVersion: "22105" uid: 194f14ce-af37-4c92-9909-2259ac7d7ec6 spec: sourcePod: network-check-source-6f8b768455-xvn9c targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T07:38:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.247529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:59:06Z" - latency: 1.100491ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:58:06Z" - latency: 958.907µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:57:06Z" - latency: 974.976µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:06Z" - latency: 1.091172ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:06Z" - latency: 954.639µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:06Z" - latency: 852.089µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:06Z" - latency: 1.040256ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:06Z" - latency: 922.945µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:06Z" - latency: 1.068343ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:50:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:31:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 6bb076ac-7485-4678-86a4-8bb1ba601b8c resourceVersion: "20453" uid: 9610e2db-1d1e-4160-a1a5-7fb0a744cfdd spec: sourcePod: network-check-source-6f8b768455-xvn9c targetEndpoint: a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T07:37:06Z" message: 'load-balancer-api-external: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.697045ms message: 'load-balancer-api-external: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:06Z" - latency: 7.272913ms message: 'load-balancer-api-external: resolved host name a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:55:06Z" - latency: 4.517632ms message: 'load-balancer-api-external: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:06Z" - latency: 6.685408ms message: 'load-balancer-api-external: resolved host name a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:54:06Z" - latency: 4.603298ms message: 'load-balancer-api-external: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:06Z" - latency: 6.948282ms message: 'load-balancer-api-external: resolved host name a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:53:06Z" - latency: 4.047789ms message: 'load-balancer-api-external: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:06Z" - latency: 6.845262ms message: 'load-balancer-api-external: resolved host name a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:52:06Z" - latency: 3.95836ms message: 'load-balancer-api-external: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:06Z" - latency: 6.448181ms message: 'load-balancer-api-external: resolved host name a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:31:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 6bb076ac-7485-4678-86a4-8bb1ba601b8c resourceVersion: "20454" uid: 9c1426ac-f16b-4042-a3b3-7b099df5ec60 spec: sourcePod: network-check-source-6f8b768455-xvn9c targetEndpoint: a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T07:37:06Z" message: 'load-balancer-api-internal: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.737625ms message: 'load-balancer-api-internal: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:06Z" - latency: 7.182967ms message: 'load-balancer-api-internal: resolved host name a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:55:06Z" - latency: 3.90238ms message: 'load-balancer-api-internal: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:06Z" - latency: 6.669945ms message: 'load-balancer-api-internal: resolved host name a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:54:06Z" - latency: 5.018348ms message: 'load-balancer-api-internal: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:06Z" - latency: 7.049453ms message: 'load-balancer-api-internal: resolved host name a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:53:06Z" - latency: 4.774774ms message: 'load-balancer-api-internal: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:06Z" - latency: 6.803345ms message: 'load-balancer-api-internal: resolved host name a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:52:06Z" - latency: 3.984162ms message: 'load-balancer-api-internal: tcp connection to a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:06Z" - latency: 6.390564ms message: 'load-balancer-api-internal: resolved host name a55cfd4a42a584193abe5f4e742e3404-f167c31ba12623c7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T07:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:31:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-ip-10-0-129-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 6bb076ac-7485-4678-86a4-8bb1ba601b8c resourceVersion: "22103" uid: 6756a13e-d866-43dc-823e-c1d2bfd5276b spec: sourcePod: network-check-source-6f8b768455-xvn9c targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T07:38:06Z" message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.417305ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:59:06Z" - latency: 2.391747ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:58:06Z" - latency: 2.136172ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:57:06Z" - latency: 2.599492ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:06Z" - latency: 2.177427ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:06Z" - latency: 2.174866ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:06Z" - latency: 2.286829ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:06Z" - latency: 2.317994ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:06Z" - latency: 2.031227ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:06Z" - latency: 2.169011ms message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:50:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:31:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-ip-10-0-133-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 6bb076ac-7485-4678-86a4-8bb1ba601b8c resourceVersion: "22102" uid: 7f835efd-8071-42a2-a5c3-6d83d7fd8753 spec: sourcePod: network-check-source-6f8b768455-xvn9c targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T07:38:06Z" message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 872.112µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:59:06Z" - latency: 1.437307ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:58:06Z" - latency: 1.016133ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:57:06Z" - latency: 868.635µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:06Z" - latency: 1.273382ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:06Z" - latency: 1.111025ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:06Z" - latency: 1.323439ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:06Z" - latency: 1.130201ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:06Z" - latency: 972.071µs message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:06Z" - latency: 1.365059ms message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:50:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:31:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-ip-10-0-141-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 6bb076ac-7485-4678-86a4-8bb1ba601b8c resourceVersion: "22104" uid: 624c982d-a976-422f-8365-695df4499e7f spec: sourcePod: network-check-source-6f8b768455-xvn9c targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T07:38:06Z" message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.419026ms message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:59:06Z" - latency: 2.10575ms message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:58:06Z" - latency: 2.221721ms message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:57:06Z" - latency: 2.228748ms message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:56:06Z" - latency: 2.338182ms message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:06Z" - latency: 2.273868ms message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:06Z" - latency: 2.168953ms message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:06Z" - latency: 2.241562ms message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:06Z" - latency: 2.325718ms message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:06Z" - latency: 2.088237ms message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:50:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T07:31:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-183-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-183.ec2.internal uid: 6bb076ac-7485-4678-86a4-8bb1ba601b8c resourceVersion: "20452" uid: 2510ea60-f9c5-4367-abbb-53f14a08bd23 spec: sourcePod: network-check-source-6f8b768455-xvn9c targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T07:37:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.187µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:55:06Z" - latency: 1.872916ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T07:55:06Z" - latency: 797.252µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:54:06Z" - latency: 1.729215ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T07:54:06Z" - latency: 1.062026ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:53:06Z" - latency: 1.682225ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T07:53:06Z" - latency: 788.22µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:52:06Z" - latency: 1.950946ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T07:52:06Z" - latency: 937.897µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T07:51:06Z" - latency: 1.706406ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T07:51:06Z" kind: List metadata: resourceVersion: ""